From: maz@misterjones.org (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL] VGIC fixes for KVM/ARM
Date: Fri, 22 Feb 2013 14:58:12 +0100 [thread overview]
Message-ID: <b06d478e1008aa14c12fa1ea9f8da941@localhost> (raw)
Arnd, Olof,
Please find below a pull request for a couple of fixes concerning
the VGIC implementation in KVM. No real hurry, these can probably
be applied after the merge window.
The branch is on top of mainline as of this morning, but I'm happy
to rebase it on something else if that's more convenient.
Thanks,
M.
---------------->8--------------
The following changes since commit
2ef14f465b9e096531343f5b734cffc5f759f4a6:
Merge branch 'x86-mm-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2013-02-21 18:06:55
-0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
kvm-arm/vgic-fixes
for you to fetch changes up to 33c83cb3c1d84b76c8270abe5487e77f83a81b22:
ARM: KVM: vgic: take distributor lock on sync_hwstate path (2013-02-22
13:29:38 +0000)
----------------------------------------------------------------
Marc Zyngier (2):
ARM: KVM: vgic: force EOIed LRs to the empty state
ARM: KVM: vgic: take distributor lock on sync_hwstate path
arch/arm/kvm/vgic.c | 35 ++++++++++++++---------------------
1 file changed, 14 insertions(+), 21 deletions(-)
--
Who you jivin' with that Cosmik Debris?
next reply other threads:[~2013-02-22 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 13:58 Marc Zyngier [this message]
2013-02-22 15:41 ` [PULL] VGIC fixes for KVM/ARM Russell King - ARM Linux
2013-02-22 17:28 ` Marc Zyngier
2013-02-22 19:18 ` Russell King - ARM Linux
2013-02-22 19:30 ` Marc Zyngier
2013-03-22 16:29 ` Marc Zyngier
2013-03-22 17:13 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2013-03-22 17:43 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-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=b06d478e1008aa14c12fa1ea9f8da941@localhost \
--to=maz@misterjones.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).