|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
> Thank you for the info. It is clear to me now. we will update
> the patch as following:
>
> xenstore:
> local= " "
> domain = ""
> x = "" # domain id
> nvram # nvram dir
> file # nvram file path
> data_in # data index + 64 bytes data,
> 128 characters, for qemu write
> data_out # data index + 64 bytes data, 128
> characters, for qemu read
>
> xend register two watches on data_in node and data_out node.
> * qemu write data: qemu write "index+data" to data_in node,
> xend data_in watch handler will copy the data to persisted file.
> * qemu read data: qemu write index to data_out node; xend
> data_out watch handler copy data from persisted file to
> data_out node; qemu read data_out node.
I don't think you need the file path -- the data should be stored in the
xend 'database' until you come to export the VM.
After initialisation, all the writes to the data will come from qemu,
hence I don't see why you need data_in and data_out. Can't you just have
a 'data' node?
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Ian Pratt
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64,
Ian Pratt <=
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Ian Pratt
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
|
|
|
|
|