WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64

To: "Yu, Ke" <ke.yu@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Christian Limpach" <christian.limpach@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 1 Nov 2006 11:16:02 -0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Huang, Xinmei" <xinmei.huang@xxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:50:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbwn3GTeQX7YqjuSrWHsAKaEOOOQwANzaogAF+2ZZACaGUm0AAEkMSwAAbrrDAAAklb1wAAHUJQABe5ZSAAFQfgUAAC850gAANOseAAAH1PUAABJGTgABiDSAAACswJ4AAAgesAAAV2EuA=
Thread-topic: [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