From: Paul Mackerras <paulus@ozlabs.org>
To: kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-next-4.19-1 tag
Date: Tue, 31 Jul 2018 05:56:44 +0000 [thread overview]
Message-ID: <20180731055644.GA12117@fergus> (raw)
In-Reply-To: <20180119044850.GA10633@fergus.ozlabs.ibm.com>
Paolo or Radim,
Please do a pull from my kvm-ppc-next-4.19-1 tag to get a PPC update
for 4.19. There is not much in there, just some code cleanups and bug
fixes.
Michael Ellerman also has some changes that touch arch/powerpc/kvm in
his topic/ppc-kvm branch, which he has merged into his next branch. I
have not pulled them into my tree since there are no conflicts with
the changes in my kvm-ppc-next branch.
Thanks,
Paul.
The following changes since commit 6f0d349d922ba44e4348a17a78ea51b7135965b1:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2018-06-25 15:58:17 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-4.19-1
for you to fetch changes up to b5c6f7607b908b1445f2556c8d2f3b1ec5fc5aa8:
KVM: PPC: Book3S HV: Read kvm->arch.emul_smt_mode under kvm->lock (2018-07-26 15:38:41 +1000)
----------------------------------------------------------------
PPC KVM update for 4.19.
This update adds no new features; it just has some minor code cleanups
and bug fixes, including a fix to allow us to create KVM_MAX_VCPUS
vCPUs on POWER9 in all CPU threading modes.
----------------------------------------------------------------
Alexey Kardashevskiy (1):
KVM: PPC: Book3S: Fix matching of hardware and emulated TCE tables
Nicholas Mc Guire (2):
KVM: PPC: Book3S HV: Add of_node_put() in success path
KVM: PPC: Book3S HV: Fix constant size warning
Paul Mackerras (2):
KVM: PPC: Book3S HV: Allow creating max number of VCPUs on POWER9
KVM: PPC: Book3S HV: Read kvm->arch.emul_smt_mode under kvm->lock
Sam Bobroff (1):
KVM: PPC: Book3S HV: Pack VCORE IDs to access full VCPU ID space
Simon Guo (1):
KVM: PPC: Remove mmio_vsx_tx_sx_enabled in KVM MMIO emulation
arch/powerpc/include/asm/kvm_book3s.h | 47 +++++++++++++++++++++++++++++++++++
arch/powerpc/include/asm/kvm_host.h | 26 +++++++++++--------
arch/powerpc/include/asm/reg.h | 2 +-
arch/powerpc/kvm/book3s_64_vio.c | 5 ++--
arch/powerpc/kvm/book3s_hv.c | 42 +++++++++++++++++++++----------
arch/powerpc/kvm/book3s_xive.c | 19 ++++++++------
arch/powerpc/kvm/emulate_loadstore.c | 7 +++---
arch/powerpc/kvm/powerpc.c | 30 +++++++++++-----------
8 files changed, 125 insertions(+), 53 deletions(-)
next prev parent reply other threads:[~2018-07-31 5:56 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 ` Paul Mackerras [this message]
2018-08-02 11:56 ` [GIT PULL] Please pull my kvm-ppc-next-4.19-1 tag 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 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-1 tag Paul Mackerras
2018-12-20 13:58 ` 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=20180731055644.GA12117@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox