linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL 0/2] KVM/ARM Fixes for v4.8 - round #2
Date: Fri,  9 Sep 2016 12:54:54 +0200	[thread overview]
Message-ID: <20160909105456.8585-1-christoffer.dall@linaro.org> (raw)

Hi Paolo and Radim,

Here are a couple of fixes for KVM/ARM for v4.8-rc6 or -rc7, as soon as
they can make it.

They fix an idmap issue on 32-bit KVM on ARM, and fixes a memory
unmapping issue that we've had forever on both arm and arm64.

The following changes since commit 20218b86ad8adb4bf71db9425bb59680f345eafd:

  Merge tag 'kvm-s390-master-4.8-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvm-master (2016-09-05 16:15:22 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvm-arm-fixes-for-v4.8-round2

for you to fetch changes up to 293f293637b55db4f9f522a5a72514e98a541076:

  kvm-arm: Unmap shadow pagetables properly (2016-09-09 12:40:30 +0200)

Thanks!
-Christoffer

---
Marc Zyngier (1):
      arm: KVM: Fix idmap overlap detection when the kernel is idmap'ed

Suzuki K Poulose (1):
      kvm-arm: Unmap shadow pagetables properly

 arch/arm/kvm/arm.c | 2 --
 arch/arm/kvm/mmu.c | 4 +++-
 2 files changed, 3 insertions(+), 3 deletions(-)

             reply	other threads:[~2016-09-09 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 10:54 Christoffer Dall [this message]
2016-09-09 10:54 ` [PULL 1/2] arm: KVM: Fix idmap overlap detection when the kernel is idmap'ed Christoffer Dall
2016-09-09 10:54 ` [PULL 2/2] kvm-arm: Unmap shadow pagetables properly Christoffer Dall
2016-09-09 15:46 ` [PULL 0/2] KVM/ARM Fixes for v4.8 - round #2 Paolo Bonzini

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=20160909105456.8585-1-christoffer.dall@linaro.org \
    --to=christoffer.dall@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).