From: Alex Williamson <alex.williamson@redhat.com>
To: Edward Cree <ecree@solarflare.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: pci_sriov_set_totalvfs question
Date: Tue, 29 Jul 2014 08:51:42 -0600 [thread overview]
Message-ID: <1406645502.1011.166.camel@ul30vt.home> (raw)
In-Reply-To: <53D7A9FC.3040001@solarflare.com>
On Tue, 2014-07-29 at 15:04 +0100, Edward Cree wrote:
> Not sure if this list is the right place to ask, but:
> I'm working on fallback code in the sfc driver where in some
> configurations the device won't support using VFs, but will still
> advertise them as present [1]. This is discovered at PF probe time, and
> what I want to do is just set sriov_totalvfs to 0 in this case.
>
> As far as I can tell, pci_sriov_set_totalvfs (drivers/pci/iov.c) is the
> function to call, but I'm confused by the comment on that function which
> states "Should be called from PF driver's probe routine with device's
> mutex held."
>
> Specifically, it's unclear what mutex is meant. struct pci_dev doesn't
> have one; struct pci_sriov /does/ but the struct is only defined in
> drivers/pci/pci.h which I don't appear to be able to include from a
> driver. There's also one in the 'struct device dev' member of struct
> pci_dev, but that seems rather unlikely.
>
> Also, the wording of the comment makes me wonder if being in the PF
> probe routine /implies/ that the mutex is held already, in which case I
> don't have to do anything. This is supported by the only callers,
> igb_probe (via igb_sw_init and igb_probe_vfs) and ixgbe_probe, not
> appearing to take any mutexes before calling pci_sriov_set_totalvfs.
I believe this is referring to device_lock(), which should already be
held on the PF during probe. Thanks,
Alex
next prev parent reply other threads:[~2014-07-29 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 14:04 pci_sriov_set_totalvfs question Edward Cree
2014-07-29 14:51 ` Alex Williamson [this message]
2014-07-30 10:22 ` Edward Cree
2014-07-30 2:48 ` Ethan 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=1406645502.1011.166.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=ecree@solarflare.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 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).