From: Matt Evans <matt@ozlabs.org>
To: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: [PATCH 0/8] kvm tools SPAPR PPC64 support
Date: Tue, 06 Dec 2011 15:05:48 +1100 [thread overview]
Message-ID: <4EDD949C.4010206@ozlabs.org> (raw)
Hi,
This set of patches builds upon the prep-work of the previous set and adds
support to kvmtool for PPC64 SPAPR-based guests, i.e. an environment akin to an
LPAR on IBM's pSeries machines.
This support is not yet fully-featured but, in a basic state, works well.
The guests have a functional but no-frills experience, with:
- SMP guests
- HV console (or RTAS console, for udbg)
- Net, block over virtio-pci
- No PAPR VIO/VSCSI/VNET yet
- No fancyfeatures like migration yet
Though minimal, guests are quite stable.
There are obvious areas for future improvement:
- Non-VRMA RMAs aren't supported, meaning POWER7-only for the moment
- Other CPU-specific details are currently assumed (e.g. available page sizes);
work is required to determine host capabilities and pass these up.
- Support SLOF
- Maybe support VIO
- Some hypercalls used by partition firmware/SLOF (not the kernel) are
unimplemented
- Fancy PCI (e.g. passthrough)
- Currently KVM_NR_CPUs is arbitrarily fixed at 255, and could be higher.
Guests with this many CPUs boot fine.
Some PPC KVM kernel-side features aren't implemented yet and have required
kvmtool workarounds; mmio coalescing isn't supported and lack of ioeventfds
requires virtio to gracefully fall back when it fails to register one.
Cheers,
Matt
Matt Evans (8):
kvm tools: Add initial SPAPR PPC64 architecture support
kvm tools: Generate SPAPR PPC64 guest device tree
kvm tools: Add SPAPR PPC64 hcall & rtascall structure
kvm tools: Add SPAPR PPC64 HV console
kvm tools: Add PPC64 XICS interrupt controller support
kvm tools: Add PPC64 PCI Host Bridge
kvm tools: Add PPC64 kvm_cpu__emulate_io()
kvm tools: Make virtio-pci's ioeventfd__add_event() fall back
gracefully if ioeventfds unavailable
tools/kvm/Makefile | 16 +
tools/kvm/include/kvm/ioeventfd.h | 3 +-
tools/kvm/ioeventfd.c | 12 +-
tools/kvm/kvm.c | 3 +
tools/kvm/powerpc/include/kvm/barrier.h | 6 +
tools/kvm/powerpc/include/kvm/kvm-arch.h | 74 ++++
tools/kvm/powerpc/include/kvm/kvm-cpu-arch.h | 48 +++
tools/kvm/powerpc/ioport.c | 18 +
tools/kvm/powerpc/irq.c | 62 +++
tools/kvm/powerpc/kvm-cpu.c | 281 ++++++++++++++
tools/kvm/powerpc/kvm.c | 466 +++++++++++++++++++++++
tools/kvm/powerpc/spapr.h | 316 +++++++++++++++
tools/kvm/powerpc/spapr_hcall.c | 151 ++++++++
tools/kvm/powerpc/spapr_hvcons.c | 101 +++++
tools/kvm/powerpc/spapr_hvcons.h | 19 +
tools/kvm/powerpc/spapr_pci.c | 429 +++++++++++++++++++++
tools/kvm/powerpc/spapr_pci.h | 38 ++
tools/kvm/powerpc/spapr_rtas.c | 226 +++++++++++
tools/kvm/powerpc/xics.c | 529 ++++++++++++++++++++++++++
tools/kvm/powerpc/xics.h | 23 ++
tools/kvm/virtio/pci.c | 11 +-
21 files changed, 2827 insertions(+), 5 deletions(-)
create mode 100644 tools/kvm/powerpc/include/kvm/barrier.h
create mode 100644 tools/kvm/powerpc/include/kvm/kvm-arch.h
create mode 100644 tools/kvm/powerpc/include/kvm/kvm-cpu-arch.h
create mode 100644 tools/kvm/powerpc/ioport.c
create mode 100644 tools/kvm/powerpc/irq.c
create mode 100644 tools/kvm/powerpc/kvm-cpu.c
create mode 100644 tools/kvm/powerpc/kvm.c
create mode 100644 tools/kvm/powerpc/spapr.h
create mode 100644 tools/kvm/powerpc/spapr_hcall.c
create mode 100644 tools/kvm/powerpc/spapr_hvcons.c
create mode 100644 tools/kvm/powerpc/spapr_hvcons.h
create mode 100644 tools/kvm/powerpc/spapr_pci.c
create mode 100644 tools/kvm/powerpc/spapr_pci.h
create mode 100644 tools/kvm/powerpc/spapr_rtas.c
create mode 100644 tools/kvm/powerpc/xics.c
create mode 100644 tools/kvm/powerpc/xics.h
reply other threads:[~2011-12-06 4:05 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=4EDD949C.4010206@ozlabs.org \
--to=matt@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).