mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bodong Wang <bodong@mellanox.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <saeedm@mellanox.com>,
	Eli Cohen <eli@mellanox.com>
Subject: Re: [PATCH] pci/sriov: Add an option to probe VFs or not before enabling SR-IOV
Date: Mon, 20 Mar 2017 22:38:43 -0500	[thread overview]
Message-ID: <70e91a67-7d15-671f-bba3-de00dd51406d@mellanox.com> (raw)
In-Reply-To: <20170321002445.GA24862@gwshan>

On 3/20/2017 7:24 PM, Gavin Shan wrote:
> On Mon, Mar 20, 2017 at 06:34:23PM -0500, Bodong Wang wrote:
>> On 3/20/2017 6:07 PM, Gavin Shan wrote:
>>> On Mon, Mar 20, 2017 at 05:14:34PM +0200, 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.
>>>>
>>>> Added a new PCI sysfs interface "sriov_probe_vfs" to control that
>>> >from 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_probe_vfs
>>>>
>>>> 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.
>>>>
>>> Bodong, I'm not sure if there is a requirement to load driver for the
>>> specified number of VFs? That indicates no driver will be loaded for
>>> other VFs. If so, this interface might serve the purpose as well.
>> Gavin, thanks for the review. That is indeed an interesting suggestion.
>> Theoretically,  we can change that probe_vfs from boolean to integer. And use
>> it as a counter to probe the first N VFs(if N < total_vfs).  Let's see if
>> there are any objections.
> Ok.
>
>>> +#ifdef CONFIG_PCI_IOV
>>> +	if (!pci_dev->is_virtfn ||
>>> +	    (pci_dev->is_virtfn && pci_dev->physfn->sriov->probe_vfs)) {
>>> +#endif
>>> +		error = __pci_device_probe(drv, pci_dev);
>>> +		if (error) {
>>> +			pcibios_free_irq(pci_dev);
>>> +			pci_dev_put(pci_dev);
>>> +		}
>>> +#ifdef CONFIG_PCI_IOV
>>> 	}
>>> +#endif
>>>
>>> I think it's reasonable to have a inline function for this check:
>> It's doable, but what's the benefit?
>>> #ifdef CONFIG_PCI_IOV
>>> static inline bool pci_device_can_probe(struct pci_dev *pdev)
>>> {
>>> 	return (!pdev->is_virtfn || pdev->physfn->sriov->probe_vfs);
>> should be return (!pdev->is_virtfn || (pci_dev->is_virtfn &&
>> pci_dev->physfn->sriov->probe_vfs));
>>
>> We want to probe that device if 1) it's a PF 2) it'a VF and probe_vfs is set
>>> }
>>> #else
>>> static inline bool pci_device_can_probe(struct pci_dev *pdev)
>>> {
>>> 	return true;
>>> }
>> This function will be a waste if CONFIG_PCI_IOV is not defined.
>>> #endif
> It makes the code a bit clean. Nope, the proposed conditional
> expression is elaborate. Yeah, the purpose is exactly same as
> you said: probe driver for non-VF or VFs that were allowed.
>
>       (!pdev->is_virtfn || pdev->physfn->sriov->probe_vfs);
>
> When pdev->is_virtfn is flase, "pdev->physfn->sriov->probe_vfs"
> doesn't take effect. Otherwise, it means pdev->is_virtfn is true
> indirectly and going to check "pdev->physfn->sriov->probe_vfs".
> So it needn't check pdev->is_virtfn explicitly in later case,
> but it isn't wrong :)
>
> Thanks,
> Gavin
>
Make sense :) Will apply in V1.

Thanks,

Bodong

  reply	other threads:[~2017-03-21  3:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 15:14 bodong
2017-03-20 23:07 ` Gavin Shan
2017-03-20 23:34   ` Bodong Wang
2017-03-21  0:24     ` Gavin Shan
2017-03-21  3:38       ` Bodong Wang [this message]
2017-03-21  4:57     ` Alex Williamson
2017-03-21  5:43       ` Gavin Shan
2017-03-21  6:01         ` Alex Williamson
2017-03-21  9:25           ` Gavin Shan
2017-03-21 14:23             ` Alex Williamson
2017-03-21 14:34               ` Eli Cohen
2017-03-21 23:48                 ` Gavin Shan
2017-03-21 23:46               ` Gavin Shan
2017-03-21 13:43           ` Bodong Wang

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=70e91a67-7d15-671f-bba3-de00dd51406d@mellanox.com \
    --to=bodong@mellanox.com \
    --cc=bhelgaas@google.com \
    --cc=eli@mellanox.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --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

all inboxes | Powered by JetHome®