From: Stuart Yoder <stuart.yoder@freescale.com>
To: agraf@suse.de, kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Cc: Stuart Yoder <stuart.yoder@freescale.com>
Subject: [PATCH v11 0/8] KVM: PPC: Add ePAPR idle hcall support
Date: Fri, 22 Jun 2012 20:00:09 +0000 [thread overview]
Message-ID: <1340395209-4886-1-git-send-email-stuart.yoder@freescale.com> (raw)
From: Stuart Yoder <stuart.yoder@freescale.com>
This is a reworked version of the v10 patchset I sent out back
in March, address the comments, plus adding some additional
fixes found in further testing.
Liu Yu-B13201 (3):
KVM: PPC: Add support for ePAPR idle hcall in host kernel
KVM: PPC: ev_idle hcall support for e500 guests
PPC: Don't use hardcoded opcode for ePAPR hcall invocation
Scott Wood (1):
powerpc/fsl-soc: use CONFIG_EPAPR_PARAVIRT for hcalls
Stuart Yoder (4):
PPC: epapr: create define for return code value of success
KVM: PPC: use definitions in epapr header for hcalls
KVM: PPC: add pvinfo for hcall opcodes on e500mc/e5500
PPC: select EPAPR_PARAVIRT for all users of epapr hcalls
Documentation/virtual/kvm/api.txt | 7 ++++-
arch/powerpc/include/asm/Kbuild | 1 +
arch/powerpc/include/asm/epapr_hcalls.h | 36 ++++++++++++++++--------------
arch/powerpc/include/asm/fsl_hcalls.h | 36 +++++++++++++++---------------
arch/powerpc/include/asm/kvm_para.h | 21 +++++++++--------
arch/powerpc/kernel/epapr_hcalls.S | 32 +++++++++++++++++++++++++++
arch/powerpc/kernel/epapr_paravirt.c | 11 ++++++++-
arch/powerpc/kernel/kvm.c | 2 +-
arch/powerpc/kvm/powerpc.c | 30 +++++++++++++++++++-------
arch/powerpc/platforms/Kconfig | 1 +
arch/powerpc/sysdev/fsl_msi.c | 9 ++++++-
arch/powerpc/sysdev/fsl_soc.c | 2 +
drivers/tty/Kconfig | 1 +
drivers/virt/Kconfig | 1 +
include/linux/kvm.h | 2 +
15 files changed, 133 insertions(+), 59 deletions(-)
--
1.7.3.4
reply other threads:[~2012-06-22 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1340395209-4886-1-git-send-email-stuart.yoder@freescale.com \
--to=stuart.yoder@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@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