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

Re: [Xen-devel] [PATCH RFC 10/15] libxc: allow caller to specify guest rambase rather than hardcoding

To: Ian Campbell <ian.campbell@xxxxxxxxxx>
From: Julien Grall <julien.grall@xxxxxxxxxx>
Date: Thu, 10 Oct 2013 16:31:31 +0100
Cc: stefano.stabellini@xxxxxxxxxxxxx, tim@xxxxxxx, xen-devel@xxxxxxxxxxxxx
Delivery-date: Thu, 10 Oct 2013 15:31:48 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 10/07/2013 05:39 PM, Ian Campbell wrote:
> It's still hardcoded but it could now be plausibly be made variable.

There is a thread were people asking to change the base address.
For the xl side, how about a parameter in the configuration file?
The default value would be 0.

> 
> TODO: the #if is a bit lame.

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH RFC 10/15] libxc: allow caller to specify guest rambase rather than hardcoding
  - From: Ian Campbell

References:
- [Xen-devel] [PATCH RFC 00/15] xen: arm: 64-bit guest support and domU FDT autogeneration
  - From: Ian Campbell
- [Xen-devel] [PATCH RFC 10/15] libxc: allow caller to specify guest rambase rather than hardcoding
  - From: Ian Campbell

Prev by Date: Re: [Xen-devel] [PATCH RFC 09/15] libxc: arm: rename various bits of zimage load with 32 suffix
Next by Date: Re: [Xen-devel] [PATCH RFC 10/15] libxc: allow caller to specify guest rambase rather than hardcoding
Previous by thread: [Xen-devel] [PATCH RFC 10/15] libxc: allow caller to specify guest rambase rather than hardcoding
Next by thread: Re: [Xen-devel] [PATCH RFC 10/15] libxc: allow caller to specify guest rambase rather than hardcoding
Index(es):
- Date
- Thread

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