This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: 64bit xen relocation

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: 64bit xen relocation
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 11 Sep 2008 12:02:37 +0100
Delivery-date: Thu, 11 Sep 2008 04:03:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F024D97AF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckT/B4Ekg5O316vT3ey/Zq7Nwo/UgAAchlT
Thread-topic: 64bit xen relocation
User-agent: Microsoft-Entourage/
On 11/9/08 11:49, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> One question is, why are 0-1M frames also copied to high end
> which are then clobbered immediately? It looks like unnecessary
> if just for leaving a guard range from stray pointers...
> move_memory(e, 0, __pa(&_end) - xen_phys_start);
> /* Poison low 1MB to detect stray pointers to physical 0-1MB. */
> memset(maddr_to_bootstrap_virt(e), 0x55, 1U<<20);

Sure. I suppose it makes the move_memory() arguments a bit simpler than
they'd be if we started at 0x100000.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>