netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Mark D Rustad <mark.d.rustad@intel.com>, bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH 1/2] pci: Add dev_flags bit to access VPD through function 0
Date: Tue, 02 Jun 2015 10:48:48 -0700	[thread overview]
Message-ID: <556DEC80.70206@redhat.com> (raw)
In-Reply-To: <20150602170414.6252.48036.stgit@mdrustad-wks.jf.intel.com>

On 06/02/2015 10:04 AM, Mark D Rustad wrote:
> Add a dev_flags bit, PCI_DEV_FLAGS_VPD_REF_F0, to access VPD through
> function 0 to provide VPD access on other functions. This solves
> concurrent access problems on many devices without changing the
> attributes exposed in sysfs. Never set this bit on funciton 0 or
> there will be an infinite recursion.
>
> Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
> ---
>   drivers/pci/access.c |   39 ++++++++++++++++++++++++++++++++++++++-
>   include/linux/pci.h  |    2 ++
>   2 files changed, 40 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/access.c b/drivers/pci/access.c
> index d9b64a175990..e435c087c354 100644
> --- a/drivers/pci/access.c
> +++ b/drivers/pci/access.c
> @@ -439,6 +439,40 @@ static const struct pci_vpd_ops pci_vpd_pci22_ops = {
>   	.release = pci_vpd_pci22_release,
>   };
>   
> +static ssize_t pci_vpd_f0_read(struct pci_dev *dev, loff_t pos, size_t count,
> +			       void *arg)
> +{
> +	struct pci_dev *tdev = pci_get_slot(dev->bus, PCI_SLOT(dev->devfn));
> +	ssize_t ret;
> +
> +	if (!tdev)
> +		return -ENODEV;
> +
> +	ret = pci_read_vpd(tdev, pos, count, arg);
> +	pci_dev_put(tdev);
> +	return ret;
> +}
> +
> +static ssize_t pci_vpd_f0_write(struct pci_dev *dev, loff_t pos, size_t count,
> +				const void *arg)
> +{
> +	struct pci_dev *tdev = pci_get_slot(dev->bus, PCI_SLOT(dev->devfn));
> +	ssize_t ret;
> +
> +	if (!tdev)
> +		return -ENODEV;
> +
> +	ret = pci_write_vpd(tdev, pos, count, arg);
> +	pci_dev_put(tdev);
> +	return ret;
> +}
> +

I'm pretty sure these could cause some serious errors if you direct 
assign the device into a VM since you then end up with multiple devices 
sharing a bus.  Also it would likely have side-effects on a LOM (Lan On 
Motherboard) as it also shares the bus with multiple non-Ethernet devices.

I believe you still need to add something like a check for 
!pci_is_root_bus(dev->bus) before you attempt to grab function 0.  It 
probably also wouldn't hurt to check the dev->multifunction bit before 
running this code since it wouldn't make sense to go chasing down the 
VPD on another function if the device doesn't have one.  You could 
probably do that either as a part of this code, or perhaps put it in the 
quirk.

- Alex

- Alex

  reply	other threads:[~2015-06-02 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 17:04 [PATCH 0/2] pci: Provide a flag to access VPD through function 0 Mark D Rustad
2015-06-02 17:04 ` [PATCH 1/2] pci: Add dev_flags bit " Mark D Rustad
2015-06-02 17:48   ` Alexander Duyck [this message]
2015-06-02 18:15     ` [Intel-wired-lan] " Rustad, Mark D
2015-06-02 17:04 ` [PATCH 2/2] pci: Add VPD quirk for Intel Ethernet devices Mark D Rustad

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=556DEC80.70206@redhat.com \
    --to=alexander.h.duyck@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.d.rustad@intel.com \
    --cc=netdev@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 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).