All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Tim Deegan <Tim.Deegan@eu.citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH][v3] PV featured HVM(hybrid) support in Xen
Date: Mon, 8 Feb 2010 16:31:33 +0800	[thread overview]
Message-ID: <201002081631.33727.sheng@linux.intel.com> (raw)
In-Reply-To: <C7957806.965C%keir.fraser@eu.citrix.com>

On Monday 08 February 2010 16:12:54 Keir Fraser wrote:
> On 08/02/2010 08:05, "Yang, Sheng" <sheng.yang@intel.com> wrote:
> > Hi Keir
> >
> > Here is the latest (hybrid) patchset.
> >
> > Change from v2:
> >
> > 1. Change the name "hybrid" to "PV featured HVM", as well as flag and
> > macro names.
> > 2. Merge the hypercall page with HVM.
> > 3. Clean up VIRQ delivery mechanism, fixing the lock issue.
> > 4. Remove the reserved the region in E820(but another issue remains, I
> > can't get location of grant table elegantly, as I described in Linux part
> > patches)
> >
> > Please review, thanks!
> 
> Why can't you leave LAPIC available for things like INIT-SIPI-SIPI, and
> simply not use it for things you need higher perf for?

I am not quite understand why we need to stick to INIT-SIPI-SIPI. For the 
physical cpus, we can't tell their state directly, so we need a protocol, like 
INIT-SIPI-SIPI; but for virtual cpus, we have hypercall as our protocol, so we 
can easily tell them when and where to start, which is much more directly like 
PV domU did.

-- 
regards
Yang, Sheng

  reply	other threads:[~2010-02-08  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  8:05 [PATCH][v3] PV featured HVM(hybrid) support in Xen Yang, Sheng
2010-02-08  8:12 ` Keir Fraser
2010-02-08  8:31   ` Sheng Yang [this message]
2010-02-08 10:09     ` 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=201002081631.33727.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=keir.fraser@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 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.