From: domiel forty-two <domiel42@yahoo.com.au>
To: xen-devel@lists.xensource.com
Subject: Re: Xen-devel Digest, Vol 71, Issue 85
Date: Thu, 17 Feb 2011 18:44:29 -0800 (PST) [thread overview]
Message-ID: <528111.91222.qm@web39321.mail.mud.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1266 bytes --]
Hi all!
Did the nested xen stuff make it into the xen-unstable (4.1-rc1?) tree as
suggested back in January by Tim Deegan?
TIA
________________________________
Date: Fri, 7 Jan 2011 16:01:12 +0000
From: Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: [Xen-devel] [PATCH 00/12] Nested Virtualization: Overview
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: Keir Fraser <keir@xen.org>, "xen-devel@lists.xensource.com"
<xen-devel@lists.xensource.com>, "Dong, Eddie" <eddie.dong@intel.com>
Message-ID: <20110107160112.GC5651@whitby.uk.xensource.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
At 16:02 +0000 on 20 Dec (1292860962), Christoph Egger wrote:
> This patch series brings Nested Virtualization to Xen.
> This is the seventh patch series.
Thanks for this. I've commented on patch 4 (core) and patch 12
(hap-on-hap) separately. Also I think we need an Acked-by: from Eddie
for patches 1-8.
Apart from that I think we can check these in as soon as the 4.1
branch has been taken, and fix up any remaining issues in-tree.
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
[-- Attachment #1.2: Type: text/html, Size: 2598 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-02-18 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 2:44 domiel forty-two [this message]
2011-02-18 7:08 ` Re: Xen-devel Digest, Vol 71, Issue 85 Keir Fraser
2011-02-18 8:01 ` domiel forty-two
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=528111.91222.qm@web39321.mail.mud.yahoo.com \
--to=domiel42@yahoo.com.au \
--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.