From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Question about backporting pci passthrough fix to 2.6.18 Date: Thu, 1 Jul 2010 11:40:14 -0400 Message-ID: <20100701154014.GF31947@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline 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: Paraic Gallagher Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jul 01, 2010 at 10:04:01AM +0100, Paraic Gallagher wrote: > Hi, > > I have a question about the bug: > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1632 > > This is marked as fixed in the pv-ops kernel. > > I am working for a company developing a xen based virtualisation solution. > Unfortunately the design is tied to CentOS and there is resistance to > upgrade to > 2.6.31 kernel. > > My question is whether it is possible for me to try to backport the fixes > for this pci passthrough issue to a 2.6.18 kernel, or are there too many > differences between the kernel versions to make this feasible/possible. You should be able to do it. The SysFS parts might need some tweaking. > > > ------- Comment #1 from konrad.wilk@oracle.com 2010-06-30 07:54 ------- > There is a fix for this in the pv-ops kernel. > > Specifically: > xen-pciback: Allocate IRQ handler for device that is shared with guest. > xen-pciback: Add SysFS instrumentation for the fake IRQ handler. > xen-pciback: When device transitions to MSI/MSI-X stop ACK-ing on the > legacy interrupt. > xen-pciback: Enable interrupt handler when device is enabled. > xen-pciback: Probe the IRQ line to check if it is not shared > > Here is a howto on PV-OPS:http://wiki.xensource.com/xenwiki/XenParavirtOps > and how to migrate from RHEL5 to it > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher > > Closing bug as FIXED in upstream. > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel