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/
Home Products Support Community News


Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
From: Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Date: Thu, 18 Mar 2010 09:30:30 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 17 Mar 2010 18:31:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BA0FF8C.30302@xxxxxxxx>
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: <alpine.DEB.2.00.1003101457100.28412@kaball-desktop> <alpine.DEB.2.00.1003171047230.23661@kaball-desktop> <4BA0FF8C.30302@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; )
On Thursday 18 March 2010 00:13:00 Jeremy Fitzhardinge wrote:
> On 03/17/2010 08:21 AM, Stefano Stabellini wrote:
> > As pointed out before by Jeremy and Konrad, the best starting point is
> > probably Konrad's pv/pcifront-2.6.31 tree: it contains most of the pirq
> > stuff, ready to be upstreamed.
> > AFAICT the only things required to make pirq mappings work (as in
> > my series) that are missing are:
> >
> > - xen_register_gsi
> >
> > - xen_setup_pirqs
> >
> > - the xen_register_gsi hook in acpi_register_gsi
> >
> > the first two should be easy to port because they don't require any
> > change but the last one definitely needs modifications in order to be
> > accepted upstream.
> Have a look at 108bfa4b9029bd0f9775319900f82eb9749f5954 and
> 78c07daac0d9e267b5c23a3e9fbd3c7697f4ef44 in
> xen/dom0/"new"-interrupt-routing.  I think this will be a plausible
> thing to upstream.

Would look into it.
> > I didn't include MSI support because is not required, but that is
> > another area that needs changes.
> Xiantao has some interesting ideas for this.
Xiantao and I have discussed on this for a month... Basically we have got two 
approaches now, but we can't reach an agreement... I would work on it after 
current hybrid thing settled down. Of course, we want MSI support benefit  
pv_ops dom0 as well as hybrid.

Yang, Sheng

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>