From: Paul Mackerras <paulus@ozlabs.org>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.9-1 tag
Date: Wed, 05 Aug 2020 00:02:21 +0000 [thread overview]
Message-ID: <20200805000221.GA808843@thinks.paulus.ozlabs.org> (raw)
In-Reply-To: <20200728055100.GA2460422@thinks.paulus.ozlabs.org>
On Tue, Jul 28, 2020 at 03:51:00PM +1000, Paul Mackerras wrote:
> Paolo,
>
> Please do a pull from my kvm-ppc-next-5.9-1 tag to get a PPC KVM
> update for 5.9. It's another relatively small update this time, the
> main thing being a series to improve the startup time for secure VMs
> and make memory hotplug work in secure VMs.
Hi Paolo,
Did this get missed?
Thanks,
Paul.
> Thanks,
> Paul.
>
> The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
>
> Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.9-1
>
> for you to fetch changes up to 81ab595ddd3c3036806b460526e1fbc5b271ff33:
>
> KVM: PPC: Book3S HV: Rework secure mem slot dropping (2020-07-28 12:34:52 +1000)
>
> ----------------------------------------------------------------
> PPC KVM update for 5.9
>
> - Improvements and bug-fixes for secure VM support, giving reduced startup
> time and memory hotplug support.
> - Locking fixes in nested KVM code
> - Increase number of guests supported by HV KVM to 4094
> - Preliminary POWER10 support
>
> ----------------------------------------------------------------
> Alexey Kardashevskiy (1):
> KVM: PPC: Protect kvm_vcpu_read_guest with srcu locks
>
> Alistair Popple (1):
> KVM: PPC: Book3SHV: Enable support for ISA v3.1 guests
>
> Cédric Le Goater (1):
> KVM: PPC: Book3S HV: Increase KVMPPC_NR_LPIDS on POWER8 and POWER9
>
> Laurent Dufour (3):
> KVM: PPC: Book3S HV: Migrate hot plugged memory
> KVM: PPC: Book3S HV: Move kvmppc_svm_page_out up
> KVM: PPC: Book3S HV: Rework secure mem slot dropping
>
> Ram Pai (4):
> KVM: PPC: Book3S HV: Fix function definition in book3s_hv_uvmem.c
> KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
> KVM: PPC: Book3S HV: Track the state GFNs associated with secure VMs
> KVM: PPC: Book3S HV: In H_SVM_INIT_DONE, migrate remaining normal-GFNs to secure-GFNs
>
> Tianjia Zhang (1):
> KVM: PPC: Clean up redundant kvm_run parameters in assembly
>
> Documentation/powerpc/ultravisor.rst | 3 +
> arch/powerpc/include/asm/kvm_book3s_uvmem.h | 14 +
> arch/powerpc/include/asm/kvm_ppc.h | 2 +-
> arch/powerpc/include/asm/reg.h | 4 +-
> arch/powerpc/kvm/book3s_64_mmu_hv.c | 8 +-
> arch/powerpc/kvm/book3s_64_mmu_radix.c | 4 +
> arch/powerpc/kvm/book3s_hv.c | 26 +-
> arch/powerpc/kvm/book3s_hv_nested.c | 30 +-
> arch/powerpc/kvm/book3s_hv_uvmem.c | 698 +++++++++++++++++++++-------
> arch/powerpc/kvm/book3s_interrupts.S | 56 ++-
> arch/powerpc/kvm/book3s_pr.c | 9 +-
> arch/powerpc/kvm/book3s_rtas.c | 2 +
> arch/powerpc/kvm/booke.c | 9 +-
> arch/powerpc/kvm/booke_interrupts.S | 9 +-
> arch/powerpc/kvm/bookehv_interrupts.S | 10 +-
> arch/powerpc/kvm/powerpc.c | 5 +-
> 16 files changed, 646 insertions(+), 243 deletions(-)
next prev parent reply other threads:[~2020-08-05 0:02 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 [this message]
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=20200805000221.GA808843@thinks.paulus.ozlabs.org \
--to=paulus@ozlabs.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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