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

To:	"Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-ia64-devel] [Discussion]: dynamic shared_info_va
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
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id:	Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post:	<mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
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

WARNING - OLD ARCHIVES

xen-ia64-devel

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