From: Joao Martins <joao.m.martins@oracle.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Ankur Arora" <ankur.a.arora@oracle.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Joao Martins" <joao.m.martins@oracle.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: [PATCH RFC 00/39] x86/KVM: Xen HVM guest support
Date: Wed, 20 Feb 2019 20:15:30 +0000 [thread overview]
Message-ID: <20190220201609.28290-1-joao.m.martins@oracle.com> (raw)
Hey,
Presented herewith a series that allows KVM to boot Xen x86 HVM guests (with their
respective frontends and backends). On the hypervisor side, the approach is to keep
the implementation similar to how HyperV was done on x86 KVM. On the backend driver
side, the intent is to reuse Xen support.
Note that this is an RFC so there are bugs and room for improvement. The intent
is to get overall feedback before proceeding further.
Running Xen guests on KVM, enables the following use-cases:
* Run unmodified Xen HVM images;
* Facilitate development/testing of Xen guests and Xen PV drivers;
There has been a similar proposal in the past with Xenner, albeit this work
has the following advantages over it:
* Allows use of existing Xen PV drivers such as block, net etc, both as
frontends and backends;
* Xen tooling will see the same UABI as on Xen. This means things like
xenstored, xenstore-list, xenstore-read run unmodified. Optionally,
userspace VMM can emulate xenstore operations;
This work is divided in two parts:
1. Xen HVM ABI support (patches 1 - 16)
Support the necessary mechanisms to allow HVM guests to
boot *without* PV frontends exposed to the guest.
We start by intercepting hypercalls made by the guest, followed
by event channel IPIs/VIRQs (for PV IPI, timers, spinlocks),
pvclock and steal clock.
Ankur Arora (1):
KVM: x86/xen: support upcall vector
Boris Ostrovsky (1):
KVM: x86/xen: handle PV spinlocks slowpath
Joao Martins (14):
KVM: x86: fix Xen hypercall page msr handling
KVM: x86/xen: intercept xen hypercalls if enabled
KVM: x86/xen: register shared_info page
KVM: x86/xen: setup pvclock updates
KVM: x86/xen: update wallclock region
KVM: x86/xen: register vcpu info
KVM: x86/xen: register vcpu time info region
KVM: x86/xen: register steal clock
KVM: x86: declare Xen HVM guest capability
KVM: x86/xen: evtchn signaling via eventfd
KVM: x86/xen: store virq when assigning evtchn
KVM: x86/xen: handle PV timers oneshot mode
KVM: x86/xen: handle PV IPI vcpu yield
KVM: x86: declare Xen HVM evtchn offload capability
Documentation/virtual/kvm/api.txt | 23 ++
arch/x86/include/asm/kvm_host.h | 46 ++++
arch/x86/kvm/Makefile | 2 +-
arch/x86/kvm/irq.c | 25 ++-
arch/x86/kvm/irq_comm.c | 11 +
arch/x86/kvm/trace.h | 33 +++
arch/x86/kvm/x86.c | 60 +++++-
arch/x86/kvm/x86.h | 1 +
arch/x86/kvm/xen.c | 1025 +++++++++++++++++++++++++++++
arch/x86/kvm/xen.h | 48 +++++
include/linux/kvm_host.h | 24 +++
include/uapi/linux/kvm.h | 73 ++++++-
12 files changed, 1361 insertions(+), 10 deletions(-)
2. PV Driver support (patches 17 - 39)
We start by redirecting hypercalls from the backend to routines
which emulate the behaviour that PV backends expect i.e. grant
table and interdomain events. Next, we add support for late
initialization of xenbus, followed by implementing
frontend/backend communication mechanisms (i.e. grant tables and
interdomain event channels). Finally, introduce xen-shim.ko,
which will setup a limited Xen environment. This uses the added
functionality of Xen specific shared memory (grant tables) and
notifications (event channels).
Note that patch 19 is useful to Xen on its own.
Ankur Arora (11):
x86/xen: export vcpu_info and shared_info
x86/xen: make hypercall_page generic
KVM: x86/xen: backend hypercall support
KVM: x86/xen: grant map support
KVM: x86/xen: grant unmap support
KVM: x86/xen: interdomain evtchn support
KVM: x86/xen: evtchn unmask support
KVM: x86/xen: add additional evtchn ops
xen-shim: introduce shim domain driver
xen/gntdev: xen_shim_domain() support
xen/xenbus: xen_shim_domain() support
Joao Martins (12):
xen/xenbus: xenbus uninit support
xen-blkback: module_exit support
KVM: x86/xen: domid allocation
KVM: x86/xen: grant table init
KVM: x86/xen: grant table grow support
KVM: x86/xen: grant copy support
xen/balloon: xen_shim_domain() support
xen/grant-table: xen_shim_domain() support
drivers/xen: xen_shim_domain() support
xen-netback: xen_shim_domain() support
xen-blkback: xen_shim_domain() support
KVM: x86: declare Xen HVM Dom0 capability
[See the entire series diffstat at the end]
There are additional Qemu patches to take advantage of this (and
they are available here[0][1]). An example on how you could run it would be:
$ ./x86_64-softmmu/qemu-system-x86_64 -nodefaults -serial mon:stdio \
-machine xenfv,accel=kvm \
-cpu host,-kvm,+xen,xen-major-version=4,xen-minor-version=4,+xen-vapic,+xen-pvclock \
-kernel /path/to/kernel -m 16G -smp 16,sockets=1,cores=16,threads=1,maxcpus=16 \
-append "earlyprintk=ttyS0 console=tty0 console=ttyS0" \
-device xen-platform -device usb-ehci -device usb-tablet,bus=usb-bus.0 -vnc :0 -k pt \
-netdev type=tap,id=net1,ifname=vif1.0,script=qemu-ifup \
-device xen-nic,netdev=net1,mac=52:54:00:12:34:56,backendtype=vif,backend=0 \
-drive file=/path/to/image.img,format=raw,id=legacy,if=ide \
-blockdev file,node-name=drive,filename=/path/to/image.img,locking=off \
-device xen-disk,vdev=xvda,drive=drive,backendtype=vbd
Naturally other options are still at your disposal (e.g. booting with q35
platform, or with virtio, etc).
Thoughts?
Cheers,
Joao
[0] https://www.github.com/jpemartins/qemu xen-shim-rfc
[1] https://www.github.com/jpemartins/linux xen-shim-rfc
Documentation/virtual/kvm/api.txt | 33 +
arch/x86/include/asm/kvm_host.h | 88 ++
arch/x86/include/asm/xen/hypercall.h | 12 +-
arch/x86/kvm/Kconfig | 10 +
arch/x86/kvm/Makefile | 3 +-
arch/x86/kvm/irq.c | 25 +-
arch/x86/kvm/irq_comm.c | 11 +
arch/x86/kvm/trace.h | 33 +
arch/x86/kvm/x86.c | 66 +-
arch/x86/kvm/x86.h | 1 +
arch/x86/kvm/xen-asm.S | 66 +
arch/x86/kvm/xen-shim.c | 138 ++
arch/x86/kvm/xen.c | 2262 ++++++++++++++++++++++++++++++
arch/x86/kvm/xen.h | 55 +
arch/x86/xen/enlighten.c | 49 +
arch/x86/xen/enlighten_hvm.c | 3 +-
arch/x86/xen/enlighten_pv.c | 1 +
arch/x86/xen/enlighten_pvh.c | 3 +-
arch/x86/xen/xen-asm_32.S | 2 +-
arch/x86/xen/xen-asm_64.S | 2 +-
arch/x86/xen/xen-head.S | 8 +-
drivers/block/xen-blkback/blkback.c | 27 +-
drivers/block/xen-blkback/common.h | 2 +
drivers/block/xen-blkback/xenbus.c | 19 +-
drivers/net/xen-netback/netback.c | 25 +-
drivers/xen/balloon.c | 15 +-
drivers/xen/events/events_2l.c | 4 +-
drivers/xen/events/events_base.c | 6 +-
drivers/xen/events/events_fifo.c | 2 +-
drivers/xen/evtchn.c | 4 +-
drivers/xen/features.c | 1 +
drivers/xen/gntdev.c | 10 +-
drivers/xen/grant-table.c | 15 +-
drivers/xen/privcmd.c | 5 +-
drivers/xen/xenbus/xenbus.h | 2 +
drivers/xen/xenbus/xenbus_client.c | 28 +-
drivers/xen/xenbus/xenbus_dev_backend.c | 4 +-
drivers/xen/xenbus/xenbus_dev_frontend.c | 6 +-
drivers/xen/xenbus/xenbus_probe.c | 57 +-
drivers/xen/xenbus/xenbus_xs.c | 40 +-
drivers/xen/xenfs/super.c | 7 +-
drivers/xen/xenfs/xensyms.c | 4 +
include/linux/kvm_host.h | 24 +
include/uapi/linux/kvm.h | 104 +-
include/xen/balloon.h | 7 +
include/xen/xen-ops.h | 2 +-
include/xen/xen.h | 5 +
include/xen/xenbus.h | 3 +
48 files changed, 3232 insertions(+), 67 deletions(-)
create mode 100644 arch/x86/kvm/xen-asm.S
create mode 100644 arch/x86/kvm/xen-shim.c
create mode 100644 arch/x86/kvm/xen.c
create mode 100644 arch/x86/kvm/xen.h
--
2.11.0
next reply other threads:[~2019-02-20 20:17 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 20:15 Joao Martins [this message]
2019-02-20 20:15 ` [PATCH RFC 01/39] KVM: x86: fix Xen hypercall page msr handling Joao Martins
2019-02-22 1:30 ` Sean Christopherson
2019-02-22 11:47 ` Joao Martins
2019-02-22 12:51 ` Paolo Bonzini
2020-11-30 10:39 ` David Woodhouse
2020-11-30 11:03 ` Paolo Bonzini
2020-11-30 11:27 ` David Woodhouse
2019-02-20 20:15 ` [PATCH RFC 02/39] KVM: x86/xen: intercept xen hypercalls if enabled Joao Martins
2019-02-21 18:29 ` Sean Christopherson
2019-02-21 20:56 ` Joao Martins
2019-02-22 0:30 ` Sean Christopherson
2019-02-22 12:50 ` Paolo Bonzini
2020-12-01 9:48 ` David Woodhouse
2020-12-01 11:19 ` David Woodhouse
2020-12-02 11:17 ` Joao Martins
2020-12-02 12:12 ` David Woodhouse
2020-12-02 5:19 ` Ankur Arora
2020-12-02 8:03 ` David Woodhouse
2020-12-02 18:20 ` Ankur Arora
2019-02-20 20:15 ` [PATCH RFC 03/39] KVM: x86/xen: register shared_info page Joao Martins
2020-12-01 13:07 ` David Woodhouse
2020-12-02 0:40 ` Ankur Arora
2020-12-02 1:26 ` David Woodhouse
2020-12-02 5:17 ` Ankur Arora
2020-12-02 10:50 ` Joao Martins
2020-12-02 10:44 ` Joao Martins
2020-12-02 12:20 ` David Woodhouse
2020-12-02 20:32 ` Ankur Arora
2020-12-03 10:16 ` David Woodhouse
2020-12-04 17:30 ` Sean Christopherson
2020-12-02 20:33 ` Ankur Arora
2020-12-12 12:07 ` David Woodhouse
2019-02-20 20:15 ` [PATCH RFC 04/39] KVM: x86/xen: setup pvclock updates Joao Martins
2019-02-20 20:15 ` [PATCH RFC 05/39] KVM: x86/xen: update wallclock region Joao Martins
2019-02-20 20:15 ` [PATCH RFC 06/39] KVM: x86/xen: register vcpu info Joao Martins
2019-02-20 20:15 ` [PATCH RFC 07/39] KVM: x86/xen: register vcpu time info region Joao Martins
2019-02-20 20:15 ` [PATCH RFC 08/39] KVM: x86/xen: register steal clock Joao Martins
2019-02-20 20:15 ` [PATCH RFC 09/39] KVM: x86: declare Xen HVM guest capability Joao Martins
2019-02-20 20:15 ` [PATCH RFC 10/39] KVM: x86/xen: support upcall vector Joao Martins
2020-12-02 11:17 ` David Woodhouse
2020-12-02 13:12 ` Joao Martins
2020-12-02 16:47 ` David Woodhouse
2020-12-02 18:34 ` Joao Martins
2020-12-02 19:02 ` David Woodhouse
2020-12-02 20:12 ` Joao Martins
2020-12-02 20:37 ` David Woodhouse
2020-12-03 1:08 ` Ankur Arora
2020-12-08 16:08 ` David Woodhouse
2020-12-09 6:35 ` Ankur Arora
2020-12-09 10:27 ` David Woodhouse
2020-12-09 10:51 ` Joao Martins
2020-12-09 11:39 ` David Woodhouse
2020-12-09 13:26 ` Joao Martins
2020-12-09 15:41 ` David Woodhouse
2020-12-09 16:12 ` Joao Martins
2021-01-01 14:33 ` David Woodhouse
2021-01-05 12:11 ` Joao Martins
2021-01-05 13:23 ` David Woodhouse
2019-02-20 20:15 ` [PATCH RFC 11/39] KVM: x86/xen: evtchn signaling via eventfd Joao Martins
2020-11-30 9:41 ` David Woodhouse
2020-11-30 12:17 ` Joao Martins
2020-11-30 12:55 ` David Woodhouse
2020-11-30 15:08 ` Joao Martins
2020-11-30 16:48 ` David Woodhouse
2020-11-30 17:15 ` Joao Martins
2020-11-30 18:01 ` David Woodhouse
2020-11-30 18:41 ` Joao Martins
2020-11-30 19:04 ` David Woodhouse
2020-11-30 19:25 ` Joao Martins
2021-11-23 13:15 ` David Woodhouse
2019-02-20 20:15 ` [PATCH RFC 12/39] KVM: x86/xen: store virq when assigning evtchn Joao Martins
[not found] ` <b750291466f3c89e0a393e48079c087704b217a5.camel@amazon.co.uk>
2022-02-10 12:17 ` Joao Martins
2022-02-10 15:23 ` [EXTERNAL] " David Woodhouse
2019-02-20 20:15 ` [PATCH RFC 13/39] KVM: x86/xen: handle PV timers oneshot mode Joao Martins
2019-02-20 20:15 ` [PATCH RFC 14/39] KVM: x86/xen: handle PV IPI vcpu yield Joao Martins
2019-02-20 20:15 ` [PATCH RFC 15/39] KVM: x86/xen: handle PV spinlocks slowpath Joao Martins
2022-02-08 12:36 ` David Woodhouse
2022-02-10 12:17 ` Joao Martins
2022-02-10 14:11 ` David Woodhouse
2019-02-20 20:15 ` [PATCH RFC 16/39] KVM: x86: declare Xen HVM evtchn offload capability Joao Martins
2019-02-20 20:15 ` [PATCH RFC 17/39] x86/xen: export vcpu_info and shared_info Joao Martins
2019-02-20 20:15 ` [PATCH RFC 18/39] x86/xen: make hypercall_page generic Joao Martins
2019-02-20 20:15 ` [PATCH RFC 19/39] xen/xenbus: xenbus uninit support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 20/39] xen-blkback: module_exit support Joao Martins
2019-02-25 18:57 ` Konrad Rzeszutek Wilk
2019-02-26 11:20 ` Joao Martins
2019-02-20 20:15 ` [PATCH RFC 21/39] KVM: x86/xen: domid allocation Joao Martins
2019-02-20 20:15 ` [PATCH RFC 22/39] KVM: x86/xen: grant table init Joao Martins
2019-02-20 20:15 ` [PATCH RFC 23/39] KVM: x86/xen: grant table grow support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 24/39] KVM: x86/xen: backend hypercall support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 25/39] KVM: x86/xen: grant map support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 26/39] KVM: x86/xen: grant unmap support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 27/39] KVM: x86/xen: grant copy support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 28/39] KVM: x86/xen: interdomain evtchn support Joao Martins
2019-02-20 20:15 ` [PATCH RFC 29/39] KVM: x86/xen: evtchn unmask support Joao Martins
2019-02-20 20:16 ` [PATCH RFC 30/39] KVM: x86/xen: add additional evtchn ops Joao Martins
2019-02-20 20:16 ` [PATCH RFC 31/39] xen-shim: introduce shim domain driver Joao Martins
2019-02-20 20:16 ` [PATCH RFC 32/39] xen/balloon: xen_shim_domain() support Joao Martins
2019-02-20 20:16 ` [PATCH RFC 33/39] xen/grant-table: " Joao Martins
2019-02-20 20:16 ` [PATCH RFC 34/39] xen/gntdev: " Joao Martins
2019-02-20 20:16 ` [PATCH RFC 35/39] xen/xenbus: " Joao Martins
2019-02-20 20:16 ` [PATCH RFC 36/39] drivers/xen: " Joao Martins
2019-02-20 20:16 ` [PATCH RFC 37/39] xen-netback: " Joao Martins
2019-02-20 20:16 ` [PATCH RFC 38/39] xen-blkback: " Joao Martins
2019-02-20 20:16 ` [PATCH RFC 39/39] KVM: x86: declare Xen HVM Dom0 capability Joao Martins
2019-02-20 21:09 ` [PATCH RFC 00/39] x86/KVM: Xen HVM guest support Paolo Bonzini
2019-02-21 0:29 ` Ankur Arora
2019-02-21 11:45 ` Joao Martins
2019-02-22 16:59 ` Paolo Bonzini
2019-03-12 17:14 ` Joao Martins
2019-04-08 6:44 ` Juergen Gross
2019-04-08 10:36 ` Joao Martins
2019-04-08 10:42 ` Juergen Gross
2019-04-08 17:31 ` Joao Martins
2019-04-09 0:35 ` Stefano Stabellini
2019-04-10 5:50 ` [Xen-devel] " Ankur Arora
2019-04-10 20:45 ` Stefano Stabellini
2019-04-09 5:04 ` Juergen Gross
2019-04-10 6:55 ` Ankur Arora
2019-04-10 7:14 ` Juergen Gross
2019-02-20 23:39 ` [Xen-devel] " Marek Marczykowski-Górecki
2019-02-21 0:31 ` Ankur Arora
2019-02-21 7:57 ` Juergen Gross
2019-02-21 12:00 ` Joao Martins
2019-02-21 11:55 ` Joao Martins
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=20190220201609.28290-1-joao.m.martins@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=ankur.a.arora@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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).