WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH][v3] PV featured HVM(hybrid) support in Xen

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][v3] PV featured HVM(hybrid) support in Xen
From: Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Date: Mon, 8 Feb 2010 16:31:33 +0800
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 08 Feb 2010 00:32:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7957806.965C%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Intel Opensource Technology Center
References: <C7957806.965C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.12.2 (Linux/2.6.31-19-generic; KDE/4.3.2; x86_64; ; )
On Monday 08 February 2010 16:12:54 Keir Fraser wrote:
> On 08/02/2010 08:05, "Yang, Sheng" <sheng.yang@xxxxxxxxx> 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

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