From: Suresh Warrier <warrier@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: warrier@linux.vnet.ibm.com, paulus@samba.org, mpe@ellerman.id.au
Subject: [PATCH 0/2] Increase number of supported IPI messages
Date: Thu, 29 Oct 2015 18:40:43 -0500 [thread overview]
Message-ID: <1446162045-26496-1-git-send-email-warrier@linux.vnet.ibm.com> (raw)
When a H_IPI hypercall is made, we often need to switch to the
host to poke the VCPU to which the virtual IPI is targeted.
This is because we cannot do a thread wake-up in real mode in
the guest. Peformance tests have shown that this is impacting
several different workloads - from MongoDB to small message
networking.
One solution is to hand off this job of waking the VCPU to a CPU
that is running in the host by sending it a message through the
IPI mechanism from the guest.
Currently, we only support 4 IPI messages and all 4 are already
used for other purposes. This patch set increases the number
of supported IPI messages to 8. It also provides the code to
send an IPI from KVM real-mode since the existing cause_ipi
functions cannot be executed in real-mode.
There is an associated patch set for "KVM: PPC: Book3S HV"
that implements the actual solution to avoid the switch to
host to do the VCPU wakeup.
Suresh Warrier (2):
powerpc/smp: Support more IPI messages
powerpc/smp: Add smp_muxed_ipi_rm_message_pass
arch/powerpc/include/asm/smp.h | 4 ++++
arch/powerpc/kernel/smp.c | 38 ++++++++++++++++++++++++++++++++++----
2 files changed, 38 insertions(+), 4 deletions(-)
--
1.8.3.4
next reply other threads:[~2015-10-29 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 23:40 Suresh Warrier [this message]
2015-10-29 23:40 ` [PATCH 1/2] powerpc/smp: Support more IPI messages Suresh Warrier
2015-10-29 23:40 ` [PATCH 2/2] powerpc/smp: Add smp_muxed_ipi_rm_message_pass Suresh Warrier
2015-11-16 5:53 ` [2/2] " Michael Ellerman
2015-11-16 21:34 ` Suresh E. Warrier
2015-11-17 0:20 ` Michael Ellerman
2015-11-25 19:27 ` Suresh E. Warrier
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=1446162045-26496-1-git-send-email-warrier@linux.vnet.ibm.com \
--to=warrier@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).