Kernel KVM-PPC virtualization development
 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-next-4.21-1 tag
Date: Tue, 18 Dec 2018 03:05:00 +0000	[thread overview]
Message-ID: <20181218030500.GA29160@blackberry> (raw)
In-Reply-To: <20180119044850.GA10633@fergus.ozlabs.ibm.com>

Paolo or Radim,

Please do a pull from my kvm-ppc-next-4.21-1 tag to get a PPC KVM
update for 4.21.  The main new thing this time is an improvement to
the nested HV KVM code so that if you have a nested hypervisor that
has a PCI device which is actually emulated by the level 0 hypervisor,
level 1 can pass that through to level 2 using VFIO and the accesses
to the device by level 2 will be emulated by level 0 and the results
passed down to level 2 correctly.

Thanks,
Paul.

The following changes since commit fd65d3142f734bc4376053c8d75670041903134d:

  kvm: svm: Ensure an IBPB on all affected CPUs when freeing a vmcb (2018-11-27 12:50:42 +0100)

are available in the git repository at:

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

for you to fetch changes up to 95d386c2d2e7660a6447df1507a9845665dab7d8:

  KVM: PPC: Book3S HV: Allow passthrough of an emulated device to an L3 guest (2018-12-17 11:33:50 +1100)

----------------------------------------------------------------
PPC KVM update for 4.21

The main new feature this time is support in HV nested KVM for passing
a device that is emulated by a level 0 hypervisor and presented to
level 1 as a PCI device through to a level 2 guest using VFIO.

Apart from that there are improvements for migration of radix guests
under HV KVM and some other fixes and cleanups.

----------------------------------------------------------------
Bharata B Rao (1):
      KVM: PPC: Pass change type down to memslot commit function

Paul Mackerras (4):
      KVM: PPC: Book3S HV: Fix race between kvm_unmap_hva_range and MMU mode switch
      KVM: PPC: Book3S HV: Map single pages when doing dirty page logging
      KVM: PPC: Book3S HV: Cleanups - constify memslots, fix comments
      KVM: PPC: Book3S HV: Flush guest mappings when turning dirty tracking on/off

Suraj Jitindar Singh (9):
      KVM: PPC: Book3S PR: Set hflag to indicate that POWER9 supports 1T segments
      KVM: PPC: Book3S: Only report KVM_CAP_SPAPR_TCE_VFIO on powernv machines
      KVM: PPC: Book3S HV: Add function kvmhv_vcpu_is_radix()
      KVM: PPC: Book3S HV: Implement functions to access quadrants 1 & 2
      KVM: PPC: Add load_from_eaddr and store_to_eaddr to the kvmppc_ops struct
      KVM: PPC: Update kvmppc_st and kvmppc_ld to use quadrants
      KVM: PPC: Book3S HV: Allow passthrough of an emulated device to an L2 guest
      KVM: PPC: Book3S: Introduce new hcall H_COPY_TOFROM_GUEST to access quadrants 1 & 2
      KVM: PPC: Book3S HV: Allow passthrough of an emulated device to an L3 guest

Yangtao Li (1):
      KVM: PPC: Book3S HV: Change to use DEFINE_SHOW_ATTRIBUTE macro

 arch/powerpc/include/asm/hvcall.h        |   1 +
 arch/powerpc/include/asm/kvm_book3s.h    |  21 +++--
 arch/powerpc/include/asm/kvm_book3s_64.h |  15 +++-
 arch/powerpc/include/asm/kvm_host.h      |   3 +
 arch/powerpc/include/asm/kvm_ppc.h       |  10 ++-
 arch/powerpc/kernel/exceptions-64s.S     |   9 +++
 arch/powerpc/kvm/book3s.c                |   5 +-
 arch/powerpc/kvm/book3s_64_mmu_hv.c      |  12 ++-
 arch/powerpc/kvm/book3s_64_mmu_radix.c   | 134 +++++++++++++++++++++++++++++--
 arch/powerpc/kvm/book3s_hv.c             |  95 +++++++++++++++++++---
 arch/powerpc/kvm/book3s_hv_nested.c      | 116 ++++++++++++++++++++++++--
 arch/powerpc/kvm/book3s_hv_rm_mmu.c      |   2 +-
 arch/powerpc/kvm/book3s_pr.c             |   4 +-
 arch/powerpc/kvm/book3s_xics.c           |  12 +--
 arch/powerpc/kvm/book3s_xive.c           |  12 +--
 arch/powerpc/kvm/booke.c                 |   3 +-
 arch/powerpc/kvm/powerpc.c               |  33 +++++++-
 arch/powerpc/mm/fault.c                  |   1 +
 18 files changed, 418 insertions(+), 70 deletions(-)

  parent reply	other threads:[~2018-12-18  3:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  4:48 [GIT PULL] Please pull my kvm-ppc-next-4.16-1 tag Paul Mackerras
2018-02-01 15:17 ` Radim Krčmář
2018-02-09  9:41 ` [GIT PULL] Please pull my kvm-ppc-next-4.16-2 tag Paul Mackerras
2018-02-10 14:52   ` Radim Krčmář
2018-03-29  5:38 ` [GIT PULL] Please pull my kvm-ppc-next-4.17-1 tag Paul Mackerras
2018-03-29 20:34 ` Radim Krčmář
2018-06-04  1:27 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-1 tag Paul Mackerras
2018-06-13  5:51 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-2 tag Paul Mackerras
2018-06-13 16:22 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-1 tag Paolo Bonzini
2018-06-13 21:52 ` Paul Mackerras
2018-07-31  5:56 ` [GIT PULL] Please pull my kvm-ppc-next-4.19-1 tag Paul Mackerras
2018-08-02 11:56 ` Paolo Bonzini
2018-10-10  5:55 ` [GIT PULL] Please pull my kvm-ppc-next-4.20-1 tag Paul Mackerras
2018-10-10 16:38 ` Paolo Bonzini
2018-10-20 10:53 ` [GIT PULL] Please pull my kvm-ppc-next-4.20-2 tag Paul Mackerras
2018-10-21  9:47 ` Paolo Bonzini
2018-12-18  3:05 ` Paul Mackerras [this message]
2018-12-20 13:58 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-1 tag Radim Krčmář
2018-12-21  4:24 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-2 tag Paul Mackerras
2018-12-21 10:48 ` 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=20181218030500.GA29160@blackberry \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox