[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Tue, 9 May 2006 06:38:35 -0700
  • Delivery-date: Tue, 09 May 2006 06:38:50 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZzQAQ++p1uD7eyRb6g/FALd/LChgALUPcg
  • Thread-topic: [Xen-ia64-devel] [Discussion]: dynamic shared_info_va

> > Or specify an architected value and provide a hypercall
> > that allows a guest to change it to a different value if
> > it wishes.
> Do you have any usage model for changing hypercall imm value ?
> I can't imagine a reason.  Changing hypercall imm value is 
> not easy: it is 
> almost hard-coded into the code, it is also used in 
> pal/sal/efi stubs and is 
> a domain-wide value.

The problem only occurs if a future version of Linux or
a future non-Linux guest chooses to use the hypercall
break imm value for some other use.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.