From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xenproject.org>
Cc: <david.vrabel@citrix.com>
Subject: Re: [Xen-devel] [PATCH v2] xen/pciback: support driver_override
Date: Fri, 9 Sep 2016 15:27:41 +0100 [thread overview]
Message-ID: <57D2C6DD.2050405@citrix.com> (raw)
In-Reply-To: <69161c4e-02ac-5b02-8c9a-161d2ec2d6ce@suse.com>
On 09/09/16 07:14, Juergen Gross wrote:
> On 08/09/16 16:10, Boris Ostrovsky wrote:
>> On 09/02/2016 08:30 AM, Juergen Gross wrote:
>>> Support the driver_override scheme introduced with commit 782a985d7af2
>>> ("PCI: Introduce new device binding path using pci_dev.driver_override")
>>>
>>> As pcistub_probe() is called for all devices (it has to check for a
>>> match based on the slot address rather than device type) it has to
>>> check for driver_override set to "pciback" itself.
>>>
>>> Signed-off-by: Juergen Gross <jgross@suse.com>
>>> ---
>>> V2: removed now unused label
>>> ---
>>> drivers/xen/xen-pciback/pci_stub.c | 16 ++++++++++------
>>> 1 file changed, 10 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/xen/xen-pciback/pci_stub.c b/drivers/xen/xen-pciback/pci_stub.c
>>> index 258b7c3..85c28f7 100644
>>> --- a/drivers/xen/xen-pciback/pci_stub.c
>>> +++ b/drivers/xen/xen-pciback/pci_stub.c
>>> @@ -25,6 +25,8 @@
>>> #include "conf_space.h"
>>> #include "conf_space_quirks.h"
>>>
>>> +#define PCISTUB_DRIVER_NAME "pciback"
>>> +
>>> static char *pci_devs_to_hide;
>>> wait_queue_head_t xen_pcibk_aer_wait_queue;
>>> /*Add sem for sync AER handling and xen_pcibk remove/reconfigue ops,
>>> @@ -529,16 +531,18 @@ static int pcistub_probe(struct pci_dev *dev, const struct pci_device_id *id)
>>> "don't have a normal (0) or bridge (1) "
>>> "header type!\n");
>>> err = -ENODEV;
>>> - goto out;
>>> }
>>>
>>> + } else if (!dev->driver_override ||
>>> + strcmp(dev->driver_override, PCISTUB_DRIVER_NAME))
>>> + /* Didn't find the device */
>>> + err = -ENODEV;
>>> +
>>> + if (!err) {
>>> dev_info(&dev->dev, "seizing device\n");
>>> err = pcistub_seize(dev);
>>> - } else
>>> - /* Didn't find the device */
>>> - err = -ENODEV;
>>> + }
>>
>> Should devices with pciback override be displayed in
>> /sys/bus/pci/drivers/pciback/slots? If they should then they need to be
>> either added to pcistub_device_ids or kept on some other list.
>
> No, I don't think so. The patch is just needed to _avoid_ having to use
> the slots stuff: without the patch you need something like:
>
> echo 0000:07:10.0 > /sys/bus/pci/devices/0000\:07\:10.0/driver/unbind
> echo 0000:07:10.0 > /sys/bus/pci/drivers/pciback/new_slot
> echo 0000:07:10.0 > /sys/bus/pci/drivers_probe
>
> while with the patch you can use the same mechanism as for similar
> drivers like pci-stub and vfio-pci:
>
> echo pciback > /sys/bus/pci/devices/0000\:07\:10.0/driver_override
> echo 0000:07:10.0 > /sys/bus/pci/devices/0000\:07\:10.0/driver/unbind
> echo 0000:07:10.0 > /sys/bus/pci/drivers_probe
>
> So e.g. libvirt doesn't need special handling for pciback. The slot list
> is necessary for assigning devices to pciback on boot, but I think the
> override mechanism is better for runtime assignment.
Can you include something like this in the commit message?
David
next prev parent reply other threads:[~2016-09-09 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 12:30 [PATCH v2] xen/pciback: support driver_override Juergen Gross
2016-09-08 14:10 ` Boris Ostrovsky
2016-09-08 14:10 ` Boris Ostrovsky
2016-09-09 6:14 ` Juergen Gross
2016-09-09 6:14 ` Juergen Gross
2016-09-09 14:20 ` Boris Ostrovsky
2016-09-09 14:20 ` Boris Ostrovsky
2016-09-09 14:47 ` Juergen Gross
2016-09-09 14:47 ` Juergen Gross
2016-09-09 14:27 ` David Vrabel [this message]
2016-09-09 14:29 ` [Xen-devel] " Juergen Gross
2016-09-09 14:29 ` Juergen Gross
2016-09-09 14:27 ` David Vrabel
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=57D2C6DD.2050405@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 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.