The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bodong Wang <bodong@mellanox.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<saeedm@mellanox.com>, Eli Cohen <eli@mellanox.com>
Subject: Re: [v3] PCI: Add an option to control probing of VFs before enabling SR-IOV
Date: Fri, 14 Apr 2017 10:44:12 -0500	[thread overview]
Message-ID: <e11e080f-241e-7d6e-832d-7e5d819dfc57@mellanox.com> (raw)
In-Reply-To: <20170414153718.GD29349@bhelgaas-glaptop.roam.corp.google.com>

On 4/14/2017 10:37 AM, Bjorn Helgaas wrote:
> On Thu, Apr 13, 2017 at 01:51:40AM +0300, bodong@mellanox.com wrote:
>> From: Bodong Wang <bodong@mellanox.com>
>>
>> Sometimes it is not desirable to probe the virtual functions after
>> SRIOV is enabled. This can save host side resource usage by VF
>> instances which would be eventually probed to VMs.
>>
>> Add a new PCI sysfs interface "sriov_drivers_autoprobe" to control
>> that from the PF, all current callers still retain the same
>> functionality. To modify it, echo 0/n/N (disable probe) or 1/y/Y
>> (enable probe) to:
>>
>> /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
>>
>> Note that, the choice must be made before enabling VFs. The change
>> will not take effect if VFs are already enabled. Simply, one can set
>> sriov_numvfs to 0, choose whether to probe or not, and then resume
>> sriov_numvfs.
>>
>> Signed-off-by: Bodong Wang <bodong@mellanox.com>
>> Signed-off-by: Eli Cohen <eli@mellanox.com>
>> Reviewed-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>> Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
>> Reviewed-by: Bjorn Helgaas <helgaas@kernel.org>
> Applied to pci/virtualization for v4.12, thanks, Bodong!
Thank you! Bjorn/Alex/Gavin.

      reply	other threads:[~2017-04-14 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 22:51 [v3] PCI: Add an option to control probing of VFs before enabling SR-IOV bodong
2017-04-13  2:56 ` Alex Williamson
2017-04-13  5:24   ` Gavin Shan
2017-04-13 14:16     ` Bodong Wang
2017-04-14 15:37 ` Bjorn Helgaas
2017-04-14 15:44   ` Bodong Wang [this message]

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=e11e080f-241e-7d6e-832d-7e5d819dfc57@mellanox.com \
    --to=bodong@mellanox.com \
    --cc=eli@mellanox.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=saeedm@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox