From: Yu Zhao <yu.zhao@intel.com>
To: keir.fraser@eu.citrix.com
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] Dom0 PCI: fix a regression introduced by the SR-IOV change
Date: Wed, 03 Jun 2009 13:41:29 +0800 [thread overview]
Message-ID: <4A260D09.4080502@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
The device class may be changed during the early fixup. So need to
re-read the device class from pci_dev after the fixup.
The patch "PCI: centralize device setup code" (c/s 825) wrongly cleaned
up the device class re-read. This patch reverts that change.
Signed-off-by: Yu Zhao <yu.zhao@intel.com>
[-- Attachment #2: 00.patch --]
[-- Type: text/x-patch, Size: 957 bytes --]
# HG changeset patch
# User Yu Zhao <yu.zhao@intel.com>
# Date 1244007008 -28800
# Node ID ec3442c2ed48eb11fcacd3fe31af48932f0a6645
# Parent 97e0d58411d4cee30c16ee1f81d23b72ec7f107c
PCI: fix a regression introduced by the SR-IOV change
The device class may be changed during the early fixup. So need to
re-read the device class from pci_dev after the fixup.
The patch "PCI: centralize device setup code" (c/s 825) wrongly cleaned
up the device class re-read. This patch reverts that change.
Signed-off-by: Yu Zhao <yu.zhao@intel.com>
diff -r 97e0d58411d4 -r ec3442c2ed48 drivers/pci/probe.c
--- a/drivers/pci/probe.c Tue Jun 02 23:43:55 2009 +0100
+++ b/drivers/pci/probe.c Wed Jun 03 13:30:08 2009 +0800
@@ -721,6 +721,7 @@
/* Early fixups, before probing the BARs */
pci_fixup_device(pci_fixup_early, dev);
+ class = dev->class >> 8;
switch (dev->hdr_type) { /* header type */
case PCI_HEADER_TYPE_NORMAL: /* standard header */
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2009-06-03 5:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A260D09.4080502@intel.com \
--to=yu.zhao@intel.com \
--cc=keir.fraser@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.