|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
2006/11/1, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>:
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.
Maybe I misunderstand something. the only database I see is the
xenstore database, in which we don't want to save nvram data. is there
another database?
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
The reason of two node is that nvram is a bit special, since it need
to communicate with external data file, not just xenstore data.
To be more detail, the qemu need to read and write the data. Writing
is simple: just write to data_in node and trigger watch handler. read
is a little bit complex: qemu write index to data_out first, then
watch handler feed data into data_out, finally qemu read the data_out
node.
if there is xend database, maybe only one node is needed. need more
info from you.
Best Regards
Ke
_______________________________________________
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,
Yu Ke <=
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Ian Pratt
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
|
|
|
|
|