From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL 0/3] KVM/ARM Fixes for v4.12-rc5
Date: Tue, 6 Jun 2017 22:21:30 +0200 [thread overview]
Message-ID: <20170606202130.GS9464@cbox> (raw)
In-Reply-To: <20170606135629.31664-1-cdall@linaro.org>
On Tue, Jun 06, 2017 at 03:56:26PM +0200, Christoffer Dall wrote:
> Hi Radim and Paolo,
>
> Three additional fixes for KVM/ARM for v4.12.
We didn't expect three additional fixes to pop up so quickly, so I'm
going to send another pull request tomorrow.
Please hold off on applying this one if you haven't done so already.
Sorry about that.
-Christoffer
>
> They fix an issue with migrating GICv2 VMs on GICv3 systems, squash a
> bug for gicv3 when figuring out preemption levels, and fix a potential
> null pointer derefence in KVM happening under memory pressure.
>
> The following changes since commit fa472fa91a5a0b241f5ddae927d2e235d07545df:
>
> KVM: arm/arm64: Hold slots_lock when unregistering kvm io bus devices (2017-05-18 11:18:16 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git kvm-arm-for-v4.12-rc5
>
> for you to fetch changes up to d6dbdd3c8558cad3b6d74cc357b408622d122331:
>
> KVM: arm/arm64: Handle possible NULL stage2 pud when ageing pages (2017-06-06 15:28:40 +0200)
>
next prev parent reply other threads:[~2017-06-06 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 13:56 [PULL 0/3] KVM/ARM Fixes for v4.12-rc5 Christoffer Dall
2017-06-06 13:56 ` [PULL 1/3] KVM: arm/arm64: Fix isues with GICv2 on GICv3 migration Christoffer Dall
2017-06-06 13:56 ` [PULL 2/3] KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction Christoffer Dall
2017-06-06 13:56 ` [PULL 3/3] KVM: arm/arm64: Handle possible NULL stage2 pud when ageing pages Christoffer Dall
2017-06-06 20:21 ` Christoffer Dall [this message]
2017-06-07 9:24 ` [PULL 0/3] KVM/ARM Fixes for v4.12-rc5 Radim Krčmář
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=20170606202130.GS9464@cbox \
--to=cdall@linaro.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).