From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: [GIT PULL] pv/pcifront-2.6.32 .. update: 2 bug-fixes. Date: Mon, 21 Jun 2010 18:09:51 -0400 Message-ID: <20100621220951.GA26574@phenom.dumpdata.com> References: <20100618201620.GA22626@phenom.dumpdata.com> <20100621211227.GC1172@kepler.schwinge.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20100621211227.GC1172@kepler.schwinge.homeip.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Thomas Schwinge Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, Jun 21, 2010 at 11:12:27PM +0200, Thomas Schwinge wrote: > Hello! > > On Fri, Jun 18, 2010 at 04:16:20PM -0400, Konrad Rzeszutek Wilk wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git pv/pcifront-2.6.32 > > > > Since the last pull it fixes two bugs: > > > > 1). Passing in to the guest a device with non-zero function would not > > be scanned. You had to pass in the zero-function as well. > > This fixes: http://lists.xensource.com/archives/html/xen-devel/2010-06/msg00475.html > > > > 2). When rescanning (so using 'xm pci-attach') the xen-pcifront would > > not set the parent of the device to be the PCI bus device and the > > device initialization would stop at: > > > > [ 4.802563] igb 0000:01:00.1: device not available (can't reserve > > [mem 0xfb840000-0xfb85ffff]) > > > > Konrad Rzeszutek Wilk (2): > > xen-pcifront: Enforce scanning of device functions on initial execution. > > xen-pcifront: Claim PCI resources before going live. > > Confirmed -- with both patches applied on top of a current Debian > amd64-xen kernel, forwarding of only PCI ID 0:2.7 (that is, without also > forwarding 0:2.0) works fine on my system. Thanks! Great. Now did it fix your e100 card as well? > > > Regards, > Thomas > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel