All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: [PATCH 0/14] Nested Virtualization: Overview
Date: Tue, 17 Aug 2010 12:33:29 +0200	[thread overview]
Message-ID: <201008171233.30154.Christoph.Egger@amd.com> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B2291435E0@shsmsx501.ccr.corp.intel.com>

On Tuesday 17 August 2010 08:04:20 Dong, Eddie wrote:
> Hi, Chris:
>
> Christoph Egger wrote:
> > Hi!
> >
> > This patch series brings Nested Virtualization to Xen.
> > This is the third patch series. Improvements to the
> > previous patch submission:
> >
> > - implement HVM-on-HVM (instead of SVM-on-HVM)
>
> Given that we don't have consensus on cross architecture nested
> virtualization support, I am doubting why this is urgent for now.

The reason to be "urgent" is not the time. This is the best way from
the software engineering side.

> I would prefer we make SVM-on-SVM and VMX-on-VMX work first. After that,
> if you prove SVM-on-VMX has real performance gain (which I doubt), we can
> see how to make a much generic effort to accomodate both natively nested
> virtualization and cross architecture nested virtualization.

Tim and Keir made clear they don't want to have two implementations after
I submitted my patch series the *first* time.

> Drawing a picture which doesn't have a real usage with massive common code
> change is a kind of too much load for us now. Xen hvm_function table is a
> good example. Intel enabled VMX at very beginning of Xen HVM support, and
> SVM comes later on with a lot of code reuse from VMX side. Then the
> community and both side work together to make an API wrapper to reuse
> common code better and accomodate both architecture. I think we have to go
> similar path to make it work first.

Tim remembers on this and said in this mail
http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00812.html

"With HVM it has turned out to be quite a lot, but it's taken years of
reshuffling to pull code out into common HVM routines (and we're not there
yet)."

If I understand Tim correctly, the way you suggest is a "no".
(Added Tim on CC)

Christoph

>
> > - move cpuid handling into tools (per Keir's request)
> >
> > There might still be some nuances to fiddle with to make it
> > fit for VMX. Feedback from Intel is appreciated, therefore.
>
> Thx, Eddie



-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2010-08-17 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 14:59 [PATCH 0/14] Nested Virtualization: Overview Christoph Egger
2010-08-17  6:04 ` Dong, Eddie
2010-08-17 10:33   ` Christoph Egger [this message]
2010-08-17 10:41     ` Keir Fraser
2010-08-17 12:30       ` Tim Deegan

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=201008171233.30154.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=eddie.dong@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 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.