From: Yu Zhao <yu.zhao@intel.com>
To: keir.fraser@eu.citrix.com
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] Dom0 PCI: fix SR-IOV function dependency link problem
Date: Wed, 03 Jun 2009 13:41:34 +0800 [thread overview]
Message-ID: <4A260D0E.1010703@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
PCIe Root Complex Integrated Endpoint does not implement ARI, so this
kind of endpoint uses 3-bit function number. The function dependency
link of the integrated endpoint should be calculated using the device
number field in conjunction with the value from function dependency
link register.
Normal SR-IOV endpoint always implements ARI and the function dependency
link register contains 8-bit function number (i.e. `devfn' from software
perspective).
Signed-off-by: Yu Zhao <yu.zhao@intel.com>
[-- Attachment #2: 01.patch --]
[-- Type: text/x-patch, Size: 1235 bytes --]
# HG changeset patch
# User Yu Zhao <yu.zhao@intel.com>
# Date 1244007161 -28800
# Node ID 3a959a6975152b741389d2eed1823d55be4f2889
# Parent ec3442c2ed48eb11fcacd3fe31af48932f0a6645
PCI: fix SR-IOV function dependency link problem
PCIe Root Complex Integrated Endpoint does not implement ARI, so this
kind of endpoint uses 3-bit function number. The function dependency
link of the integrated endpoint should be calculated using the device
number field in conjunction with the value from function dependency
link register.
Normal SR-IOV endpoint always implements ARI and the function dependency
link register contains 8-bit function number (i.e. `devfn' from software
perspective).
Signed-off-by: Yu Zhao <yu.zhao@intel.com>
diff -r ec3442c2ed48 -r 3a959a697515 drivers/pci/iov.c
--- a/drivers/pci/iov.c Wed Jun 03 13:30:08 2009 +0800
+++ b/drivers/pci/iov.c Wed Jun 03 13:32:41 2009 +0800
@@ -366,6 +366,8 @@
iov->self = dev;
pci_read_config_dword(dev, pos + PCI_SRIOV_CAP, &iov->cap);
pci_read_config_byte(dev, pos + PCI_SRIOV_FUNC_LINK, &iov->link);
+ if (!dev->bus->number) /* Root Complex Integrated Endpoint */
+ iov->link = PCI_DEVFN(PCI_SLOT(dev->devfn), iov->link);
if (pdev)
iov->dev = pci_dev_get(pdev);
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2009-06-03 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 5:41 Yu Zhao [this message]
2009-06-04 5:33 ` [PATCH] Dom0 PCI: fix SR-IOV function dependency link problem Isaku Yamahata
2009-06-04 12:38 ` Yu Zhao
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=4A260D0E.1010703@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.