29 Nov
2021
29 Nov
'21
4:22 p.m.
Hi Etienne,
I can add a P-R in optee_os.
Based on my quick testing it appears to be a simple one line change unless I've overlooked something.
Thanks John
core/arch/arm/kernel/boot.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/core/arch/arm/kernel/boot.c b/core/arch/arm/kernel/boot.c index 09c1b811..58bf50cd 100644 --- a/core/arch/arm/kernel/boot.c +++ b/core/arch/arm/kernel/boot.c @@ -1132,7 +1132,7 @@ static void discover_nsec_memory(void) const struct core_mmu_phys_mem *mem_begin = NULL; const struct core_mmu_phys_mem *mem_end = NULL; size_t nelems; - void *fdt = get_external_dt(); + void *fdt = get_dt();
if (fdt) { mem = get_nsec_memory(fdt, &nelems);
--
2.17.1
-----Original Message-----
From: Etienne Carriere etienne.carriere@linaro.org
Sent: Monday, November 22, 2021 10:17 AM
To: John Linn linnj@xilinx.com; op-tee@lists.trustedfirmware.org
Subject: Fwd: Embedded DT (CFG_EMBED_DT) with dynamic shared memory (CFG_CORE_DYN_SHM) in optee-os
Hello John,
> From: John Linn linnj@xilinx.com
> Date: Thu, Nov 18, 2021 at 10:24 PM
> Subject: Embedded DT (CFG_EMBED_DT) with dynamic shared memory
> (CFG_CORE_DYN_SHM) in optee-os
> To: op-teeATlists.trustedfirmware.org
> <op-teeATlists.trustedfirmware.org>
>
>
> It appears that dynamic shared memory does not work with an embedded DT, but I'm likely missing something. I have it working fine with an external DT.
>
> There is a bit of interaction in kernel/boot.c with the two configuration options and my testing is not seeing it work with 3.14 and master looks the same viewing it.
>
> get_external_fdt() is called which does not work with the embedded DT it appears to me.
Indeed the current implementation gets the main memory size from the external non-secure DTB.
This memory is mainly REE memory and can tbe used as shared memory.
It looks reasonable to get the same info from the embedded DTB instead but the point to discuss, IMO, is whether the memory nodes of OP-TEE secure DT relate to OP-TEE "secure memory" or to system-wide (possibly
non-secure) memory. In the former case, that information could not be used to define the "non-secure shareable address ranges".
Feel free to create a P-R in optee_os for that purpose (something like try with embedded_dt() then fallback to externalè_dt()),
Regards,
Etienne
>
> Any hints or advice?
>
> Thanks
> John