| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [RFC PATCH 33/35] Add the Xenbus sysfs and virtual devic
Greg KH wrote:
On Tue, May 09, 2006 at 02:53:14PM -0700, Chris Wright wrote:
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?
Hi Greg,
XenStore is a shared namespace (similar to sysfs or open firmware)
between domains. The interdomain communication primitives exposed by
Xen are very lowlevel (virtual IRQ and shared memory). XenStore is
implemented on top of these primitives and provides some higher level
operations (read a key, write a key, enumerate a directory, notify when
a key changes value).
We use XenStore to implement our virtual drivers (this infrastructure is
called XenBus). The drivers are split between a backend and frontend.
The frontend is the portion of the driver that runs in the guest and the
backend is the portion of the driver that runs in the host (and actually
virtualizes the underlying device).
The xenbus_mkdir, etc. functions you see operate on XenStore.
Regards,
Anthony Liguori
thanks,
greg k-h
------------------------------------------------------------------------
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxx
https://lists.osdl.org/mailman/listinfo/virtualization
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home