From: Paul Mackerras <paulus@ozlabs.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag
Date: Tue, 14 May 2019 20:13:27 +1000 [thread overview]
Message-ID: <20190514101327.GA13522@blackberry> (raw)
Paolo, Radim,
I have added 3 more commits to my kvm-ppc-next tree, for various fixes
that have come in recently. There is one bug fix, one spelling fix,
and one commit that removes some code that does nothing. The net
result is 12 fewer lines of code in the kernel. :)
If you pull this tag and not the earlier kvm-ppc-next-5.2-1 tag, you
might want to include the text from that tag in the commit message.
That text is:
"
PPC KVM update for 5.2
* Support for guests to access the new POWER9 XIVE interrupt controller
hardware directly, reducing interrupt latency and overhead for guests.
* In-kernel implementation of the H_PAGE_INIT hypercall.
* Reduce memory usage of sparsely-populated IOMMU tables.
* Several bug fixes.
"
Thanks,
Paul.
The following changes since commit 0caecf5b00199636eb2d32201199ecd6be52558d:
KVM: PPC: Book3S HV: XIVE: Clear escalation interrupt pointers on device close (2019-04-30 19:41:01 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.2-2
for you to fetch changes up to 4894fbcce856635c9ab79f44e50826e86bb92110:
KVM: PPC: Book3S: Remove useless checks in 'release' method of KVM device (2019-05-14 12:06:03 +1000)
----------------------------------------------------------------
Second PPC KVM update for 5.2
- Fix a bug, fix a spelling mistake, remove some useless code.
----------------------------------------------------------------
Colin Ian King (1):
KVM: PPC: Book3S HV: XIVE: Fix spelling mistake "acessing" -> "accessing"
Cédric Le Goater (1):
KVM: PPC: Book3S: Remove useless checks in 'release' method of KVM device
Paul Mackerras (1):
KVM: PPC: Book3S HV: Make sure to load LPID for radix VCPUs
arch/powerpc/kvm/book3s_hv_rmhandlers.S | 6 ------
arch/powerpc/kvm/book3s_xive_native.c | 2 +-
virt/kvm/kvm_main.c | 6 ------
3 files changed, 1 insertion(+), 13 deletions(-)
next reply other threads:[~2019-05-14 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 10:13 Paul Mackerras [this message]
2019-05-15 21:40 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag 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=20190514101327.GA13522@blackberry \
--to=paulus@ozlabs.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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