From: Thomas Schwinge <thomas@schwinge.name>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: [GIT PULL] pv/pcifront-2.6.32 .. update: 2 bug-fixes.
Date: Mon, 21 Jun 2010 23:12:27 +0200 [thread overview]
Message-ID: <20100621211227.GC1172@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20100618201620.GA22626@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 1149 bytes --]
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!
Regards,
Thomas
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-06-21 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 20:16 [GIT PULL] pv/pcifront-2.6.32 .. update: 2 bug-fixes Konrad Rzeszutek Wilk
2010-06-21 21:12 ` Thomas Schwinge [this message]
2010-06-21 22:09 ` Konrad Rzeszutek Wilk
2010-06-21 22:34 ` Thomas Schwinge
2010-06-21 22:48 ` Konrad Rzeszutek Wilk
2010-06-22 8:56 ` AW: " Carsten Schiers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100621211227.GC1172@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).