Hello Stefano,
On 07.07.18 02:11, Stefano Stabellini wrote:
Extend allocate_memory to work for non 1:1 mapped domUs. Specifically,
memory allocated for domU will be mapped into the domU pseudo-physical
address space at the appropriate addresses according to the guest memory
map: GUEST_RAM0_BASE and GUEST_RAM1_BASE.
I would speculate about GUEST_RAMx_BASE and GUEST_RAMx_SIZE macros.
Those values might not fit the real SoC memory map. And it becomes a
problem once we decided to assign some peripheral directly to the guest
because a RAM space specified to VM would overlap with IO range of the
assigned device.
In my practice, we always align those macros with the SoC memory map.
This becomes more convenient and practical than IO remapping.
It might be the moment to get those values configurable for the guests.
At least for those, which are configured from the device tree. Here
naturally fit making `memory` property similar to `reg` - the list of
<base, size> values.
--
*Andrii Anisov*
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
