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] Re: Xen: Hybrid extension patchset for hypervisor

To: Frank van der Linden <Frank.Vanderlinden@xxxxxxx>
Subject: Re: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor
From: "Yang, Sheng" <sheng.yang@xxxxxxxxx>
Date: Thu, 17 Sep 2009 14:13:59 +0800
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Delivery-date: Mon, 21 Sep 2009 04:57:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AB13875.9020703@xxxxxxx>
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: <C6D66994.14D6A%keir.fraser@xxxxxxxxxxxxx> <4AB13875.9020703@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.11.2 (Linux/2.6.28-15-generic; KDE/4.2.2; x86_64; ; )
On Thursday 17 September 2009 03:11:49 Frank van der Linden wrote:
> Keir Fraser wrote:
> > On 16/09/2009 09:44, "Yang, Sheng" <sheng.yang@xxxxxxxxx> wrote:
> >> Hi Keir & Jeremy
> >>
> >> Here is the hypervisor part of hybrid extension support.
> >>
> >> Please review, thanks!
> >
> > The principle is okay I guess. These changes would have to be trickled in
> > with a  really good explanation and justification for each one. For
> > example, I'm not clear why the enable-hybrid hypercall is needed. Why not
> > just provide access to evtchn and timer hypercalls always, and guest sues
> > them if it is capable of it? I'm also not sure why PV timer events get
> > routed to irq0 -- why not via an event channel as usual, now that you are
> > enabling HVM guests to use the evtchn subsystem? What's a hybrid gnttab,
> > and why does it need an explciit reserved e820 region? And so on.
> >
> > The general principle of these patches seems to be to create a set of
> > individual, and perhaps largely independent, accelerations/enlightenments
> > to the HVM interface. I can at least agree with and support that aim.
> >
> >  -- Keir
>
> I did not see the hypervisor part of these patches appear in my
> xen-devel inbox. Is this a problem on my end, or were they not sent to
> the list? If so, I'm interested in them, so it'd be great if they could
> be sent to the list.
>
> Thanks,
>
> - Frank

It's quite strange...

Here is the patches(attached). Send them again...

-- 
regards
Yang, Sheng

Attachment: 1.patch
Description: Text Data

Attachment: 2.patch
Description: Text Data

Attachment: 3.patch
Description: Text Data

Attachment: 4.patch
Description: Text Data

Attachment: 5.patch
Description: Text Data

Attachment: 6.patch
Description: Text Data

Attachment: 7.patch
Description: Text Data

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