From: Vaibhav Jain <vaibhav@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org
Cc: mikey@neuling.org, sbhat@linux.ibm.com,
amachhiw@linux.vnet.ibm.com, Jordan Niethe <jniethe5@gmail.com>,
gautam@linux.ibm.com, Nicholas Piggin <npiggin@gmail.com>,
David.Laight@ACULAB.COM, kconsul@linux.vnet.ibm.com,
vaibhav <vajain21@vajain21.in.ibm.com>,
Vaibhav Jain <vaibhav@linux.ibm.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: [PATCH 00/12] KVM: PPC: Nested APIv2 : Performance improvements
Date: Fri, 1 Dec 2023 18:56:05 +0530 [thread overview]
Message-ID: <20231201132618.555031-1-vaibhav@linux.ibm.com> (raw)
From: vaibhav <vajain21@vajain21.in.ibm.com>
This patch series introduces series of performance improvements to recently
added support for Nested APIv2 PPC64 Guests via [1]. Details for Nested
APIv2 for PPC64 Guests is available in Documentation/powerpc/kvm-nested.rst.
This patch series introduces various optimizations for a Nested APIv2
guests namely:
* Reduce the number times L1 hypervisor requests for L2 state from L0.
* Register the L2 VPA with L1
* Optimizing interrupt delivery of some interrupt types.
* Optimize emulation of mmio loads/stores for L2 in L1.
The hcalls needed for testing these patches have been implemented in the
spapr qemu model and is available at [2].
There are scripts available to assist in setting up an environment for
testing nested guests at [3].
These patches are consequence of insights from on going performance
engineering effort for improving performance of Nested APIv2
Guests. Special thanks goes to:
* Gautam Menghani
* Jordan Niethe
* Nicholas Piggin
* Vaidyanathan Srinivasan
Refs:
[1] https://lore.kernel.org/all/20230905034658.82835-1-jniethe5@gmail.com
[2] https://github.com/planetharsh/qemu/tree/upstream-0714-kop
[3] https://github.com/iamjpn/kvm-powervm-test
Jordan Niethe (11):
KVM: PPC: Book3S HV nestedv2: Invalidate RPT before deleting a guest
KVM: PPC: Book3S HV nestedv2: Avoid reloading the tb offset
KVM: PPC: Book3S HV nestedv2: Do not check msr on hcalls
KVM: PPC: Book3S HV nestedv2: Get the PID only if needed to copy
tofrom a guest
KVM: PPC: Book3S HV nestedv2: Ensure LPCR_MER bit is passed to the L0
KVM: PPC: Book3S HV nestedv2: Do not inject certain interrupts
KVM: PPC: Book3S HV nestedv2: Avoid msr check in
kvmppc_handle_exit_hv()
KVM: PPC: Book3S HV nestedv2: Do not call H_COPY_TOFROM_GUEST
KVM: PPC: Book3S HV nestedv2: Register the VPA with the L0
KVM: PPC: Reduce reliance on analyse_instr() in mmio emulation
KVM: PPC: Book3S HV nestedv2: Do not cancel pending decrementer
exception
Nicholas Piggin (1):
KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with
MSR_EE
arch/powerpc/include/asm/kvm_book3s.h | 10 +++-
arch/powerpc/include/asm/kvm_book3s_64.h | 1 +
arch/powerpc/kvm/book3s.c | 4 +-
arch/powerpc/kvm/book3s_64_mmu_radix.c | 7 ++-
arch/powerpc/kvm/book3s_hv.c | 72 +++++++++++++++++-------
arch/powerpc/kvm/book3s_hv_nested.c | 2 +-
arch/powerpc/kvm/book3s_hv_nestedv2.c | 29 ++++++++++
arch/powerpc/kvm/emulate_loadstore.c | 21 ++++---
8 files changed, 107 insertions(+), 39 deletions(-)
--
2.42.0
next reply other threads:[~2023-12-01 13:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 13:26 Vaibhav Jain [this message]
2023-12-01 13:26 ` [PATCH 01/12] KVM: PPC: Book3S HV nestedv2: Invalidate RPT before deleting a guest Vaibhav Jain
2023-12-07 9:15 ` Aneesh Kumar K.V
2023-12-08 13:45 ` Vaibhav Jain
2023-12-15 16:12 ` Aneesh Kumar K.V
2023-12-18 4:54 ` Vaibhav Jain
2023-12-01 13:26 ` [PATCH 02/12] KVM: PPC: Book3S HV nestedv2: Avoid reloading the tb offset Vaibhav Jain
2023-12-01 13:26 ` [PATCH 03/12] KVM: PPC: Book3S HV nestedv2: Do not check msr on hcalls Vaibhav Jain
2023-12-01 13:26 ` [PATCH 04/12] KVM: PPC: Book3S HV nestedv2: Get the PID only if needed to copy tofrom a guest Vaibhav Jain
2023-12-01 13:26 ` [PATCH 05/12] KVM: PPC: Book3S HV nestedv2: Ensure LPCR_MER bit is passed to the L0 Vaibhav Jain
2023-12-01 13:26 ` [PATCH 06/12] KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE Vaibhav Jain
2023-12-01 13:26 ` [PATCH 07/12] KVM: PPC: Book3S HV nestedv2: Do not inject certain interrupts Vaibhav Jain
2023-12-01 13:26 ` [PATCH 08/12] KVM: PPC: Book3S HV nestedv2: Avoid msr check in kvmppc_handle_exit_hv() Vaibhav Jain
2023-12-01 13:26 ` [PATCH 09/12] KVM: PPC: Book3S HV nestedv2: Do not call H_COPY_TOFROM_GUEST Vaibhav Jain
2023-12-08 8:15 ` Aneesh Kumar K.V
2023-12-11 3:56 ` Vaibhav Jain
2023-12-11 4:01 ` Aneesh Kumar K.V
2023-12-18 7:02 ` Vaibhav Jain
2023-12-18 7:29 ` Aneesh Kumar K.V
2023-12-01 13:26 ` [PATCH 10/12] KVM: PPC: Book3S HV nestedv2: Register the VPA with the L0 Vaibhav Jain
2023-12-01 13:26 ` [PATCH 11/12] KVM: PPC: Reduce reliance on analyse_instr() in mmio emulation Vaibhav Jain
2023-12-01 13:26 ` [PATCH 12/12] KVM: PPC: Book3S HV nestedv2: Do not cancel pending decrementer exception Vaibhav Jain
2023-12-21 10:44 ` [PATCH 00/12] KVM: PPC: Nested APIv2 : Performance improvements Michael Ellerman
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=20231201132618.555031-1-vaibhav@linux.ibm.com \
--to=vaibhav@linux.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=amachhiw@linux.vnet.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=jniethe5@gmail.com \
--cc=kconsul@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=sbhat@linux.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=vajain21@vajain21.in.ibm.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;
as well as URLs for NNTP newsgroup(s).