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

Re: [Embedded-pv-devel] Memory usage on Aaarch64



Hello,

I already answered to this question on xen-devel. Please have a look at [1]

[1] https://lists.xenproject.org/archives/html/xen-devel/2017-12/msg01176.html

Cheers,


On 12 December 2017 at 20:20, Michael.rosswood
<michael.rosswood@xxxxxxxxxxxxxx> wrote:
> Hello everyone,
>
> I'm trying to understand how Xen and each domain use RAM
> on Aarch64 systems.
>
> My understanding is that during Xen startup, Xen will copy
> itself to upper physical memory, and continue to run from there,
> correct? Is there any information on how the heap is handled here
> compared to Xen on ARM (e.g. domheap and xenheap)?
>
> From http://www.wiki.xilinx.com/Xen+Hypervisor+internals, it looks
> like all memory for dom0 is mapped 1:1. Does this mean that dom0
> keeps physical memory from address 0 up until dom0_mem?
>
> Further below, it mentions that each domU has an artificial memory
> map. But I'm not sure what this looks like in memory. Could someone
> clarify how this is done?
>
> Thanks,
> Michael
>
> _______________________________________________
> Embedded-pv-devel mailing list
> Embedded-pv-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/embedded-pv-devel

_______________________________________________
Embedded-pv-devel mailing list
Embedded-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/embedded-pv-devel

 


Rackspace

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