public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Guo Heyi <heyi.guo@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Yi Li <phoenix.liyi@huawei.com>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH v2 1/1] ArmPkg/TimerDxe: Add ISB for timer compare value reload
Date: Thu, 15 Mar 2018 09:40:41 +0000	[thread overview]
Message-ID: <147790b3-379c-81b8-57e1-f7b5d99b9db7@arm.com> (raw)
In-Reply-To: <CAKv+Gu-JTy=gkcLGWW5P-8KJr092+ugOL12m+9s4Q+WaUW_1fQ@mail.gmail.com>

On 15/03/18 07:30, Ard Biesheuvel wrote:
> On 15 March 2018 at 07:11, Guo Heyi <heyi.guo@linaro.org> wrote:
>> Hi Marc and Ard,
>>
>> I found the timer re-enable code was added by Ard for special reason:
>>
>> commit b1a633434ddc5fc28de817debd963f7845fb78c7
>> Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Date:   Thu Sep 18 21:16:47 2014 +0000
>>
>>     ArmPkg/TimerDxe: add workaround for KVM timer interrupt handling
>>
>> So this line of code cannot be removed and I will add an ISB after enabling
>> timer.
>>
> 
> I'm not sure. IIUC, the KVM issue that required this has been fixed
> long ago, and I don't want to carry this forever. Marc?

This has been fixed quite a while ago:

commit f120cd6533d21075ab103ae6c225b1697853660d
Author: Marc Zyngier <marc.zyngier@arm.com>
Date:   Mon Jun 23 13:59:13 2014 +0100

    KVM: arm/arm64: timer: Allow the timer to control the active state

    In order to remove the crude hack where we sneak the masked bit
    into the timer's control register, make use of the phys_irq_map
    API control the active state of the interrupt.

    This causes some limited changes to allow for potential error
    propagation.

    Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
    Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>

>> Another strange thing is that we got lots of "Spurious GIC interrupt" error
>> messages when timer enable code was removed, though at last it could boot to EFI
>> shell. Please let me know if you have any idea about the possible reason of this
>> issue.
>>
> 
> No idea, sorry.

Me neither. You'd have to dump the control register before and after,
and work out what is being changed exactly.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...


  reply	other threads:[~2018-03-15  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13  0:31 [PATCH v2 0/1] ArmPkg/TimerDxe: Add ISB for timer compare value reload Heyi Guo
2018-03-13  0:31 ` [PATCH v2 1/1] " Heyi Guo
2018-03-13  9:33   ` Marc Zyngier
2018-03-14  0:25     ` Guo Heyi
2018-03-14  7:45       ` Marc Zyngier
2018-03-14 14:50         ` Ard Biesheuvel
2018-03-15  7:11           ` Guo Heyi
2018-03-15  7:30             ` Ard Biesheuvel
2018-03-15  9:40               ` Marc Zyngier [this message]
2018-03-15  9:52                 ` Ard Biesheuvel
2018-03-15 10:02                   ` Marc Zyngier

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=147790b3-379c-81b8-57e1-f7b5d99b9db7@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