Re: [Xen-devel] [PATCH for-4.12 v2 2/2] xen/arm: Stop relocating Xen

[Andrii Anisov <andrii.anisov@xxxxxxxxx>]

On 14.12.18 17:52, Andrii Anisov wrote:
> Hello Julien,
>
> Let me speculate a bit about the topic.
>
> On 14.12.18 13:44, Julien Grall wrote:
> > At the moment, Xen is relocated towards the end of the memory.
> This statement is not really true. Some time ago, XEN was relocated toward the 
> end of
> the low memory (under 4 GB). Currently, on my board I see some kind of mess:
>
>      (XEN) RAM: 0000000048000000 - 00000000bfffffff
>      (XEN) RAM: 0000000500000000 - 000000057fffffff
>      (XEN) RAM: 0000000600000000 - 000000067fffffff
>      (XEN) RAM: 0000000700000000 - 000000077fffffff
>      (XEN)
>      (XEN) MODULE[0]: 0000000048000000 - 0000000048013000 Device Tree
>      (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
>      (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
>      (XEN)  RESVD[0]: 0000000048000000 - 0000000048013000
>      (XEN)
>      (XEN)
>      (XEN) Command line: dom0_mem=3G console=dtuart dtuart=serial0 
> dom0_max_vcpus=2 bootscrub=0 loglvl=all cpufreq=none tbuf_size=8192 loglvl=all/none 
> guest_loglvl=all/none
>      (XEN) parameter "cpufreq" unknown!
>      (XEN) Placing Xen at 0x000000077fe00000-0x0000000780000000
>      (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078188d81 => 
> 000000077fe00000-000000077ff08d81
>
> As you can see XEN is moved towards the end of the first GB of the low memory 
> instead of the end of under 4GB RAM.
Sorry, I have to recall the piece above. I miscounted zeros in the relocation 
address. XEN is actually set by the end of the RAM above 4GB.


> On my current setup I have two 128MB chunks stolen: one by relocated XEN, kernel module an XSM module, 
Not by relocated XEN, but still by kernel and XSM

--
Sincerely,
Andrii Anisov.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel