Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: [GIT PULL] Please pull my kvm-ppc-fixes-5.1-1 tag
Date: Mon, 8 Apr 2019 08:12:25 +1000	[thread overview]
Message-ID: <20190407221225.GA31464@blackberry> (raw)

Paolo or Radim,

Please do a pull from my kvm-ppc-fixes-5.1-1 tag to get two commits
which fix bugs which could potentially cause hangs or corruption in
the host.

Thanks,
Paul.

The following changes since commit 690edec54cbaa0e98dc592aae6864272f48f3c84:

  Merge tag 'kvmarm-fixes-for-5.1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into kvm-master (2019-03-28 19:07:30 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-fixes-5.1-1

for you to fetch changes up to 345077c8e172c255ea0707214303ccd099e5656b:

  KVM: PPC: Book3S: Protect memslots while validating user address (2019-04-05 14:37:24 +1100)

----------------------------------------------------------------
KVM/PPC fixes for 5.1

- Fix host hang in the HTM assist code for POWER9
- Take srcu read lock around memslot lookup

----------------------------------------------------------------
Alexey Kardashevskiy (1):
      KVM: PPC: Book3S: Protect memslots while validating user address

Suraj Jitindar Singh (1):
      KVM: PPC: Book3S HV: Perserve PSSCR FAKE_SUSPEND bit on guest exit

 arch/powerpc/kvm/book3s_64_vio.c | 6 +++---
 arch/powerpc/kvm/book3s_hv.c     | 4 +++-
 2 files changed, 6 insertions(+), 4 deletions(-)

             reply	other threads:[~2019-04-07 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 22:12 Paul Mackerras [this message]
2019-04-18  4:05 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.1-1 tag Paul Mackerras
2019-04-18 16:53   ` 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=20190407221225.GA31464@blackberry \
    --to=paulus@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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