|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Proposal for init/kexec/hotplug format for Xen
I have a few questions about some of the future features:
1) What is the transport going to be for querying/updating? How are you
going to handle security?
2) Are we going to use any sort of standard for storing device
information? If so, what?
3) How does this change the device setup exchange? Right now, a series
of control messages is exchanged so that the back-end can get notified
to create the virtual device and then something has to proxy some
information from the front-end (usually just a shared memory location)
to that backend.
All of this is still necessary right? How does a value being updated
trigger an appropriate event?
Regards,
Anthony Liguori
Included below for your reading pleasure,
Rusty.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
|
|