Re: [Xen-devel] [PATCH] Add code to track the address of the VM generation id buffer across a

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Ian Campbell
> Sent: 01 December 2011 14:25
> To: Paul Durrant
> Cc: Konrad Rzeszutek Wilk; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] [PATCH] Add code to track the address of
> the VM generation id buffer across a
> 
> On Thu, 2011-12-01 at 11:54 +0000, Paul Durrant wrote:
> > Would the following be sufficient?
> >
> >   Paul
> >
> > diff -r 62ff6a318c5d docs/man/xl.cfg.pod.5
> > --- a/docs/man/xl.cfg.pod.5     Wed Nov 30 16:59:58 2011 -0800
> > +++ b/docs/man/xl.cfg.pod.5     Thu Dec 01 11:52:58 2011 +0000
> > @@ -484,6 +484,12 @@ of Xen) within a Xen guest or to support
> which
> > uses hardware virtualisation extensions (e.g. Windows XP
> > compatibility mode on more modern Windows OS).
> >
> > +=item B<generation_id=NUMBER>
> > +
> > +This value will be exposed inside the guest at an address which
> can
> > +be determined by evaluating the ADDR package of an ACPI device
> with
> > +_CID "VM_Gen_Counter".
> 
> Belongs more in the "Support for Paravirtualisation of HVM Guests"
> section, which is just below? The "Processor and Platform Features"
> is more about things which are optional (at least in theory) on real
> systems.
> 

Ok.

> Since the semantics of the number itself are up to the toolstack and
> this toolstack defers this requirement up to the user it should
> probably also say something along the lines of:
> 
>         The semantics of this value are guest dependent and it is up
> to
>         the user to ensure those semantics are met.
> 

Ok, I'll add something to that effect.

  Paul

> (even better would be to implement something meaningful in xl,
> obviously)
> 


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