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

Re: [Xen-devel] [PATCH V5 02/15] Move x86 specific funtions/variables to arch header



On Mon, 2014-09-22 at 11:56 +0100, Jan Beulich wrote:
> >>> On 22.09.14 at 12:52, <Ian.Campbell@xxxxxxxxxx> wrote:
> > On Fri, 2014-09-19 at 09:37 +0100, Jan Beulich wrote:
> >> Hmm, so you're still moving the relocation processing code - why? I
> >> don't recall you having said you're sure you'll not need this on ARM.
> > 
> > ARM relocates itself to the top of memory during bringup already. I
> > don't think we need to do it here as well/instead.
> 
> There are two relocations (on x86) actually: One (always used) is
> to move the hypervisor image to high physical memory. The other
> (needed under UEFI only) is to relocate the hypervisor from where
> the UEFI loader put it (running in physical mode, virtual and
> physical addresses are the same) to its linked virtual address. Are
> you saying that ARM isn't in need of this?

Correct, the main ARM entry point (which the UEFI stub calls) takes care
of enabling paging, including handling the move from (potentially
differing) physical to virtual addresses.

Ian.


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


 


Rackspace

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