xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Cc: Thomas Schwinge <thomas@schwinge.name>
Subject: [GIT PULL] pv/pcifront-2.6.32 .. update: 2 bug-fixes.
Date: Fri, 18 Jun 2010 16:16:20 -0400	[thread overview]
Message-ID: <20100618201620.GA22626@phenom.dumpdata.com> (raw)

Hey Jeremy,

Plese pull from
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.

P.S.
I will concentrate on back-porting some of those fixes in the
pcifront-2.6.31.x branch as well.

             reply	other threads:[~2010-06-18 20:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 20:16 Konrad Rzeszutek Wilk [this message]
2010-06-21 21:12 ` [GIT PULL] pv/pcifront-2.6.32 .. update: 2 bug-fixes Thomas Schwinge
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=20100618201620.GA22626@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jeremy@goop.org \
    --cc=thomas@schwinge.name \
    --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).