From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Backend in user space, how is its kernel dev unregistered? Date: Thu, 05 Mar 2009 10:40:11 +0100 Message-ID: <49AF9DFB.2020206@redhat.com> References: <87k575yslm.fsf@pike.pond.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87k575yslm.fsf@pike.pond.sub.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Markus Armbruster Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org Markus Armbruster wrote: > Keir Fraser writes: > >> On 04/03/2009 19:02, "Markus Armbruster" wrote: >> >>> 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. >> Presumably these should watch xenstore themselves and tear down state when >> they see state changes from the frontend, or the corresponding xenstore >> directory disappear completely. Just like in the kernel's xenbus_probe.c. >> >> -- Keir > > Stupid question: how can a user space driver get *kernel* devices unregistered? /me is confused. Which kernel device you are talking about? Frontend? That one lives in guest kernel space and should work like all other frontends. Backend? There is no kernel device in the first place. cheers, Gerd