From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH 0 of 5] PV on HVM Xen Date: Wed, 17 Mar 2010 09:13:00 -0700 Message-ID: <4BA0FF8C.30302@goop.org> References: <201003151629.12994.sheng@linux.intel.com> <201003171738.37830.sheng@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: "xen-devel@lists.xensource.com" , "Zhang, Xiantao" , Sheng Yang List-Id: xen-devel@lists.xenproject.org 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. > 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. J