Paraic Gallagher
2010-Jul-01 09:04 UTC
[Xen-devel] Question about backporting pci passthrough fix to 2.6.18
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. thanks all, Páraic. ------- 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
Konrad Rzeszutek Wilk
2010-Jul-01 15:40 UTC
Re: [Xen-devel] Question about backporting pci passthrough fix to 2.6.18
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Reasonably Related Threads
- XEN | kernel 3.0 vs 2.6.34-xen - no pci backend?
- blktapctrl not running
- with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don''t own device"
- PCI passthrough of cciss HBA
- PCI passthrough of a SATA/PATA controller, "FLR functionality not supported"