Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>, kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-fixes-5.5-1 tag
Date: Thu, 19 Dec 2019 11:19:12 +1100	[thread overview]
Message-ID: <20191219001912.GA12288@blackberry> (raw)

Paolo,

Please do a pull from my kvm-ppc-fixes-5.5-1 to get one commit which
should go in 5.5.  It fixes a regression introduced in my last pull,
which added an ultravisor call even on systems without an ultravisor.

Thanks,
Paul.

The following changes since commit 7d73710d9ca2564f29d291d0b3badc09efdf25e9:

  kvm: vmx: Stop wasting a page for guest_msrs (2019-12-04 12:23:27 +0100)

are available in the git repository at:

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

for you to fetch changes up to d89c69f42bf0fe42d1f52ea9b3dca15b1ade7601:

  KVM: PPC: Book3S HV: Don't do ultravisor calls on systems without ultravisor (2019-12-18 15:46:34 +1100)

----------------------------------------------------------------
PPC KVM fix for 5.5

- Fix a bug where we try to do an ultracall on a system without an
  ultravisor.

----------------------------------------------------------------
Paul Mackerras (1):
      KVM: PPC: Book3S HV: Don't do ultravisor calls on systems without ultravisor

 arch/powerpc/kvm/book3s_hv.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

             reply	other threads:[~2019-12-19  0:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19  0:19 Paul Mackerras [this message]
2019-12-22 12:18 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.5-1 tag 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=20191219001912.GA12288@blackberry \
    --to=paulus@ozlabs.org \
    --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