kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: [GIT PULL] Please pull my kvm-ppc-fixes branch
Date: Mon, 15 May 2017 18:16:29 +1000	[thread overview]
Message-ID: <20170515081629.GA3691@fergus.ozlabs.ibm.com> (raw)

Paolo,

Please do a pull from my kvm-ppc-fixes branch to get 3 commits that
should go into 4.12.  Two of them fix failures to build for PR KVM
configurations, and one of them fixes a host crash that can occur on
POWER9 with radix guests.

Thanks,
Paul.

The following changes since commit 36c344f3f1ffc0b1b20abd237b7401dc6687ee8f:

  Merge tag 'kvm-arm-for-v4.12-round2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD (2017-05-09 12:51:49 +0200)

are available in the git repository at:

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

for you to fetch changes up to 76d837a4c0f905f98088877d780169d7a14a6b29:

  KVM: PPC: Book3S PR: Don't include SPAPR TCE code on non-pseries platforms (2017-05-12 15:32:30 +1000)

----------------------------------------------------------------
Paul Mackerras (3):
      KVM: PPC: Book3S HV: Add radix checks in real-mode hypercall handlers
      KVM: PPC: Book3S PR: Check copy_to/from_user return values
      KVM: PPC: Book3S PR: Don't include SPAPR TCE code on non-pseries platforms

 arch/powerpc/kvm/Kconfig             |  2 +-
 arch/powerpc/kvm/Makefile            |  4 +--
 arch/powerpc/kvm/book3s_64_vio_hv.c  | 13 +++++++
 arch/powerpc/kvm/book3s_hv_builtin.c |  9 ++++-
 arch/powerpc/kvm/book3s_pr_papr.c    | 70 +++++++++++++++++++++++++++---------
 arch/powerpc/kvm/powerpc.c           |  4 ++-
 6 files changed, 80 insertions(+), 22 deletions(-)

             reply	other threads:[~2017-05-15  8:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  8:16 Paul Mackerras [this message]
2017-05-15  8:32 ` [GIT PULL] Please pull my kvm-ppc-fixes branch Christian Zigotzky
2017-05-16 13:52 ` Radim Krčmář
  -- strict thread matches above, loose matches on Subject: below --
2017-10-19  4:20 Paul Mackerras
2017-10-19 13:11 ` Radim Krčmář
2017-09-14  4:06 Paul Mackerras
2017-08-30  6:21 Paul Mackerras
2017-09-08 14:37 ` Radim Krčmář
2017-09-09 13:38   ` Paolo Bonzini
2017-09-12  4:01     ` Paul Mackerras
2017-08-25  1:38 Paul Mackerras
2017-08-25  7:02 ` Paolo Bonzini
2017-08-25  9:06   ` Paul Mackerras
2017-07-26  4:43 Paul Mackerras
2017-06-20  4:30 Paul Mackerras
2017-06-20 12:39 ` Radim Krčmář
2017-06-20 12:55   ` Paolo Bonzini
2017-06-20 15:17     ` Radim Krčmář
2017-06-20 23:37       ` Paul Mackerras
2017-06-21 10:30         ` Paolo Bonzini
2017-04-06  6:28 Paul Mackerras
2017-04-06 14:37 ` Radim Krčmář
2017-03-02  1:55 Paul Mackerras
2017-03-02 11:00 ` Paolo Bonzini
2017-03-02 21:04 ` Radim Krčmář
2016-03-08 10:54 Paul Mackerras
2015-12-10  3:12 Paul Mackerras
2015-12-11 11:30 ` Paolo Bonzini
2015-11-12  5:35 Paul Mackerras
2015-11-12  9:11 ` 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=20170515081629.GA3691@fergus.ozlabs.ibm.com \
    --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 \
    /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).