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: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
From: "Yu Ke" <mr.yuke@xxxxxxxxx>
Date: Wed, 1 Nov 2006 21:14:49 +0800
Cc: Christian Limpach <christian.limpach@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Huang, Xinmei" <xinmei.huang@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:34:57 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RBJ7bZ4jH5jR4w9Z7PSMUok7vYxxSVTm0kvHURdb30WwpvmkbAkxeRqLlv/gIdlOyZzvX6v6bI4SI3G/dhPtUqPa4IsGf4kgnka3pf/vDNrcF2Pu/GA6iP/vzV/QQcZcbzeFtLjjfkb20T7XR5tx/JiuzAI/nKFkkiho3nsx/gA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8A87A9A84C201449A0C56B728ACF491E01F6B5@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <8A87A9A84C201449A0C56B728ACF491E01F6B5@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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