How the memory size set in the qemu.mk file (such as 1057 at this time) is allocated to REE and TEE? about build

[jenswi-linaro]

OP-TEE and the Linux kernel reads this memory configuration from the DTB which QEMU generates when initializing. The value 1057 is mostly used for legacy reasons, it might be possible to use a more even value these days.

[wsp1999]

Then, How do I change the memory ratio between TEE and REE?

[jenswi-linaro]

The secure memory is using a fixed number hardcoded into QEMU, this is only non-secure memory. Unless you're using a static carveout for share memory everything is used by the REE.

[wsp1999]

Does this means that 1057 is only non-secure memory? Where should I modify the fixed number to set the size of the safe memory?

[jenswi-linaro]

It's hardcoded in hw/arm/virt.c in the QEMU source, search for VIRT_SECURE_MEM. If stuff breaks I'm not able to help.

[wsp1999]

If I want to modify the size ratio of safe and non-safe memory in a project, what should I do？

[jenswi-linaro]

The amount of secure memory in the QEMU virt model is constant, so the only way to change the ratio is to change the amount of non-secure memory. I suppose it shouldn't be too hard to add another region with secure memory in QEMU, but I'm afraid I can't help you with that. You can perhaps get help with that on a QEMU mailing list or forum.

[github-actions]

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

[n43e125]

I monitored that when setting memory larger than 1057 while having multiple core settings with -smp 4, it sometimes failed to bring up core 2,3,4. Are there any constraints on memory setting?