xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 01/12] Nested Virtualization: tools
Date: Fri, 01 Apr 2011 11:26:16 +0100	[thread overview]
Message-ID: <C9BB66D8.15B13%keir.xen@gmail.com> (raw)
In-Reply-To: <19860.50935.146868.916017@mariner.uk.xensource.com>

On 31/03/2011 19:24, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> Christoph Egger writes ("[Xen-devel] [PATCH 01/12] Nested Virtualization:
> tools"):
>> tools: Add nestedhvm guest config option
> 
> I don't have an objection to this.  The tools parts seem largely sane.
> However, I have two queries.
> 
> Firstly, one for Christoph: is this patch safe to apply before the
> relevant hypervisor features, or will it break ?  If it will break
> then it should be applied later.
> 
> Secondly, one for the Xen.org team in general: are we accepting new
> features in Xend ?  If not then I should drop the changes to xend from
> this patch.

If we are dropping xend in this release cycle, why would we bother taking
new features for it? In fact, why is xend even still in the tree? :-)

 -- Keir

> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2011-04-01 10:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 14:22 [PATCH 01/12] Nested Virtualization: tools Christoph Egger
2011-03-28 13:54 ` Dong, Eddie
2011-03-31 18:24 ` Ian Jackson
2011-04-01  8:41   ` Christoph Egger
2011-04-01 10:26   ` Keir Fraser [this message]
2011-04-04 10:25     ` Ian Jackson
  -- strict thread matches above, loose matches on Subject: below --
2010-12-20 16:03 Christoph Egger

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=C9BB66D8.15B13%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Ian.Jackson@eu.citrix.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).