> Do you have comments on this patch? NVRAM is a useful feature for IA64 VT-I
> domain, especially for windows 2003 booting.
What does it use the NVRAM for? Is the meaning common across all OSes that use 
it? How many bytes are used? Does the data actually need to be changed, or 
would initializing it to a constant work?
If the data is static, I'm wandering whether it would be better to store this 
data explicitly as part of the domain config rather than referencing another 
file.
Thanks,
Ian
 
> Best Regards
> Ke
>
> Huang, Xinmei <> write on 2006年10月18日 9:40:
> > Hi all,
> > This is the patch for IA64 nvram emulation.
> > Note that Nvram Option in configure file is also prerequisite when
> > creating a Vti domain. -----Original Message-----
> > From: Alex Williamson [mailto:alex.williamson@xxxxxx]
> > Sent: 2006年10月16日 5:18
> > To: Huang, Xinmei
> > Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-ia64-devel][PATCH]Nvram patch
> >
> > On Fri, 2006年10月13日 at 14:37 +0800, Huang, Xinmei wrote:
> >> Hi all,
> >> Nvram emulation solution is that: Qemu uses one file to emulate
> >> nvram. Qemu would load/save relevant content from/to nvram file when
> >> GFW sends command through I/O port. Nvram option is added in config
> >> file to specify a per-domain nvram file path, which can't be shared
> >> by different domains. Nvram file would be created if non-existent. A
> >> new GFW which supports nvram emulation is prerequisite.
> >
> > This looks good, but it's mainly adding new functionality to common
> > code. Other architectures may wish to leverage this work too. I
> > think
> > it should therefore be submitted to xen-devel. Thanks,
> >
> > Alex
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel