From: ehrhardt@linux.vnet.ibm.com
To: linuxppc-dev@ozlabs.org, kvm-ppc@vger.kernel.org
Cc: hollisb@us.ibm.com
Subject: [PATCH 0/3][RFC] kvmppc: paravirtualization interface - guest part v3
Date: Tue, 16 Sep 2008 08:27:27 +0200 [thread overview]
Message-ID: <1221546450-15761-1-git-send-email-ehrhardt@linux.vnet.ibm.com> (raw)
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Version 3 updates:
- guest hypercall infrastructure is now generic (in epapr_hcalls.h)
while the kvm specific functions stay in kvm_para.h
- the hypercalls now use beat style ABI
- dropped the guest coop patch changing wrteei to wrtee (now mfmsr is
rewritten avoiding side effects and a lot of corner cases. Additionally this
does not need any guest cooperation to be effective)
This patch series implements a paravirtualization interface using:
- the device tree mechanism to pass hypervisor informations to the guest
- hypercalls for guest->host calls
- an example exploiter of that interface (magic page)
The device tree format used here (=base for the discussions on
embedded-hypervisor) is the following.
- A node "hypervisor" to show the general availability of some hypervisor data
- flags for features like the example "feature,pv-magicpage"
setting 1 = available, everything else = unavailable
- Some features might need to pass more data and can use an entry in the
device tree like the example of "data,pv-magicpage-size"
The host side of these patches can be found on kvm-ppc@vger.kernel.org
I hope that eventually this guest patch series (that is modifying the ppc boot
process and adding e.g. new ppc fixmaps could go upstream (when discussed
and agreed somewhen) via linuxppc-dev, while the kvm host part will go via
kvm (Avi Kivity).
[patches in series]
[PATCH 1/3] kvmppc: read device tree hypervisor node infrastructure
[PATCH 2/3] kvmppc: add hypercall infrastructure - guest part
[PATCH 3/3] kvmppc: magic page paravirtualization - guest part
---
[diffstat]
arch/powerpc/kernel/kvm.c | 53 +++++++++++++++++++++++++++++++
b/arch/powerpc/kernel/Makefile | 2 +
b/arch/powerpc/kernel/kvm.c | 30 +++++++++++++++++
b/arch/powerpc/kernel/setup_32.c | 3 +
b/arch/powerpc/platforms/44x/Kconfig | 7 ++++
b/include/asm-powerpc/epapr_hcalls.h | 59 +++++++++++++++++++++++++++++++++++
b/include/asm-powerpc/fixmap.h | 10 +++++
b/include/asm-powerpc/kvm_para.h | 43 +++++++++++++++++++++++--
include/asm-powerpc/kvm_para.h | 26 +++++++++++++++
9 files changed, 229 insertions(+), 4 deletions(-)
next reply other threads:[~2008-09-16 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 6:27 ehrhardt [this message]
2008-09-16 6:27 ` [PATCH 1/3] kvmppc: read device tree hypervisor node infrastructure ehrhardt
2008-09-16 6:27 ` [PATCH 2/3] kvmppc: add hypercall infrastructure - guest part v3 ehrhardt
2008-10-13 16:42 ` Kumar Gala
2008-10-13 17:29 ` Hollis Blanchard
2008-10-13 17:44 ` Kumar Gala
2008-09-16 6:27 ` [PATCH 3/3] kvmppc: magic page paravirtualization - guest part ehrhardt
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=1221546450-15761-1-git-send-email-ehrhardt@linux.vnet.ibm.com \
--to=ehrhardt@linux.vnet.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).