Hi,
I am booting True Dom0-less on Xilinx ZynqMP UltraScale+ using Xen 4.11,
taken from https://github.com/Xilinx/xen.
The system has 2GB of RAM (0x00000000 - 0x80000000) of which Xen and the DomU
have an allocation of 1.25GB, per this memory map:
1. DomU1: 0x60000000 - 0x80000000
2. DomU2: 0x40000000 - 0x60000000
3. Xen: 0x30000000 - 0x40000000
I am able to support True Dom0-less by means of the patch/hack demonstrated
By Stefano Stabellini at https://youtu.be/UfiP9eAV0WA?t=1746.
I was able to forcefully put the Xen binary at the address range immediately
below 0x40000000 by means of modifying get_xen_paddr() - in itself an ugly hack.
My questions are:
1. Since Xen performs runtime allocations from its heap, it is allocating
downwards from 0x80000000 - thereby "stealing" memory from DomU1.
Can I force the runtime allocations to be from a specific address range?
2. Has the issue of physical memory map address maps been addressed by Xen for embedded?
Thank you.
Dov
The information in this e-mail transmission contains proprietary and business
sensitive information. Unauthorized interception of this e-mail may constitute
a violation of law. If you are not the intended recipient, you are hereby
notified that any review, dissemination, distribution or duplication of this
communication is strictly prohibited. You are also asked to contact the sender
by reply email and immediately destroy all copies of the original message.
I am booting True Dom0-less on Xilinx ZynqMP UltraScale+ using Xen 4.11,
taken from https://github.com/Xilinx/xen.
The system has 2GB of RAM (0x00000000 - 0x80000000) of which Xen and the DomU
have an allocation of 1.25GB, per this memory map:
1. DomU1: 0x60000000 - 0x80000000
2. DomU2: 0x40000000 - 0x60000000
3. Xen: 0x30000000 - 0x40000000
I am able to support True Dom0-less by means of the patch/hack demonstrated
By Stefano Stabellini at https://youtu.be/UfiP9eAV0WA?t=1746.
I was able to forcefully put the Xen binary at the address range immediately
below 0x40000000 by means of modifying get_xen_paddr() - in itself an ugly hack.
My questions are:
1. Since Xen performs runtime allocations from its heap, it is allocating
downwards from 0x80000000 - thereby "stealing" memory from DomU1.
Can I force the runtime allocations to be from a specific address range?
2. Has the issue of physical memory map address maps been addressed by Xen for embedded?
Thank you.
Dov
The information in this e-mail transmission contains proprietary and business
sensitive information. Unauthorized interception of this e-mail may constitute
a violation of law. If you are not the intended recipient, you are hereby
notified that any review, dissemination, distribution or duplication of this
communication is strictly prohibited. You are also asked to contact the sender
by reply email and immediately destroy all copies of the original message.