From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: Fwd: [PATCH 0/18] Nested Virtualization: Overview
Date: Thu, 15 Apr 2010 15:20:31 +0200 [thread overview]
Message-ID: <201004151520.31527.Christoph.Egger@amd.com> (raw)
Resending w/o documents. It seems to not get through to the list.
---------- Forwarded Message ----------
Subject: [PATCH 0/18] Nested Virtualization: Overview
Date: Thursday 15 April 2010
From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Hi!
This patch series brings Nested Virtualization to Xen.
I have attached two documents Nested_Virtualization.pdf and XenNestedHVM.pdf.
The first describes how nested virtualization works in general and the latter
describes the xen implementation in detail.
The patch series:
patch 01: add nestedhvm guest config option to the tools
This is the only one patch touching the tools
patch 02: move viridian MSRs into the viridian header for use in an
other file added in patch 09.
patch 03: change local_event_delivery_* to take vcpu argument.
This prevents spurious xen crashes on guest shutdown/destroy
with nestedhvm enabled.
patch 04: obsolete gfn_to_mfn_current and remove it.
gfn_to_mfn_current is redundant to
gfn_to_mfn(current->domain, ...)
This patch reduces the size of patch 17.
patch 05: hvm_set_cr0: Allow guest to switch into paged real mode.
This makes hvmloader boot when we use xen in xen.
patch 06: Move phys_table from struct domain to struct p2m_domain.
Combined with patch 17 and patch 18, this allows to run
nested guest with hap.
patch 07: Add data structures for nested virtualization.
patch 08: add nestedhvm function hooks, described in XenNestedHVM.pdf
patch 09: The heart of nested virtualization.
patch 10: Allow guest to enable SVM in EFER
patch 11: Propagate SVM cpuid feature bits to guest
patch 12: Emulate MSRs needed for nested virtualization
patch 13: Handle interrupts (generic part)
patch 14: SVM specific implementation for nested virtualization
patch 15: Handle interrupts (SVM specific)
patch 16: The piece of code that effectively turns nested virtualization on
patch 17: Change p2m infrastructure to operate with per-p2m instead
of per-domain. Combined with patch 06 and patch 18, this
allows to run nested guest with hap.
patch 18: Handle nested pagefault to enable hap-on-hap
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
-------------------------------------------------------
next reply other threads:[~2010-04-15 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 13:20 Christoph Egger [this message]
2010-04-15 13:39 ` Fwd: [PATCH 0/18] Nested Virtualization: Overview Vincent Hanquez
2010-04-15 14:50 ` Christoph Egger
2010-04-15 14:51 ` Christoph Egger
2010-04-15 14:57 ` Keir Fraser
2010-04-15 15:17 ` Christoph Egger
2010-04-15 16:26 ` Keir Fraser
2010-04-15 15:25 ` Tim Deegan
2010-04-16 10:01 ` Christoph Egger
2010-04-16 9:07 ` Qing He
2010-04-16 9:32 ` Christoph Egger
2010-04-16 10:27 ` Tim Deegan
2010-04-16 17:50 ` Keir Fraser
2010-04-20 2:07 ` Dong, Eddie
2010-04-17 11:43 ` Joerg Roedel
2010-04-18 17:52 ` Keir Fraser
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=201004151520.31527.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=xen-devel@lists.xensource.com \
/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.