From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Tim Deegan <Tim.Deegan@citrix.com>, Qing He <qing.he@intel.com>
Subject: Re: [PATCH] RFC: nested virtualization: tools
Date: Thu, 20 May 2010 16:13:57 +0200 [thread overview]
Message-ID: <201005201613.57932.Christoph.Egger@amd.com> (raw)
In-Reply-To: <201005201609.38515.Christoph.Egger@amd.com>
On Thursday 20 May 2010 16:09:38 Christoph Egger wrote:
> Hi!
>
> This patch implements 'nestedhvm' guest config option using HVM_PARAM.
> Qing: Please take this patch, make it work for VMX and send it on xen-devel
> for review.
Forgot to mention: The libxl part is missing. Qing: Feel free to implement the
libxl part.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2010-05-20 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 14:09 [PATCH] RFC: nested virtualization: tools Christoph Egger
2010-05-20 14:13 ` Christoph Egger [this message]
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=201005201613.57932.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Tim.Deegan@citrix.com \
--cc=qing.he@intel.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 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).