|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid
On 5/19/06, Jeremy Katz <katzj@xxxxxxxxxx> wrote:
> Let me copy/paste from my previous message you replied to and quoted:
> it was only added to support driver domains getting information about
> the devices to configure.
But isn't the device configuration there happening from the kernel?
I'll admit I haven't played with getting any of the device passthrough
stuff going since those patches went in. I'm just not clear on what
benefit having userspace being able to frob at xenstore from domU really
has. And in any case, getting it upstream is going to be an uphill
battle at best
For some of the device setup, it is more flexible if it happens in
userspace. For example, figuring out what device a given name
corresponds too (needs lookup in /dev) or binding a loop device for a
file backed vbd.
Instead of inventing yet another interface for the kernel to
communicate with our hotplug scripts (and back), we decided to use
xenstore.
christian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH] /sys/hypervisor/uuid, Markus Armbruster
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Markus Armbruster
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Keir Fraser
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Markus Armbruster
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Keir Fraser
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Jeremy Katz
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Keir Fraser
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Jeremy Katz
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Christian Limpach
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Jeremy Katz
- Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid, Anthony Liguori
|
|
|
|
|