From: Eli Cohen <eli@dev.mellanox.co.il>
To: Yuval Mintz <Yuval.Mintz@qlogic.com>
Cc: Eli Cohen <eli@dev.mellanox.co.il>,
"bhelgaas@google.com" <bhelgaas@google.com>,
David Miller <davem@davemloft.net>,
linux-pci <linux-pci@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
"ogerlitz@mellanox.com" <ogerlitz@mellanox.com>,
"yevgenyp@mellanox.com" <yevgenyp@mellanox.com>,
Donald Dutile <ddutile@redhat.com>
Subject: Re: [PATCH RFC] pci: Control whether VFs are probed on pci_enable_sriov
Date: Mon, 8 Dec 2014 21:10:32 +0200 [thread overview]
Message-ID: <20141208191032.GC24790@mtldesk30> (raw)
In-Reply-To: <B5657A6538887040AD3A81F1008BEC63BA669B@avmb3.qlogic.org>
On Sun, Dec 07, 2014 at 08:08:47PM +0000, Yuval Mintz wrote:
> >>>Use a parameter to pci_enable_sriov to control that policy, and modify
> >>>all current callers such that they retain the same functionality.
> >>
> >> What's the end-game here? How eventually would this be controlled?
>
> >You can probe any VF at the hypervisor through sysfs files
> >(bind/unbind). You can also pass them through to a VM. Nothing
> >changes.
>
> If you're not planning on adding a logic to set this, why do we need to
> add a parameter to pci_enable_sriov() - given that all callers use the
> exact same logic?
> [And I don't really think we'd want different devices to behave differently
> by default; That would be confusing for users.]
>
Currently the kerenl will call probe for any device for which there is
a supporting driver and I did not want to change that.
> >>>Use a one shot flag on struct pci_device which is cleared after the
> >>>first probe is ignored so subsequent attempts go through.
> >>
> >> Does a one-shot flag suffice? E.g., consider assigning a VF to VM and
> >> than shutting down the VM. Assuming this feature is disabled,
> >> the VF didn't appear on the hypervisor prior to the assignment but
> >> will appear after its shutdown.
>
> >Sorry, I don't follow you here. Please clarify.
>
> >To be clear, the functionality proposed here is really one shot. It
> >just prevents calling probe once; besides that nothing changes.
>
> What I meant is that device is unbinded after initial probe,
> But in the scenario I've stated above, the VF will become binded once
> it's returned to the hypervisor.
> Now, I understand that what you're trying to achieve - but my question
> is whether what you're REALLY trying to achieve is the ability to have VFs
> which would only be binded to VMs and never to hypervisor [by default]?
No this was not my intention. I guess any driver that wishes to
achieve the same functionality can simply ignore the N first probes after
the call to pci_enable_sriov() where N is the number of VFs it
created.
next prev parent reply other threads:[~2014-12-08 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 13:08 [PATCH RFC] pci: Control whether VFs are probed on pci_enable_sriov Eli Cohen
2014-12-07 17:05 ` Yuval Mintz
2014-12-07 18:42 ` Eli Cohen
2014-12-07 20:08 ` Yuval Mintz
2014-12-08 19:10 ` Eli Cohen [this message]
2014-12-08 19:25 ` Yuval Mintz
2014-12-09 6:43 ` Eli Cohen
2014-12-09 7:07 ` Yuval Mintz
2014-12-09 17:24 ` Don Dutile
2014-12-07 21:32 ` Don Dutile
2014-12-08 18:52 ` Eli Cohen
2015-01-09 18:25 ` Bjorn Helgaas
2015-01-09 18:38 ` Don Dutile
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=20141208191032.GC24790@mtldesk30 \
--to=eli@dev.mellanox.co.il \
--cc=Yuval.Mintz@qlogic.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=ddutile@redhat.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yevgenyp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.