public inbox for kvm-ppc@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.1-1 tag
Date: Fri, 22 Feb 2019 16:43:11 +0000	[thread overview]
Message-ID: <91d91855-5018-2774-18ff-e9962e60352f@redhat.com> (raw)
In-Reply-To: <20190222051405.GA2527@blackberry>

On 22/02/19 06:14, Paul Mackerras wrote:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-next-5.1-1 tag to get a PPC KVM
> update for 5.1.  There is nothing major in there, just a collection of
> bug fixes and minor improvements.
> 
> Thanks,
> Paul.
> 
> The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:
> 
>   Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.1-1
> 
> for you to fetch changes up to 0a0c50f771f577b05f5a1ac9867d296d02a5e51c:
> 
>   Merge remote-tracking branch 'remotes/powerpc/topic/ppc-kvm' into kvm-ppc-next (2019-02-22 13:52:30 +1100)
> 
> ----------------------------------------------------------------
> PPC KVM update for 5.1
> 
> There are no major new features this time, just a collection of bug
> fixes and improvements in various areas, including machine check
> handling and context switching of protection-key-related registers.
> 
> ----------------------------------------------------------------
> Alexey Kardashevskiy (2):
>       KVM: PPC: Release all hardware TCE tables attached to a group
>       KVM: PPC: Book3S: Improve KVM reference counting
> 
> Jordan Niethe (1):
>       KVM: PPC: Book3S HV: Fix build failure without IOMMU support
> 
> Masahiro Yamada (1):
>       KVM: PPC: Remove -I. header search paths
> 
> Michael Ellerman (2):
>       KVM: PPC: Book3S HV: Context switch AMR on Power9
>       powerpc/kvm: Save and restore host AMR/IAMR/UAMOR
> 
> Paul Mackerras (5):
>       KVM: PPC: Book3S PR: Add emulation for slbfee. instruction
>       KVM: PPC: Book3S: Allow XICS emulation to work in nested hosts using XIVE
>       KVM: PPC: Book3S HV: Simplify machine check handling
>       powerpc/64s: Better printing of machine check info for guest MCEs
>       Merge remote-tracking branch 'remotes/powerpc/topic/ppc-kvm' into kvm-ppc-next
> 
> Suraj Jitindar Singh (2):
>       KVM: PPC: Book3S HV: Optimise mmio emulation for devices on FAST_MMIO_BUS
>       KVM: PPC: Book3S HV: Add KVM stat largepages_[2M/1G]
> 
> wangbo (1):
>       KVM: PPC: Book3S HV: Replace kmalloc_node+memset with kzalloc_node
> 
>  arch/powerpc/include/asm/kvm_host.h     |  3 ++
>  arch/powerpc/include/asm/kvm_ppc.h      | 17 +++++++-
>  arch/powerpc/include/asm/mce.h          |  2 +-
>  arch/powerpc/kernel/mce.c               |  8 ++--
>  arch/powerpc/kvm/Makefile               |  5 ---
>  arch/powerpc/kvm/book3s.c               | 20 ++++++---
>  arch/powerpc/kvm/book3s_32_mmu.c        |  1 +
>  arch/powerpc/kvm/book3s_64_mmu.c        | 14 ++++++
>  arch/powerpc/kvm/book3s_64_mmu_hv.c     | 18 ++++++++
>  arch/powerpc/kvm/book3s_64_mmu_radix.c  | 15 ++++++-
>  arch/powerpc/kvm/book3s_64_vio.c        |  8 ++--
>  arch/powerpc/kvm/book3s_emulate.c       | 18 ++++++++
>  arch/powerpc/kvm/book3s_hv.c            | 47 +++++++++++++-------
>  arch/powerpc/kvm/book3s_hv_builtin.c    | 14 +++---
>  arch/powerpc/kvm/book3s_hv_ras.c        | 58 ++++++-------------------
>  arch/powerpc/kvm/book3s_hv_rm_xics.c    |  7 +++
>  arch/powerpc/kvm/book3s_hv_rmhandlers.S | 76 +++++++++++++--------------------
>  arch/powerpc/kvm/book3s_rtas.c          |  8 ++--
>  arch/powerpc/kvm/powerpc.c              |  4 +-
>  arch/powerpc/platforms/powernv/opal.c   |  2 +-
>  20 files changed, 206 insertions(+), 139 deletions(-)
> 

Pulled, thanks.

Paolo

  parent reply	other threads:[~2019-02-22 16:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  5:14 [GIT PULL] Please pull my kvm-ppc-next-5.1-1 tag Paul Mackerras
2019-02-22  5:23 ` Masahiro Yamada
2019-02-22  5:52 ` Paul Mackerras
2019-02-22  6:46 ` Masahiro Yamada
2019-02-22  9:46 ` Paul Mackerras
2019-02-22 16:43 ` Paolo Bonzini [this message]
2019-03-01  3:37 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-2 tag Paul Mackerras
2019-03-01  5:21 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-3 tag Paul Mackerras
2019-03-14  3:31 ` Paul Mackerras
2019-03-15 18:13 ` Paolo Bonzini
2019-05-02  4:06 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-1 tag Paul Mackerras
2019-05-09 22:46   ` Paul Mackerras
2019-05-14 10:13 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag Paul Mackerras
2019-05-15 21:40   ` Paolo Bonzini
2019-08-28 23:23 ` [GIT PULL] Please pull my kvm-ppc-next-5.4-1 tag Paul Mackerras
2019-09-06 12:04   ` Paul Mackerras
2019-09-10 14:51     ` Paolo Bonzini
2019-10-31 11:13 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-1 tag Paul Mackerras
2019-10-31 23:36   ` Paolo Bonzini
2019-11-25  0:58 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag Paul Mackerras
2019-11-25 10:29   ` Paolo Bonzini
2019-11-25 23:44     ` Paul Mackerras
2019-11-26  8:52       ` Paolo Bonzini
2020-01-21  3:33 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-1 tag Paul Mackerras
2020-01-21 16:15   ` Paolo Bonzini
2020-01-30  0:54 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-2 tag Paul Mackerras
2020-03-30 23:08 ` [GIT PULL] Please pull my kvm-ppc-next-5.7-1 tag Paul Mackerras
2020-03-31 14:47   ` Paolo Bonzini
2020-06-01 23:53 ` [GIT PULL] Please pull my kvm-ppc-next-5.8-1 tag Paul Mackerras
2020-06-04 18:58   ` Paolo Bonzini
2020-06-11  0:48     ` Paul Mackerras
2020-06-11  1:01       ` Paolo Bonzini
2020-07-28  5:51 ` [GIT PULL] Please pull my kvm-ppc-next-5.9-1 tag Paul Mackerras
2020-08-05  0:02   ` Paul Mackerras
2020-08-07 12:23     ` Paolo Bonzini
2020-09-22  4:19 ` [GIT PULL] Please pull my kvm-ppc-next-5.10-1 tag Paul Mackerras
2020-09-22 12:18   ` Paolo Bonzini
2021-02-11  7:25 ` [GIT PULL] Please pull my kvm-ppc-next-5.12-1 tag Paul Mackerras
2021-02-11 13:00   ` 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=91d91855-5018-2774-18ff-e9962e60352f@redhat.com \
    --to=pbonzini@redhat.com \
    --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