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: [Pkg-xen-devel] Problems with PCI pass-through

Hello!

On Tue, Jun 08, 2010 at 11:08:26AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 07, 2010 at 11:13:56AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Sat, Jun 05, 2010 at 12:42:15AM +0200, Thomas Schwinge wrote:
> > > As I'm writing in
> > > <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2010-May/002782.html>
> > > I'm having problems with PCI pass-through.
> > 
> > Oh, sorry didn't pay attention to it.

Well, no problem: that's a Debian-internal list, so that's why I
re-posted it here -- where you did notice it.

> > > It doesn't matter whether I'm using a 3.4 or 4.0 hypervisor (Debian
> > > packages).  Also I tested two different kernels (both .32 ones).
> > > 
> > > 
> > > Some more details:
> > > 
> > > On Sat, May 29, 2010 at 03:32:46PM +0300, Pasi Kärkkäinen wrote:
> > > > On Fri, May 28, 2010 at 11:18:56PM +0200, Thomas Schwinge wrote:
> > > > > I'm having problems getting PCI pass-through to work.
> > 
> > Aha. I know exactly what the problem is..

Thanks for the explanatio.  Indeed, adding the PCI 0 device does make it
work!

> And it is a regression (compared to say 2.6.27 or 2.6.18).
> 
> There was some disussion about this:
> http://lkml.indiana.edu/hypermail//linux/kernel/0906.2/03861.html
> 
> which ended up pulling out of the Linux kernel the functinality to
> scan for specific functions.
> 
> Will have to add that to xen-pcifront driver..

If you need someone to test any patches, please ask.


Regards,
 Thomas

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>