From: Pavel Fedin <p.fedin@samsung.com>
To: 'Christoffer Dall' <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
'Marc Zyngier' <marc.zyngier@arm.com>
Subject: RE: [PATCH] KVM: arm/arm64: BUG FIX: Do not inject spurious interrupts
Date: Fri, 25 Sep 2015 17:01:45 +0300 [thread overview]
Message-ID: <012f01d0f79a$b6fc59c0$24f50d40$@samsung.com> (raw)
In-Reply-To: <20150914112932.GH15712@cbox>
Hello!
> The alternative is to just call compute_pending which does nothing more
> than a few bitwise and/or operations plus a couple of handfuls of
> load/stores on this IRQ injection path, so I don't see the problem doing
> this.
I looked at it, convinced. After all, resetting pending_on_cpu saves from unnecessary wakeups IIRC.
Posting v2...
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
prev parent reply other threads:[~2015-09-25 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 11:51 [PATCH] KVM: arm/arm64: BUG FIX: Do not inject spurious interrupts Pavel Fedin
2015-08-27 12:44 ` Christoffer Dall
2015-08-28 9:11 ` Pavel Fedin
2015-09-14 11:29 ` Christoffer Dall
2015-09-25 14:01 ` Pavel Fedin [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='012f01d0f79a$b6fc59c0$24f50d40$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox