Re: [RFC PATCH 33/35] Add the Xenbus sysfs and virtual device hotplug driver.

From: Greg KH
Date: Tue May 09 2006 - 18:03:05 EST


On Tue, May 09, 2006 at 02:53:14PM -0700, Chris Wright wrote:
> * Greg KH (greg@xxxxxxxxx) wrote:
> > And what are you doing with the different "levels"? Is there some
> > description of how you are using sysfs for this? Busses should not be
> > "nested", devices should. How does sysfs look with this code in it?
> > What is the /sys/bus/ structure? What is the /sys/devices/ structure?
>
> e.g.
>
> /sys/bus/xen
> |-- devices
> | |-- vbd-51713 -> ../../../devices/xen/vbd-51713
> | `-- vif-0 -> ../../../devices/xen/vif-0
> `-- drivers
> `-- vbd
> |-- bind
> |-- unbind
> `-- vbd-51713 -> ../../../../devices/xen/vbd-51713
>
> /sys/devices/xen
> |-- uevent
> |-- vbd-51713
> | |-- block:xvda1 -> ../../../block/xvda1
> | |-- bus -> ../../../bus/xen
> | |-- devtype
> | |-- driver -> ../../../bus/xen/drivers/vbd
> | |-- nodename
> | `-- uevent
> `-- vif-0
> |-- bus -> ../../../bus/xen
> |-- devtype
> |-- nodename
> `-- uevent

<snip>

> > What is the "frontend/backend" relationship here?
>
> do you mean in sysfs? or more in general?

Either. You seem to mention a lot of nested depths in sysfs or "files",
yet your above tree doesn't show that. And I don't understand what you
mean by frontend/backend here either? Is it a sysfs thing? Or a Xen
thing?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/