On Tue, 2007-09-25 at 08:36 +0200, Arnd Bergmann wrote:
> On Tuesday 25 September 2007, Rusty Russell wrote:
> > I don't mind: we could expose it.
> 
> What I mean with setting the parent appropriately is not to have a global
> device that is used by the hv-specific probing code, but to make sure
> that each of them provides their own one. The bus_type should either be
> global or provide the wrappers for device_register and driver_register
> that you have, but the host bridge device belongs with the code that
> probes it. E.g. when all virtio devices are behind PCI bridges, there
> does not need to be an empty /virtio or /lguest device node at all.

Right, that makes sense.  I'll shift this "virtio" device node out to
the lguest code.

Thanks!
Rusty.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to