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 08:25:08 -0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Huang, Xinmei" <xinmei.huang@xxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:50:45 -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>
References: <117E3EB5059E4E48ADFF2822933287A4F92D83@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbwn3GTeQX7YqjuSrWHsAKaEOOOQwANzaogAF+2ZZACaGUm0AAEkMSwAAbrrDAAAklb1wAAHUJQABe5ZSAAFQfgUAAC850gAANOseAAAH1PUAABJGTgABiDSAAACswJ4A==
Thread-topic: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
> >> OK. then the xensotor content will looks like this:
> >> nvram = " "                                          # nvram dir
> >>    vti-domain1 = " "                               # domain name
> >>        0 = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"  # 128 characters, data
> >>        offset = 0*64 1 = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"  # 128
> >>        characters, data offset = 1*64 .........
> >>    # skip data block of all 0xff vti-domain2 = " "
> >>        ..........
> >
> > We'll have to think about how this data gets persisted (I'd trigger
a
> > watcher and store it outside of xenstore). Look at the xen-api.hg
tree
> > to see how stuff gets persisted.
> I am not familiar with the xan-api project, so could you please give
more
> info on "trigger a watcher and store it outside of xenstore"? 

See xenbits.xensource.com/ext/xen-api.hg

Various parts of a domain's runtime config are persisted in a database,
and the nvram state could be added to this. There's no good example to
copy as the nvram state is unusual in that its written by both qemu
rather than the control tools. Xenbus watchers let you do this, though.

> Does xenstore
> has the interface to write data outside of xenstore. 

You can register a watcher to be told when someone writes to a section
of the store then arrange to persist the data. You can add this to xend.

> Or do you mean having
> a separate thread to watch, and the thread will write data outside of
> xenstore. In this way, qemu should have ringbuffer to pass the data to
the
> thread.

No extra ring buffer is needed or wanted.

Ian


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel