From: Alex Williamson <alex.williamson@redhat.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: "arjan@linux.intel.com" <arjan@linux.intel.com>,
"rjw@sisk.pl" <rjw@sisk.pl>,
"kay.sievers@vrfy.org" <kay.sievers@vrfy.org>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>
Subject: Re: [PATCH] don't allow vfio drivers to bind on driver_attach
Date: Tue, 12 Jan 2016 15:43:40 -0700 [thread overview]
Message-ID: <1452638620.9674.64.camel@redhat.com> (raw)
In-Reply-To: <1452637513.30228.16.camel@intel.com>
On Tue, 2016-01-12 at 22:25 +0000, Keller, Jacob E wrote:
> On Tue, 2016-01-12 at 15:06 -0700, Alex Williamson wrote:
> > We already have a solution in the kernel for this, it's the
> > driver_override interface. Rather than your above example of
> > adding
> > a
> > new ID to the dynamic list for the driver, such that it will
> > automatically probe the device, we reverse the process to allow the
> > device to match the driver. The sequence becomes:
> >
> > echo vfio-pci > /sys/bus/pci/devices/<pci address>/driver_override
> > echo <pci address> > /sys/bus/pci/drivers/<old driver>/unbind
> > echo <pci address> /sys/bus/pci/drivers_probe
> >
> > The old interface is kept around because there are quite a few
> > users
> > of
> > it, some of which would be broken by the proposed manual_bind_only
> > code
> > change, including the example of using driver_override above. This
> > also avoids even the need for pci-stub (which has the same issue),
> > since we can simply put a dummy name in driver_override to avoid a
> > device from matching any driver. Thanks,
> >
> > Alex
>
>
> Hmm, that makes sense. So really I should see about getting the tools
> which currently use the old interface to use a new one?
>
> (Don't we still want/need vfio-pci for other reasons besides just being
> a stub driver?)
Of course, vfio-pci is much more than a stub driver, I was only noting
pci-stub as another meta driver that only uses dynamic adds. It's more
of a side comment that the functionality that pci-stub provides is mostly unnecessary with driver_override. Thanks,
Alex
prev parent reply other threads:[~2016-01-12 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 21:33 [PATCH] don't allow vfio drivers to bind on driver_attach Jacob Keller
2016-01-12 21:33 ` [PATCH] driver: add manual_bind_only option for virtual stub drivers Jacob Keller
2016-01-12 21:53 ` kbuild test robot
2016-01-13 0:02 ` kbuild test robot
2016-01-12 22:06 ` [PATCH] don't allow vfio drivers to bind on driver_attach Alex Williamson
2016-01-12 22:25 ` Keller, Jacob E
2016-01-12 22:43 ` Alex Williamson [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=1452638620.9674.64.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=arjan@linux.intel.com \
--cc=jacob.e.keller@intel.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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.