Re: [Xen-devel] [PATCH] linux: allow pciback to be built as a module

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 8 Mar 2006, at 19:07, Ryan wrote:

> Do you mean if no other driver grabs a device, have that device attach
> to the pcistub driver?
I mean have some way of asking the pcistub driver to late-bind, but not 
have pcistub bind greedily and automatically.
> I have a type of "late binding" support coded up and working, but it
> isn't quite ready for submission yet. You can add/remove PCI slots
> to/from the pcistub driver at run-time. It doesn't automatically 
> pick-up
> devices that don't have a driver, but it is useful for working with the
> bind/unbind driver attributes in sysfs in Linux. This would also be
> useful in scenarios with cardbus where you *may* not know the slot
> numbers in advance. Or if the administrator simply decides to change 
> his
> mind and take, for example, a network card out of service in dom0 and
> put it in a domU or vice versa.
It sounds like you have basically what I'm talking about already 
working. I'm not sure it makes sense to have pciback greedily bind to 
PCI devices. If you don;t have to bind really early (to avoid other 
driver probes during boot) then you can probably leave the bind until 
driver-domain creation.
It'd be great to get a patch for that in the tree, and hook it into the 
tools (so that driver-domain creation fails only if the device is 
already bound to another driver --- currently we fail if the device is 
not already bound to pciback).
 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel