From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL v2 0/6] KVM/ARM Fixes for v4.12-rc5 - Take 2
Date: Thu, 8 Jun 2017 15:04:50 +0200 [thread overview]
Message-ID: <2a8a3bf1-d7dc-e005-b8b2-d7eb03e7a998@redhat.com> (raw)
In-Reply-To: <20170607171152.21874-1-cdall@linaro.org>
On 07/06/2017 19:11, Christoffer Dall wrote:
> Hi Radim and Paolo,
>
> Six additional fixes for KVM/ARM for v4.12 (instead of only the first
> three in the first version of this pull request).
>
> The changes are:
> - Fix an issue with migrating GICv2 VMs on GICv3 systems.
> - Squashed a bug for gicv3 when figuring out preemption levels.
> - Fix a potential null pointer derefence in KVM happening under memory
> pressure.
> - Maintain RES1 bits in the SCTLR_EL2 to make sure KVM works on new
> architecture revisions.
> - Allow unaligned accesses at EL2/HYP
>
> 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-take2
>
> for you to fetch changes up to 33b5c38852b29736f3b472dd095c9a18ec22746f:
>
> arm: KVM: Allow unaligned accesses at HYP (2017-06-06 22:20:02 +0200)
>
> Thanks,
> -Christoffer
Pulled, thanks.
Paolo
> ---
> Christoffer Dall (2):
> KVM: arm/arm64: Fix isues with GICv2 on GICv3 migration
> KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction
>
> Marc Zyngier (4):
> KVM: arm/arm64: Handle possible NULL stage2 pud when ageing pages
> arm64: KVM: Preserve RES1 bits in SCTLR_EL2
> arm64: KVM: Allow unaligned accesses at EL2
> arm: KVM: Allow unaligned accesses at HYP
>
> arch/arm/kvm/init.S | 5 ++--
> arch/arm64/include/asm/sysreg.h | 4 ++++
> arch/arm64/kvm/hyp-init.S | 11 +++++----
> arch/arm64/kvm/vgic-sys-reg-v3.c | 10 ++++----
> include/linux/irqchip/arm-gic-v3.h | 4 ++++
> include/linux/irqchip/arm-gic.h | 28 ++++++++++++++++++++---
> virt/kvm/arm/hyp/vgic-v3-sr.c | 2 +-
> virt/kvm/arm/mmu.c | 3 +++
> virt/kvm/arm/vgic/vgic-mmio-v2.c | 16 +++++++++++--
> virt/kvm/arm/vgic/vgic-v2.c | 28 ++++++++++++++++++++---
> virt/kvm/arm/vgic/vgic-v3.c | 47 ++++++++++++++++++++++++++------------
> virt/kvm/arm/vgic/vgic.h | 12 ++++++----
> 12 files changed, 131 insertions(+), 39 deletions(-)
>
prev parent reply other threads:[~2017-06-08 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 17:11 [PULL v2 0/6] KVM/ARM Fixes for v4.12-rc5 - Take 2 Christoffer Dall
2017-06-07 17:11 ` [PULL v2 1/6] KVM: arm/arm64: Fix isues with GICv2 on GICv3 migration Christoffer Dall
2017-06-07 17:11 ` [PULL v2 2/6] KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction Christoffer Dall
2017-06-07 17:11 ` [PULL v2 3/6] KVM: arm/arm64: Handle possible NULL stage2 pud when ageing pages Christoffer Dall
2017-06-07 17:11 ` [PULL v2 4/6] arm64: KVM: Preserve RES1 bits in SCTLR_EL2 Christoffer Dall
2017-06-07 17:11 ` [PULL v2 5/6] arm64: KVM: Allow unaligned accesses at EL2 Christoffer Dall
2017-06-07 17:11 ` [PULL v2 6/6] arm: KVM: Allow unaligned accesses at HYP Christoffer Dall
2017-06-08 13:04 ` Paolo Bonzini [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=2a8a3bf1-d7dc-e005-b8b2-d7eb03e7a998@redhat.com \
--to=pbonzini@redhat.com \
--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).