[Xen-devel] Backend in user space, how is its kernel dev unregistered?

[Markus Armbruster <armbru@xxxxxxxxxx>]

There's a curious asymmetry in how Xen backend devices are registered
and unregistered.

Registering is the job of xenbus_probe.c: it watches xenstore, and when
a device node shows up, it calls device_register().

Unregistering is the device driver's job: it watches xenstore, and when
it sees the front end shut down, it calls device_unregister().

But what if the device driver is in user space?  vfb and vkbd are.  I
can't see how their kernel devices can ever get unregistered.

If that is true, any ideas on how to plug the leak?

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