public inbox for kvm-ppc@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>, kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.12-1 tag
Date: Thu, 11 Feb 2021 13:00:08 +0000	[thread overview]
Message-ID: <eb082e35-e202-633d-d3e1-8a2eafcda68d@redhat.com> (raw)
In-Reply-To: <20210211072553.GA2877131@thinks.paulus.ozlabs.org>

On 11/02/21 08:25, Paul Mackerras wrote:
> Paolo,
> 
> Please do a pull from my kvm-ppc-next-5.12-1 tag to get a PPC KVM
> update for 5.12.  This one is quite small, with just one new feature,
> support for the second data watchpoint in POWER10.
> 
> Thanks,
> Paul.
> 
> The following changes since commit 9294b8a12585f8b4ccb9c060b54bab0bd13f24b9:
> 
>    Documentation: kvm: fix warning (2021-02-09 08:42:10 -0500)
> 
> are available in the git repository at:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.12-1
> 
> for you to fetch changes up to 72476aaa469179222b92c380de60c76b4cb9a318:
> 
>    KVM: PPC: Book3S HV: Fix host radix SLB optimisation with hash guests (2021-02-11 17:28:15 +1100)
> 
> ----------------------------------------------------------------
> PPC KVM update for 5.12
> 
> - Support for second data watchpoint on POWER10, from Ravi Bangoria
> - Remove some complex workarounds for buggy early versions of POWER9
> - Guest entry/exit fixes from Nick Piggin and Fabiano Rosas
> 
> ----------------------------------------------------------------
> Fabiano Rosas (2):
>        KVM: PPC: Book3S HV: Save and restore FSCR in the P9 path
>        KVM: PPC: Don't always report hash MMU capability for P9 < DD2.2
> 
> Nicholas Piggin (5):
>        KVM: PPC: Book3S HV: Remove support for running HPT guest on RPT host without mixed mode support
>        KVM: PPC: Book3S HV: Fix radix guest SLB side channel
>        KVM: PPC: Book3S HV: No need to clear radix host SLB before loading HPT guest
>        KVM: PPC: Book3S HV: Use POWER9 SLBIA IH=6 variant to clear SLB
>        KVM: PPC: Book3S HV: Fix host radix SLB optimisation with hash guests
> 
> Paul Mackerras (1):
>        KVM: PPC: Book3S HV: Ensure radix guest has no SLB entries
> 
> Ravi Bangoria (4):
>        KVM: PPC: Book3S HV: Allow nested guest creation when L0 hv_guest_state > L1
>        KVM: PPC: Book3S HV: Rename current DAWR macros and variables
>        KVM: PPC: Book3S HV: Add infrastructure to support 2nd DAWR
>        KVM: PPC: Book3S HV: Introduce new capability for 2nd DAWR
> 
> Yang Li (1):
>        KVM: PPC: remove unneeded semicolon
> 
>   Documentation/virt/kvm/api.rst            |  12 ++
>   arch/powerpc/include/asm/hvcall.h         |  25 ++++-
>   arch/powerpc/include/asm/kvm_book3s_asm.h |  11 --
>   arch/powerpc/include/asm/kvm_host.h       |   7 +-
>   arch/powerpc/include/asm/kvm_ppc.h        |   2 +
>   arch/powerpc/include/uapi/asm/kvm.h       |   2 +
>   arch/powerpc/kernel/asm-offsets.c         |   9 +-
>   arch/powerpc/kvm/book3s_hv.c              | 149 +++++++++++++++----------
>   arch/powerpc/kvm/book3s_hv_builtin.c      | 108 +-----------------
>   arch/powerpc/kvm/book3s_hv_nested.c       |  70 +++++++++---
>   arch/powerpc/kvm/book3s_hv_rmhandlers.S   | 175 ++++++++++++++++--------------
>   arch/powerpc/kvm/booke.c                  |   2 +-
>   arch/powerpc/kvm/powerpc.c                |  14 ++-
>   include/uapi/linux/kvm.h                  |   1 +
>   tools/arch/powerpc/include/uapi/asm/kvm.h |   2 +
>   tools/include/uapi/linux/kvm.h            |   1 +
>   16 files changed, 309 insertions(+), 281 deletions(-)
> 

Pulled, thanks.

Paolo

      reply	other threads:[~2021-02-11 13:00 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
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 [this message]

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=eb082e35-e202-633d-d3e1-8a2eafcda68d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@ozlabs.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