From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v1 1/2] arm: Add ability to relocate Xen in over 4GB space Date: Fri, 10 Apr 2015 15:49:42 +0100 Message-ID: <5527E306.10104@citrix.com> References: <1428496597-18981-1-git-send-email-oiurii.konovalenko@globallogic.com> <1428496597-18981-2-git-send-email-oiurii.konovalenko@globallogic.com> <552551B9.2040602@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrii Anisov Cc: Iurii Konovalenko , Ian Campbell , Stefano Stabellini , Julien Grall , Tim Deegan , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 10/04/15 15:38, Andrii Anisov wrote: > Julien, > >>> Secondary CPUs run on unrelocated copy of Xen until turning on MMU. >>> After turning on MMU secondary CPUs run on relocated copy of Xen. >> >> The non-relocated copy of Xen is not marked as reserved. So Xen may >> allocate the area for his own purpose before the secondary CPU has boot. > > Could you please clarify how the same issue resolved with the piece of > bootloader code which implements secondary processors wfe in HYP mode > and jump to hypervisor? I'm not sure to understand the question. Currently, Xen add a bootmodule (see start_xen) to cover Xen. The base address is updated once Xen is relocated. You may want to add a bootmodule for the non-relocated Xen. I hope it answers to your question. Regards, -- Julien Grall