All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Backend in user space, how is its kernel dev unregistered?
Date: Wed, 04 Mar 2009 20:02:27 +0100	[thread overview]
Message-ID: <8763ip158c.fsf@pike.pond.sub.org> (raw)

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?

             reply	other threads:[~2009-03-04 19:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 19:02 Markus Armbruster [this message]
2009-03-04 19:14 ` Backend in user space, how is its kernel dev unregistered? Keir Fraser
2009-03-04 19:17 ` Keir Fraser
2009-03-04 19:51   ` Markus Armbruster
2009-03-04 22:29     ` Keir Fraser
2009-03-05 12:40       ` Markus Armbruster
2009-03-05 13:17         ` Gerd Hoffmann
2009-03-05 13:18         ` Keir Fraser
2009-03-05  9:40     ` Gerd Hoffmann

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=8763ip158c.fsf@pike.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /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.