All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: bhelgaas@google.com, gwshan@linux.vnet.ibm.com
Cc: linux-pci@vger.kernel.org, Wei Yang <weiyang@linux.vnet.ibm.com>
Subject: [PATCH 0/2] PCI/IOV: fix on offset/stride based on NumVFs change
Date: Mon, 22 Dec 2014 13:48:44 +0800	[thread overview]
Message-ID: <1419227326-12083-1-git-send-email-weiyang@linux.vnet.ibm.com> (raw)

Per SRIOV SPEC sec 3.3.9, 3.3.10, offset/stride may change when NumVFs is
written. While current kernel doesn't update offset/stride with the change of
NumVFs.

This property will also affect the iov bus range in enumeration.

This patch set consists of two patches:
1. Update the offset/stride with NumVFs change
2. Calculate VF bus range on each possilbe NumVFs

Code based on 3.19-rc1 and tested on x86 and powernv platform.
Bus range doesn't chage on current hardware.

Wei Yang (2):
  PCI: Refresh offset/stride after NumVFs is written
  PCI: Calculate the VF bus range on each possible NumVFs

 drivers/pci/iov.c |   54 +++++++++++++++++++++++++++++++++++++++++++++--------
 drivers/pci/pci.h |    1 +
 2 files changed, 47 insertions(+), 8 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2014-12-22  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22  5:48 Wei Yang [this message]
2014-12-22  5:48 ` [PATCH 1/2] PCI: Refresh offset/stride after NumVFs is written Wei Yang
2014-12-22  5:48 ` [PATCH 2/2] PCI: Calculate the VF bus range on each possible NumVFs Wei Yang
2015-01-21 22:54   ` Bjorn Helgaas
2015-01-22  9:42     ` Wei Yang

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=1419227326-12083-1-git-send-email-weiyang@linux.vnet.ibm.com \
    --to=weiyang@linux.vnet.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linux-pci@vger.kernel.org \
    /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.