From: Christoffer Dall <cdall@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
"Alexander Graf" <agraf@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Marc Zyngier" <marc.zyngier@arm.com>
Subject: Re: [PATCH kvm-unit-tests] arm64: timer: Avoid IRQ race in timer test
Date: Thu, 3 Aug 2017 08:24:21 +0200 [thread overview]
Message-ID: <20170803062421.GA17272@cbox> (raw)
In-Reply-To: <20170802155312.yep4rywinl5pmc6i@kamzik.brq.redhat.com>
On Wed, Aug 02, 2017 at 05:53:12PM +0200, Andrew Jones wrote:
> On Wed, Jul 26, 2017 at 01:42:49PM +0200, Christoffer Dall wrote:
> > The current timer test relies on testing the pending state of the timer
> > before the interrupt handler has run which could lower the pending
> > signal again (because it masks the timer output signal).
> >
> > What we really want is to make sure the output signal from the timer as
> > perceived by the virtual interrupt controller is low when the timer is
> > programmed some time far in the future. The proper way to do that is to
> > disable the timer interrupt on the distributor and then reading its
> > pending state.
> >
> > Signed-off-by: Christoffer Dall <cdall@linaro.org>
> > ---
> > arm/timer.c | 41 ++++++++++++++++++++++++++++++++++-------
> > 1 file changed, 34 insertions(+), 7 deletions(-)
> >
>
> Hi Christoffer,
>
> With this patch the ptimer "not pending before" test always
> fails on KVM for me (tested on mustang and thunderx). Have
> you seen that?
>
Doy, yeah, that was a silly one. Patch incoming.
Thanks,
-Christoffer
prev parent reply other threads:[~2017-08-03 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:42 [PATCH kvm-unit-tests] arm64: timer: Avoid IRQ race in timer test Christoffer Dall
2017-07-26 13:18 ` Paolo Bonzini
2017-08-02 15:53 ` Andrew Jones
2017-08-03 6:24 ` Christoffer Dall [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-all 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=20170803062421.GA17272@cbox \
--to=cdall@linaro.org \
--cc=agraf@suse.de \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.