From: Julien Grall <julien.grall@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Marc Zyngier <marc.zyngier@arm.com>,
cross-distro@lists.linaro.org, Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH v2] ArmPkg/TimerDxe: remove workaround for KVM timer handling
Date: Mon, 23 Apr 2018 11:27:12 +0100 [thread overview]
Message-ID: <e96d90db-8111-0e0e-f3b6-c812a45a79f7@arm.com> (raw)
In-Reply-To: <CAKv+Gu_z+bWCcf5AXh1OADfeNLRug3vrx666sQxoR-zrpmyKxg@mail.gmail.com>
On 19/04/18 15:34, Ard Biesheuvel wrote:
> On 19 April 2018 at 16:23, Julien Grall <julien.grall@arm.com> wrote:
>> Hi Ard,
>>
>> Sorry for the late reply.
>>
>> On 19/04/18 09:16, Ard Biesheuvel wrote:
>>>
>>> On 17 April 2018 at 08:03, Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>> 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.
>>>>
>>>> Cc: cross-distro@lists.linaro.org
>>>> Contributed-under: TianoCore Contribution Agreement 1.1
>>>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>>> Acked-by: Marc Zyngier <marc.zyngier@arm.com>
>>>> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
>>>> Acked-by: Laszlo Ersek <lersek@redhat.com>
>>>
>>>
>>> Pushed as 411a373ed6426fb1bff253905b6a59ada44e18ad
>>
>>
>> While this was added for KVM, I believe that code is also needed by Xen.
>> Indeed before injecting the interrupt the hypervisor will mask the
>> interrupt.
>>
>> So would it be possible to revert that patch?
>>
>
> Given that this is now a Xen-only quirk, I'd rather work around it by
> creating a separate ArmGenericTimerCounterLib implementation for Xen.
That would work for me.
>
> I will try to put something together beginning of next week.
I am happy to test it.
Cheers,
--
Julien Grall
prev parent reply other threads:[~2018-04-23 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 6:03 [PATCH v2] ArmPkg/TimerDxe: remove workaround for KVM timer handling Ard Biesheuvel
2018-04-19 8:16 ` Ard Biesheuvel
2018-04-19 14:23 ` Julien Grall
2018-04-19 14:34 ` Ard Biesheuvel
2018-04-23 10:27 ` Julien Grall [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=e96d90db-8111-0e0e-f3b6-c812a45a79f7@arm.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