From: Tamas K Lengyel <tamas.lengyel@intel.com>
To: xen-devel@lists.xenproject.org
Cc: "Petre Pircalabu" <ppircalabu@bitdefender.com>,
"Tamas K Lengyel" <tamas@tklengyel.com>,
"Tamas K Lengyel" <tamas.lengyel@intel.com>,
"Wei Liu" <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <george.dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Alexandru Isaila" <aisaila@bitdefender.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH v5 00/18] VM forking
Date: Tue, 21 Jan 2020 09:49:33 -0800 [thread overview]
Message-ID: <cover.1579628566.git.tamas.lengyel@intel.com> (raw)
The following series implements VM forking for Intel HVM guests to allow for
the fast creation of identical VMs without the assosciated high startup costs
of booting or restoring the VM from a savefile.
JIRA issue: https://xenproject.atlassian.net/browse/XEN-89
The fork operation is implemented as part of the "xl fork-vm" command:
xl fork-vm -C <config_file_for_fork> -Q <qemu_save_file> <parent_domid>
By default a fully functional fork is created. The user is in charge however to
create the appropriate config file for the fork and to generate the QEMU save
file before the fork-vm call is made. The config file needs to give the
fork a new name at minimum but other settings may also require changes.
The interface also allows to split the forking into two steps:
xl fork-vm --launch-dm no \
-p <parent_domid>
xl fork-vm --launch-dm late \
-C <config_file_for_fork> \
-Q <qemu_save_file> \
<fork_domid>
The split creation model is useful when the VM needs to be created as fast as
possible. The forked VM can be unpaused without the device model being launched
to be monitored and accessed via VMI. Note however that without its device
model running (depending on what is executing in the VM) it is bound to
misbehave or even crash when its trying to access devices that would be
emulated by QEMU. We anticipate that for certain use-cases this would be an
acceptable situation, in case for example when fuzzing is performed of code
segments that don't access such devices.
Launching the device model requires the QEMU Xen savefile to be generated
manually from the parent VM. This can be accomplished simply by connecting to
its QMP socket and issuing the "xen-save-devices-state" command. For example
using the standard tool socat these commands can be used to generate the file:
socat - UNIX-CONNECT:/var/run/xen/qmp-libxl-<parent_domid>
{ "execute": "qmp_capabilities" }
{ "execute": "xen-save-devices-state", \
"arguments": { "filename": "/path/to/save/qemu_state", \
"live": false} }
At runtime the forked VM starts running with an empty p2m which gets lazily
populated when the VM generates EPT faults, similar to how altp2m views are
populated. If the memory access is a read-only access, the p2m entry is
populated with a memory shared entry with its parent. For write memory accesses
or in case memory sharing wasn't possible (for example in case a reference is
held by a third party), a new page is allocated and the page contents are
copied over from the parent VM. Forks can be further forked if needed, thus
allowing for further memory savings.
A VM fork reset hypercall is also added that allows the fork to be reset to the
state it was just after a fork, also accessible via xl:
xl fork-vm --fork-reset -p <fork_domid>
This is an optimization for cases where the forks are very short-lived and run
without a device model, so resetting saves some time compared to creating a
brand new fork provided the fork has not aquired a lot of memory. If the fork
has a lot of memory deduplicated it is likely going to be faster to create a
new fork from scratch and asynchronously destroying the old one.
The series has been tested with both Linux and Windows VMs and functions as
expected. VM forking time has been measured to be 0.0007s, device model launch
to be around 1s depending largely on the number of devices being emulated. Fork
resets have been measured to be 0.0001s under the optimal circumstances.
Patches 1-2 implement changes to existing internal Xen APIs to make VM forking
possible.
Patches 3-14 are code-cleanups and adjustments of to Xen memory sharing
subsystem with no functional changes.
Patch 15 adds the hypervisor-side code implementing VM forking.
Patch 16 is integration of mem_access with forked VMs.
Patch 17 implements the VM fork reset operation hypervisor side bits.
Patch 18 adds the toolstack-side code implementing VM forking and reset.
New in v5: Patch 3 and 14.
Paches without Acks or Reviews:
1, 2, 3, 11, 12, 14, 15, 16, 17, 18
Tamas K Lengyel (18):
x86/hvm: introduce hvm_copy_context_and_params
xen/x86: Make hap_get_allocation accessible
x86/p2m: Allow p2m_get_page_from_gfn to return shared entries
x86/mem_sharing: make get_two_gfns take locks conditionally
x86/mem_sharing: drop flags from mem_sharing_unshare_page
x86/mem_sharing: don't try to unshare twice during page fault
x86/mem_sharing: define mem_sharing_domain to hold some scattered
variables
x86/mem_sharing: Use INVALID_MFN and p2m_is_shared in
relinquish_shared_pages
x86/mem_sharing: Make add_to_physmap static and shorten name
x86/mem_sharing: Convert MEM_SHARING_DESTROY_GFN to a bool
x86/mem_sharing: Replace MEM_SHARING_DEBUG with gdprintk
x86/mem_sharing: Enable mem_sharing on first memop
x86/mem_sharing: Skip xen heap pages in memshr nominate
x86/mem_sharing: use default_access in add_to_physmap
xen/mem_sharing: VM forking
xen/mem_access: Use __get_gfn_type_access in set_mem_access
x86/mem_sharing: reset a fork
xen/tools: VM forking toolstack side
docs/man/xl.1.pod.in | 36 +++
tools/libxc/include/xenctrl.h | 13 +
tools/libxc/xc_memshr.c | 22 ++
tools/libxl/libxl.h | 7 +
tools/libxl/libxl_create.c | 237 ++++++++++-----
tools/libxl/libxl_dm.c | 2 +-
tools/libxl/libxl_dom.c | 83 ++++--
tools/libxl/libxl_internal.h | 1 +
tools/libxl/libxl_types.idl | 1 +
tools/xl/xl.h | 5 +
tools/xl/xl_cmdtable.c | 12 +
tools/xl/xl_saverestore.c | 96 ++++++
tools/xl/xl_vmcontrol.c | 8 +
xen/arch/x86/domain.c | 9 +
xen/arch/x86/hvm/hvm.c | 267 ++++++++++-------
xen/arch/x86/mm/hap/hap.c | 3 +-
xen/arch/x86/mm/mem_access.c | 5 +-
xen/arch/x86/mm/mem_sharing.c | 474 ++++++++++++++++++++++++------
xen/arch/x86/mm/p2m.c | 21 +-
xen/common/memory.c | 2 +-
xen/drivers/passthrough/pci.c | 3 +-
xen/include/asm-x86/hap.h | 1 +
xen/include/asm-x86/hvm/domain.h | 6 +-
xen/include/asm-x86/hvm/hvm.h | 2 +
xen/include/asm-x86/mem_sharing.h | 42 ++-
xen/include/asm-x86/p2m.h | 14 +-
xen/include/public/memory.h | 6 +
xen/include/xen/sched.h | 2 +
28 files changed, 1051 insertions(+), 329 deletions(-)
--
2.20.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2020-01-21 17:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 17:49 Tamas K Lengyel [this message]
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 01/18] x86/hvm: introduce hvm_copy_context_and_params Tamas K Lengyel
2020-01-22 15:00 ` Jan Beulich
2020-01-22 16:42 ` Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 02/18] xen/x86: Make hap_get_allocation accessible Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 03/18] x86/p2m: Allow p2m_get_page_from_gfn to return shared entries Tamas K Lengyel
2020-01-22 15:23 ` Jan Beulich
2020-01-22 16:51 ` Tamas K Lengyel
2020-01-22 16:55 ` Jan Beulich
2020-01-23 15:32 ` George Dunlap
2020-01-23 15:48 ` Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 04/18] x86/mem_sharing: make get_two_gfns take locks conditionally Tamas K Lengyel
2020-01-23 15:50 ` George Dunlap
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 05/18] x86/mem_sharing: drop flags from mem_sharing_unshare_page Tamas K Lengyel
2020-01-23 15:53 ` George Dunlap
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 06/18] x86/mem_sharing: don't try to unshare twice during page fault Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 07/18] x86/mem_sharing: define mem_sharing_domain to hold some scattered variables Tamas K Lengyel
2020-01-23 15:59 ` George Dunlap
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 08/18] x86/mem_sharing: Use INVALID_MFN and p2m_is_shared in relinquish_shared_pages Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 09/18] x86/mem_sharing: Make add_to_physmap static and shorten name Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 10/18] x86/mem_sharing: Convert MEM_SHARING_DESTROY_GFN to a bool Tamas K Lengyel
2020-01-23 16:14 ` George Dunlap
2020-01-23 16:23 ` Tamas K Lengyel
2020-01-23 16:32 ` George Dunlap
2020-01-23 16:37 ` Jan Beulich
2020-01-23 16:42 ` George Dunlap
2020-01-23 16:55 ` Jan Beulich
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 11/18] x86/mem_sharing: Replace MEM_SHARING_DEBUG with gdprintk Tamas K Lengyel
2020-01-22 15:30 ` Jan Beulich
2020-01-22 16:55 ` Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 12/18] x86/mem_sharing: Enable mem_sharing on first memop Tamas K Lengyel
2020-01-22 15:32 ` Jan Beulich
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 13/18] x86/mem_sharing: Skip xen heap pages in memshr nominate Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 14/18] x86/mem_sharing: use default_access in add_to_physmap Tamas K Lengyel
2020-01-22 15:35 ` Jan Beulich
2020-01-22 17:08 ` Tamas K Lengyel
2020-01-23 16:44 ` George Dunlap
2020-01-23 17:19 ` Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 15/18] xen/mem_sharing: VM forking Tamas K Lengyel
2020-01-23 17:21 ` George Dunlap
2020-01-23 17:30 ` Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 16/18] xen/mem_access: Use __get_gfn_type_access in set_mem_access Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 17/18] x86/mem_sharing: reset a fork Tamas K Lengyel
2020-01-21 17:49 ` [Xen-devel] [PATCH v5 18/18] xen/tools: VM forking toolstack side Tamas K Lengyel
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=cover.1579628566.git.tamas.lengyel@intel.com \
--to=tamas.lengyel@intel.com \
--cc=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=ppircalabu@bitdefender.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--cc=wl@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.