From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Backend in user space, how is its kernel dev unregistered?
Date: Thu, 05 Mar 2009 14:17:38 +0100 [thread overview]
Message-ID: <49AFD0F2.5030704@redhat.com> (raw)
In-Reply-To: <87y6vkw3b5.fsf@pike.pond.sub.org>
> The vfb and vkbd backends live in user space, i.e. there is no backend
> driver in the kernel. device_unregister() never gets called. This is a
> resource leak.
When a domain shuts down xend will cleanup the backend device entries in
xenstore, which in turn kills the devices. At least they disappear from
sysfs on my box ...
cheers,
Gerd
next prev parent reply other threads:[~2009-03-05 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 19:02 Backend in user space, how is its kernel dev unregistered? Markus Armbruster
2009-03-04 19:14 ` 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 [this message]
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=49AFD0F2.5030704@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=keir.fraser@eu.citrix.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.