RE: [Xen-ia64-devel] [Discussion]: dynamic shared_info_va

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

> > Note that it may be possible to move some things around
> > to make shared_archinfo contiguous so that it can share
> > the same TR.  I think there was some discussion about this
> > on xen-ia64-devel (along with the above design) some months back.
> I don't understand.  There are two areas: shared_info and 
> shared_archinfo.
> shared_info is per domain while shared_archinfo is per vcpu.

Oops!  The discussion was long ago so I had forgotten the
details.

> > To be complete, the same mechanism should be used for Linux
> > to specify a default "break immediate" value for hypercalls.
> Two possibilities:
> encode immediate value in the __xen_guest section,
> or use the imm of the first break (with a magic value).

Or specify an architected value and provide a hypercall
that allows a guest to change it to a different value if
it wishes.

Dan

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