From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Heyi Guo <heyi.guo@linaro.org>
Subject: Re: [PATCH] ArmPkg/TimerDxe: remove workaround for KVM timer handling
Date: Fri, 16 Mar 2018 13:25:47 +0000 [thread overview]
Message-ID: <CAKv+Gu-AyBaRaB=Tv6JzCeenEhWHy6Ayx8iPCuqRCOoHV+g+dw@mail.gmail.com> (raw)
In-Reply-To: <20180316114625.zbdwpqjskgpl3iwp@bivouac.eciton.net>
On 16 March 2018 at 11:46, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Fri, Mar 16, 2018 at 11:28:21AM +0000, Ard Biesheuvel wrote:
>> On 15 March 2018 at 19:01, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>> > On Thu, Mar 15, 2018 at 10:28:26AM +0000, Ard Biesheuvel wrote:
>> >> When we first ported EDK2 to KVM/arm, we implemented a workaround for
>> >> the quirky timer handling on the KVM side. This has been fixed in
>> >> Linux commit f120cd6533d2 ("KVM: arm/arm64: timer: Allow the timer to
>> >> control the active state") dated 23 June 2014, which was incorporated
>> >> into Linux release 4.3.
>> >>
>> >> So almost 4 years later, it should be safe to drop this workaround on
>> >> the EDK2 side.
>> >>
>> >> This reverts commit b1a633434ddc.
>> >>
>> >> Contributed-under: TianoCore Contribution Agreement 1.1
>> >> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> >
>> > I'm happy with this, with Marc's Ack.
>> > Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
>> >
>> > However, if this can affect old kernels running in vms, could you ping
>> > cross-distro@lists.linaro.org as well, so it doesn't catch anyone by
>> > surprise?
>>
>> It will affects VMs running new firmware on ancient host kernels (and
>> v4.2 *is* ancient when it comes to KVM/arm64 and server stuff imo)
>
> Oh, it is, but if we have
> https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754
> (Xenial guest), imagining people running a Zesty host isn't that much
> more of a stretch (it's only EOL 2 months ago).
>
Xenial has v4.4, Zesty has v4.10, if I am not mistaken?
Still doesn't hurt to cc cross-distro, obviously. Just sayin'
prev parent reply other threads:[~2018-03-16 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 10:28 [PATCH] ArmPkg/TimerDxe: remove workaround for KVM timer handling Ard Biesheuvel
2018-03-15 10:40 ` Marc Zyngier
2018-03-15 19:01 ` Leif Lindholm
2018-03-15 19:47 ` Laszlo Ersek
2018-03-16 11:28 ` Ard Biesheuvel
2018-03-16 11:46 ` Leif Lindholm
2018-03-16 13:25 ` Ard Biesheuvel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKv+Gu-AyBaRaB=Tv6JzCeenEhWHy6Ayx8iPCuqRCOoHV+g+dw@mail.gmail.com' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox