All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-fixes-4.19-1 tag
Date: Wed, 22 Aug 2018 12:08:18 +0000	[thread overview]
Message-ID: <20180822120818.GA12224@fergus> (raw)
In-Reply-To: <20180303091717.GA14569@fergus.ozlabs.ibm.com>

Paolo or Radim,

Please do a pull from my kvm-ppc-fixes-4.19-1 tag to get two small
fixes which should go into 4.19.

Thanks,
Paul.

The following changes since commit fd8ca6dac9b45db8503cf508880edd63e039e2f2:

  KVM/x86: Use CC_SET()/CC_OUT in arch/x86/kvm/vmx.c (2018-08-06 18:18:41 +0200)

are available in the git repository at:

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

for you to fetch changes up to 46dec40fb741f00f1864580130779aeeaf24fb3d:

  KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function (2018-08-20 16:05:45 +1000)

----------------------------------------------------------------
PPC KVM fixes for 4.19

Two small fixes for KVM on POWER machines; one fixes a bug where pages
might not get marked dirty, causing guest memory corruption on migration,
and the other fixes a bug causing reads from guest memory to use the
wrong guest real address for very large HPT guests (>256G of memory),
leading to failures in instruction emulation.

----------------------------------------------------------------
Paul Mackerras (2):
      KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()
      KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function

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

  parent reply	other threads:[~2018-08-22 12:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  9:17 [GIT PULL] Please pull my kvm-ppc-fixes-4.16-1 tag Paul Mackerras
2018-03-06 17:08 ` Radim Krčmář
2018-03-14  8:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-2 tag Paul Mackerras
2018-03-15 20:57 ` Paolo Bonzini
2018-03-23  4:46 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-3 tag Paul Mackerras
2018-03-23 17:21 ` Paolo Bonzini
2018-05-24  5:34 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.17-1 tag Paul Mackerras
2018-05-24 17:02 ` Radim Krčmář
2018-08-22 12:08 ` Paul Mackerras [this message]
2018-09-14  9:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-2 tag Paul Mackerras
2018-09-18 13:22 ` Paolo Bonzini
2018-10-05  0:29 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-3 tag Paul Mackerras
2018-10-05  7:43 ` Paolo Bonzini
2018-11-16 10:36 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.20-1 tag Paul Mackerras
2018-11-25 17:54 ` Paolo Bonzini
2019-04-07 22:12 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.1-1 tag Paul Mackerras
2019-04-07 22:12   ` Paul Mackerras
2019-04-18  4:05   ` Paul Mackerras
2019-04-18  4:05     ` Paul Mackerras
2019-04-18 16:53     ` Paolo Bonzini
2019-04-18 16:53       ` Paolo Bonzini
2019-05-30 11:59 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Paul Mackerras
2019-05-30 11:59   ` Paul Mackerras
2019-05-31 22:48   ` Paolo Bonzini
2019-05-31 22:48     ` Paolo Bonzini
2019-08-27  9:53 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag Paul Mackerras
2019-08-27  9:53   ` Paul Mackerras
2019-08-27 15:49   ` Radim Krčmář
2019-08-27 15:49     ` Radim Krčmář
2019-10-21  4:19 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.4-1 tag Paul Mackerras
2019-10-21  4:19   ` Paul Mackerras
2019-10-22 11:12   ` Paolo Bonzini
2019-10-22 11:12     ` Paolo Bonzini
2019-12-19  0:19 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.5-1 tag Paul Mackerras
2019-12-19  0:19   ` Paul Mackerras
2019-12-22 12:18   ` Paolo Bonzini
2019-12-22 12:18     ` Paolo Bonzini
2020-04-20 23:53 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.7-1 tag Paul Mackerras
2020-04-20 23:53   ` Paul Mackerras
2020-04-21 13:37   ` Paolo Bonzini
2020-04-21 13:37     ` 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=20180822120818.GA12224@fergus \
    --to=paulus@ozlabs.org \
    --cc=kvm-ppc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.