linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linux-pci@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, bhelgaas@google.com,
	benh@kernel.crashing.org, mpe@ellerman.id.au, clsoto@us.ibm.com,
	Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH v3 0/2] Disable VF's memory space on updating IOV BARs
Date: Wed, 26 Oct 2016 12:15:34 +1100	[thread overview]
Message-ID: <1477444536-29612-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)

This moves pcibios_sriov_enable() to the point before VF and VF BARs
are enabled on PowerNV platform. Also, pci_update_resource() is used
to update IOV BARs on PowerNV platform, the PF might have been functional
when the function is called. We shouldn't disable PF's memory decoding
at that point. Instead, the VF's memory space should be disabled.

Changelog
=========
v3:
  * Disable VF's memory space when IOV BARs are updated in
    pcibios_sriov_enable().
v2:
  * Added one patch calling pcibios_sriov_enable() before the VF
    and VF BARs are enabled.

Gavin Shan (2):
  PCI: Call pcibios_sriov_enable() before IOV BARs are enabled
  PCI: Disable VF's memory space on updating IOV BAR in
    pci_update_resource()

 drivers/pci/iov.c       | 14 +++++++-------
 drivers/pci/setup-res.c | 28 ++++++++++++++++++++--------
 2 files changed, 27 insertions(+), 15 deletions(-)

-- 
2.1.0

             reply	other threads:[~2016-10-26  1:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  1:15 Gavin Shan [this message]
2016-10-26  1:15 ` [PATCH v3 1/2] PCI: Call pcibios_sriov_enable() before IOV BARs are enabled Gavin Shan
2016-10-26  1:15 ` [PATCH v3 2/2] PCI: Disable VF's memory space on updating IOV BAR in pci_update_resource() Gavin Shan
2016-11-23 23:49 ` [PATCH v3 0/2] Disable VF's memory space on updating IOV BARs Bjorn Helgaas
2016-11-29  3:48   ` Bjorn Helgaas

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=1477444536-29612-1-git-send-email-gwshan@linux.vnet.ibm.com \
    --to=gwshan@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=clsoto@us.ibm.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).