- Hafnium - lists.trustedfirmware.org

OP-TEE SP / FF-A v1.1 mem sharing structs

by Olivier Deprez

Hi Jens, We're preparing for the Hafnium changes introducing FF-A v1.1 mem sharing structures, up to: https://review.trustedfirmware.org/c/hafnium/hafnium/+/17399 This is done in a backwards compatible manner, in which a FF-A v1.0 endpoint can still use former mem sharing struct definitions. The requirement is that the endpoint provides the right version either by its manifest, or by calling FFA_VERSION when booted. In order for this transition to happen smoothly it would require OP-TEE to declare the v1.0 version here: https://github.com/jenswi-linaro/build/blob/qemu_sel2/qemu_v8/optee_sp_mani… or call FFA_VERSION first thing: diff --git a/core/arch/arm/kernel/thread_spmc.c b/core/arch/arm/kernel/thread_spmc.c index 240bcffe..893cb63b 100644 --- a/core/arch/arm/kernel/thread_spmc.c +++ b/core/arch/arm/kernel/thread_spmc.c @@ -1382,6 +1382,18 @@ static uint16_t spmc_get_id(void) return args.a2; } +static uint16_t spmc_version(void) +{ + struct thread_smc_args args = { + .a0 = FFA_VERSION, + .a1 = MAKE_FFA_VERSION(FFA_VERSION_MAJOR, FFA_VERSION_MINOR), + }; + + thread_smccc(&args); + + return (uint16_t)args.a0; +} + static struct ffa_mem_transaction *spmc_retrieve_req(uint64_t cookie) { struct ffa_mem_transaction *trans_descr = nw_rxtx.tx; @@ -1519,6 +1531,10 @@ out: static TEE_Result spmc_init(void) { + DMSG("OP-TEE FF-A version %x, SPMC version %x", + MAKE_FFA_VERSION(FFA_VERSION_MAJOR, FFA_VERSION_MINOR), + spmc_version()); + spmc_rxtx_map(&nw_rxtx); my_endpoint_id = spmc_get_id(); DMSG("My endpoint ID %#x", my_endpoint_id); I also noticed PR #5359 introducing the v1.1 mem sharing structures, so this may be another way forward that I did not investigate. https://github.com/jenswi-linaro/optee_os/commit/ddd107f019386d035488e3b4e7… Let me know your opinions. Regards, Olivier.

2 years, 2 months

2
1
0 0

Boot arguments for S-EL1 with SPMC at S-EL2

by Jens Wiklander

Hi Olivier, I'm trying to implement a relocatable OP-TEE binary so it can be loaded at different physical addresses without the need to recompile it. This means that in the case with Hafnium when changing "load-address" or "entrypoint-offset" in the OP-TEE SP manifest there's no need to recompile OP-TEE. For this to work OP-TEE must be able to figure out which memory range it's supposed to reside in. Currently, OP-TEE knows the entry point address from PC and "memory size" from X0. However, the "memory size" is from the "load-address" so "entrypoint-offset" must be subtracted from PC in order to know the allocated memory range. Do you have ideas on how OP-TEE at runtime can determine the allocated memory range? Thanks, Jens

2 years, 2 months

2
2
0 0

load optee at 36bit address

by 梅建强(禹夜)

Hi, experts, We are currently moving optee to a 36bit address to boot with environment that hafnium runs at sel2 as spmc and optee runs at sel1 as sp. Now we have moved hafnium to 0x880000000 and run successfully. Then we tried moving optee to a 36bit address (0x89000000) as well. Although hafnium and optee were successfully initialized on the primary cpu, psci_cpu_on does not seem to be entered into when the secondary cpu is started. The error is as follows: https://github.com/OP-TEE/optee_os/issues/5895 <https://github.com/OP-TEE/optee_os/issues/5895 > Is there any difference between the two cases where hafnium and optee initialize the secondary cpu with different load_address? The log print shows that the secondary cpu has not entered hafnium. Could Hafnium be affected by the 36bit address when dealing with psci related transactions? Regards, Yuye.

2 years, 2 months

1
0
0 0

Re: optee xtest cannot run success stably

by 梅建强(禹夜)

Hi, Jens, We seem to have found the answer following the comment you gave in the issue: https://github.com/OP-TEE/optee_os/issues/5877 <https://github.com/OP-TEE/optee_os/issues/5877 > The reason seems to be that the system has more non-secure memory than what OP-TEE is aware of. When our system memory DRAM size is 32GB, optee has the following configuration for non-secure state memory: #define DRAM1_BASE 0x880000000UL #define DRAM1_SIZE 0x780000000UL On another device, our system memory DRAM size is 64G, optee uses the above configuration for non-secure memory. And xtest will not run stably. In addition, I would like to ask you a few questions in order to understand the problem better. 1. System has more non-secure memory than what OP-TEE is aware of, and optee will not run stably. Why? What is the root cause of TEEC_ERROR_OUT_OF_MEMORY on the issue? I'll do some research on it myself, meanwhile I hope you could give us some insights. 2. When I execute the following command, for i in {1.. 10}; do ./xtest&; done; xtest prints out of order, And the following error is reported: E/TC:032 002 mobj_ffa_get_by_cookie:356 possible spinlock deadlock reminder 1 E/TC:070 mobj_ffa_unregister_by_cookie:310 possible spinlock deadlock reminder 1 E/TC:004 003 mobj_ffa_get_by_cookie:356 possible spinlock deadlock reminder 1 E/TC:058 001 mobj_ffa_get_by_cookie:356 possible spinlock deadlock reminder 1 Then the system hangs and restarts automatically. Does optee currently support running multiple TAs in parallel? Is the maximum number of TAs running in parallel equal to the number of vcpus? 3. The values of MAX_XLAT_TABLES and CFG_CORE_HEAP_SIZE also seem to affect the stability of the system. What configurations, such as the number of cores, should I pay attention to if I want to configure appropriate values for these options? Thanks a lot. Regards, Yuye. ------------------------------------------------------------------ 发件人：Jens Wiklander <jens.wiklander(a)linaro.org> 发送时间：2023年3月20日(星期一) 15:05 收件人：梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> 抄　送：Olivier Deprez <Olivier.Deprez(a)arm.com>; hafnium <hafnium(a)lists.trustedfirmware.org>; op-tee <op-tee(a)lists.trustedfirmware.org> 主　题：Re: optee xtest cannot run success stably Hi Yuye, Comment below. On Mon, Mar 20, 2023 at 4:43 AM 梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> wrote: > Hi, experts > > Recently, we are testing the stability for running optee xtest with environment that hafnium runs as SPMC and optee runs on SPMC as SP. > When we reboot the system, xtest failed on some cases with TEEC_ERROR_OUT_OF_MEMORY. > It seems to be that there is an insufficient memory allocation somewhere in the chain. > We tried the following: > Using Single core startup, > Increased optee MAX_XLAT_TABLES size to 16, > Increased optee CFG_CORE_HEAP_SIZE to 0x2000000, > Increasing the size of optee CFG_TEE_RAM_VA_SIZE to 0x4000000, > Increasing the size of hafnium heap_pages to 8192, > But nothing seems to be working. > Can you offer any help or suggestions? It would help if you could pinpoint the source of the out-of-memory error. I guess it happens somewhere during mobj_ffa_get_by_cookie(), where especially thread_spmc_populate_mobj_from_rx() is interesting. It could also be worth setting CFG_CORE_DUMP_OOM=y, it's easy to enable but I'm afraid it's more of a long shot. Cheers, Jens > Some other configuration for optee is attached in the issue: > https://github.com/OP-TEE/optee_os/issues/5893 <https://github.com/OP-TEE/optee_os/issues/5893 > > > Regards, > Yuye. >

2 years, 2 months

2
1
0 0

optee xtest cannot run success stably

by 梅建强(禹夜)

Hi, experts Recently, we are testing the stability for running optee xtest with environment that hafnium runs as SPMC and optee runs on SPMC as SP. When we reboot the system, xtest failed on some cases with TEEC_ERROR_OUT_OF_MEMORY. It seems to be that there is an insufficient memory allocation somewhere in the chain. We tried the following: Using Single core startup, Increased optee MAX_XLAT_TABLES size to 16, Increased optee CFG_CORE_HEAP_SIZE to 0x2000000, Increasing the size of optee CFG_TEE_RAM_VA_SIZE to 0x4000000, Increasing the size of hafnium heap_pages to 8192, But nothing seems to be working. Can you offer any help or suggestions? Some other configuration for optee is attached in the issue: https://github.com/OP-TEE/optee_os/issues/5893 <https://github.com/OP-TEE/optee_os/issues/5893 > Regards, Yuye.

2 years, 2 months

2
1
0 0

Removing support for HF_DEBUG_LOG

by Kathleen Capella

Hi, With the introduction of FFA_CONSOLE_LOG ABI [1], we are intending to replace and remove support for HF_DEBUG_LOG. This proposal is in review in the following stages: 1) Remove the dependency of hftest VMs on HF_DEBUG_LOG and move to FFA_CONSOLE_LOG [2] 2) Remove the support for HF_DEBUG_LOG (i.e. api_debug_log) from hafnium project. [3] The adoption of FFA_CONSOLE_LOG will allow us to make use of its ability to log multiple characters at a time, as opposed to HF_DEBUG_LOG which writes one character at a time. This improvement will be enabled in a future patch. Also, should [3] be adopted, we will make accompanying changes to tf-a-tests Cactus-based tests. We want to know if there are any concerns about removing support for HF_DEBUG_LOG at this time as we realize other downstream SPs may rely on its support. Thank you, Kathleen Capella [1] feat(console_log): add FFA_CONSOLE_LOG ABI https://review.trustedfirmware.org/c/hafnium/hafnium/+/15334 [2] feat(ffa_console_log): replace hf_debug_log https://review.trustedfirmware.org/c/hafnium/hafnium/+/19513 [3] refactor: remove support for HF_DEBUG_LOG https://review.trustedfirmware.org/c/hafnium/hafnium/+/19681

2 years, 2 months

3
3
0 0

Re: Multi-OPTEE run with Hafnium

by 梅建强(禹夜)

Hi, Olivier I have forgotten one thing, hafnium will invalidate the data cache for the whole image. adrp x0, ORIGIN_ADDRESS adrp x1, image_end sub x1, x1, x0 bl arch_cache_data_invalidate_range I solved this problem by using an address-fixed variable outside the data section instead of the global variabal malloced in data section. In addition, I would like to ask that if multiple optees run on the Hafnium, how to switch the vCPUs of different optees? If one of the optees is expected to be boot under the host OS (post-boot load), how to switch the vCPUs? Thanks for the support. Regards, Yuye. ------------------------------------------------------------------ 发件人：梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> 发送时间：2023年3月11日(星期六) 21:36 收件人：Olivier Deprez <Olivier.Deprez(a)arm.com> 抄　送：Jens Wiklander <jens.wiklander(a)linaro.org>; hafnium(a)lists.trustedfirmware.org <hafnium(a)lists.trustedfirmware.org> 主　题：Re: Multi-OPTEE run with Hafnium Hi, Olivier, The framework message definition that I mentioned is refered in the FF-A Specification. I hope I didn't misinterpret it. The work flow is interpreted as follows: When the system run into the host OS, I want implemented the post-boot load optee as mentioned in the email with Hafnium as SPMC https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18635 <https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18635 > However, when the intialization about hafnium and optee has been finished, SMC_RET8 instruction failed reback from spmd to optee driver. I suspect that there may be some special handling of context needed here. Can you provide some suggestions or help? Regards, Yuye. ------------------------------------------------------------------ 发件人：Olivier Deprez <Olivier.Deprez(a)arm.com> 发送时间：2023年3月7日(星期二) 16:55 收件人：梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> 抄　送：Jens Wiklander <jens.wiklander(a)linaro.org>; hafnium(a)lists.trustedfirmware.org <hafnium(a)lists.trustedfirmware.org> 主　题：Re: Multi-OPTEE run with Hafnium Hi Yuye, I sense those questions are related to downstream changes of yours, and I may not be able to provide accurate answers without seeing the code. Please clarify if the questions are related to the upstream version of Hafnium. See additional comments below [OD]. Regards, Olivier. From: 梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> Sent: 06 March 2023 14:15 To: Olivier Deprez <Olivier.Deprez(a)arm.com> Cc: Jens Wiklander <jens.wiklander(a)linaro.org> Subject: Re: Multi-OPTEE run with Hafnium Hi, Olivier, On this question, I should add something based on the results of my tests. When I enter Hafnium through framwork message, the value of the global variable remains the same. [OD] please explain what is a framework message. When I re-enter the Hafnium image_entry via spmd_init, the global variable is restored to its original value. [OD] I'm not sure about the flow here, it depends about where the variable is declared and whether you have local changes to the hafnium boot flows. Do you know why? Regards, Yuye. ------------------------------------------------------------------ 发件人：梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> 发送时间：2023年3月6日(星期一) 17:00 收件人：Olivier Deprez <olivier.deprez(a)arm.com> 抄　送：Jens Wiklander <jens.wiklander(a)linaro.org> 主　题：Multi-OPTEE run with Hafnium Hi, Olivier, I want to ask a question about variable modification. Before this, let me explain the background about the question. Now, I have run into host OS with Hafnium as spmc and OPTEE as SP. Then the optee driver will send a framwork message to Hafnium to inform it that whether the current state of the host OS is booting or running, [OD] What is a 'framework message' in this context? Is this a custom direct request from driver to optee? so that Hafnium could know which vm node(SP) it should load and init at current state. [OD] Can you please explain why this is required? This current state is represented by a global variable. [OD] do you mean a variable in Hafnium's BSS space? Will the global variable change when message flow exit Hafnium and enter it again? [OD] This depends in which section the variable is declared (see above). Regards, Yuye.

2 years, 2 months

3
2
0 0

Re: Multi-OPTEE run with Hafnium

by 梅建强(禹夜)

Hi, Olivier, The framework message definition that I mentioned is refered in the FF-A Specification. I hope I didn't misinterpret it. The work flow is interpreted as follows: When the system run into the host OS, I want implemented the post-boot load optee as mentioned in the email with Hafnium as SPMC https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18635 <https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18635 > However, when the intialization about hafnium and optee has been finished, SMC_RET8 instruction failed reback from spmd to optee driver. I suspect that there may be some special handling of context needed here. Can you provide some suggestions or help? Regards, Yuye. ------------------------------------------------------------------ 发件人：Olivier Deprez <Olivier.Deprez(a)arm.com> 发送时间：2023年3月7日(星期二) 16:55 收件人：梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> 抄　送：Jens Wiklander <jens.wiklander(a)linaro.org>; hafnium(a)lists.trustedfirmware.org <hafnium(a)lists.trustedfirmware.org> 主　题：Re: Multi-OPTEE run with Hafnium Hi Yuye, I sense those questions are related to downstream changes of yours, and I may not be able to provide accurate answers without seeing the code. Please clarify if the questions are related to the upstream version of Hafnium. See additional comments below [OD]. Regards, Olivier. From: 梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> Sent: 06 March 2023 14:15 To: Olivier Deprez <Olivier.Deprez(a)arm.com> Cc: Jens Wiklander <jens.wiklander(a)linaro.org> Subject: Re: Multi-OPTEE run with Hafnium Hi, Olivier, On this question, I should add something based on the results of my tests. When I enter Hafnium through framwork message, the value of the global variable remains the same. [OD] please explain what is a framework message. When I re-enter the Hafnium image_entry via spmd_init, the global variable is restored to its original value. [OD] I'm not sure about the flow here, it depends about where the variable is declared and whether you have local changes to the hafnium boot flows. Do you know why? Regards, Yuye. ------------------------------------------------------------------ 发件人：梅建强(禹夜) <meijianqiang.mjq(a)alibaba-inc.com> 发送时间：2023年3月6日(星期一) 17:00 收件人：Olivier Deprez <olivier.deprez(a)arm.com> 抄　送：Jens Wiklander <jens.wiklander(a)linaro.org> 主　题：Multi-OPTEE run with Hafnium Hi, Olivier, I want to ask a question about variable modification. Before this, let me explain the background about the question. Now, I have run into host OS with Hafnium as spmc and OPTEE as SP. Then the optee driver will send a framwork message to Hafnium to inform it that whether the current state of the host OS is booting or running, [OD] What is a 'framework message' in this context? Is this a custom direct request from driver to optee? so that Hafnium could know which vm node(SP) it should load and init at current state. [OD] Can you please explain why this is required? This current state is represented by a global variable. [OD] do you mean a variable in Hafnium's BSS space? Will the global variable change when message flow exit Hafnium and enter it again? [OD] This depends in which section the variable is declared (see above). Regards, Yuye.

2 years, 2 months

1
0
0 0

Re: ffa memory problems ask for help

by Wangyuan (ange, IT)

Hi, Olivier, It means fail in ffa_send_check_transition call. Current my new problem is orig_from_mode error in ffa_send_check_transition and ffa_relinquish_check_trasition, orig_to_mode error in ffa_retrirvr_check_transition. When I run crypto xtest case in optee, there is a possibility that the check fail to be triggered. Such as: [cid:image001.png@01D951B0.8B2CC000] [cid:image002.png@01D951B0.8B2CC000] [cid:image003.jpg@01D951B1.0F4DF9D0] I'm guessing it has something to do with the fact that I don't have a VM on the ree side. Do you have some ideas about this scenario. Regards, Wangyuan 发件人: Olivier Deprez [mailto:Olivier.Deprez@arm.com] 发送时间: 2023年3月7日 20:35 收件人: Wangyuan (ange, IT) <wangyuan46(a)huawei.com> 抄送: zhouguangwei (C) <zhouguangwei5(a)huawei.com>; lingmingqiang <lingmingqiang(a)huawei.com>; hafnium <hafnium(a)lists.trustedfirmware.org>; Jens Wiklander <jens.wiklander(a)linaro.org> 主题: Re: ffa memory problems ask for help Hi Wangyuan, I believe it's likely that problem 1 is a side effect of problem 2. My guess is, after the maximum heap pages count is reached because of problem 2, it may lead to problem 1. For the sake of completion for problem 1, when you say 'mask the exception handling of this branch', does this mean that Hafnium hits some S2 page fault, or panics? Regards, Olivier. ________________________________ From: Wangyuan (ange, IT) <wangyuan46(a)huawei.com<mailto:wangyuan46@huawei.com>> Sent: 07 March 2023 12:33 To: Olivier Deprez <Olivier.Deprez(a)arm.com<mailto:Olivier.Deprez@arm.com>> Cc: zhouguangwei (C) <zhouguangwei5(a)huawei.com<mailto:zhouguangwei5@huawei.com>>; lingmingqiang <lingmingqiang(a)huawei.com<mailto:lingmingqiang@huawei.com>>; hafnium <hafnium(a)lists.trustedfirmware.org<mailto:hafnium@lists.trustedfirmware.org>>; Jens Wiklander <jens.wiklander(a)linaro.org<mailto:jens.wiklander@linaro.org>> Subject: Re: ffa memory problems ask for help Hi, Olivier, Thank you for replying. For the question 1, I don’t have a better idea. Currently, I temporarily mask the exception handling of this branch. When a problem occurs, I only print error information. The log is as follows: ERROR: mm_ptable_get_attrs_level table 0x82084032000 begin 0x7b98e000 end 0x7b990000 max_level 3 attrs 0x820840f8bf8 fail! For the question 2, I’ve solved the problem by modifying the parameter heap_pages from 60 to 180. After question 2 fixed, problem 1 seems to disappear. Regards, Wangyuan 发件人: Wangyuan (ange, IT) 发送时间: 2023年3月7日 19:30 收件人: 'Olivier Deprez' <Olivier.Deprez(a)arm.com<mailto:Olivier.Deprez@arm.com>> 抄送: zhouguangwei (C) <zhouguangwei5(a)huawei.com<mailto:zhouguangwei5@huawei.com>>; lingmingqiang <lingmingqiang(a)huawei.com<mailto:lingmingqiang@huawei.com>>; hafnium <hafnium(a)lists.trustedfirmware.org<mailto:hafnium@lists.trustedfirmware.org>>; Jens Wiklander <jens.wiklander(a)linaro.org<mailto:jens.wiklander@linaro.org>> 主题: 答复: ffa memory problems ask for help Hi, Olivier, Thank you for replying. For the question 1, I don’t have a better idea. Currently, I temporarily mask the exception handling of this branch. When a problem occurs, I only print error information. The log is as follows: ERROR: mm_ptable_get_attrs_level table 0x82084032000 begin 0x7b98e000 end 0x7b990000 max_level 3 attrs 0x820840f8bf8 fail! For the question 2, I’ve solved the problem by modifying the parameter heap_pages from 60 to 180. After question 2 fixed, problem 1 seems to disappear. Regards, Wangyuan 发件人: Olivier Deprez [mailto:Olivier.Deprez@arm.com] 发送时间: 2023年3月7日 18:10 收件人: Wangyuan (ange, IT) <wangyuan46(a)huawei.com<mailto:wangyuan46@huawei.com>> 抄送: zhouguangwei (C) <zhouguangwei5(a)huawei.com<mailto:zhouguangwei5@huawei.com>>; lingmingqiang <lingmingqiang(a)huawei.com<mailto:lingmingqiang@huawei.com>>; hafnium <hafnium(a)lists.trustedfirmware.org<mailto:hafnium@lists.trustedfirmware.org>>; Jens Wiklander <jens.wiklander(a)linaro.org<mailto:jens.wiklander@linaro.org>> 主题: Re: ffa memory problems ask for help Hi Wangyuan, Sorry for the delay. In case those issues are still relevant, problem 1: AFAIU the error message comes from additional code added on top of upstream hafnium. I cannot see a question related to problem 1, can you please elaborate about what you think is an issue? problem 2: This is probably caused by lacking "heap space", and the mm lib cannot allocate additional page tables. Did you attempt adjusting (increasing) this property for your project target: https://git.trustedfirmware.org/hafnium/project/reference.git/tree/BUILD.gn… Regards, Olivier. ________________________________ From: Wangyuan (ange, IT) <wangyuan46(a)huawei.com<mailto:wangyuan46@huawei.com>> Sent: 14 February 2023 04:32 To: hafnium <hafnium(a)lists.trustedfirmware.org<mailto:hafnium@lists.trustedfirmware.org>>; Olivier Deprez <Olivier.Deprez(a)arm.com<mailto:Olivier.Deprez@arm.com>>; Jens Wiklander <jens.wiklander(a)linaro.org<mailto:jens.wiklander@linaro.org>> Cc: zhouguangwei (C) <zhouguangwei5(a)huawei.com<mailto:zhouguangwei5@huawei.com>>; lingmingqiang <lingmingqiang(a)huawei.com<mailto:lingmingqiang@huawei.com>> Subject: ffa memory problems ask for help Hi, expert When I built test environment with hafnium v2.7 and optee 3.20.0, then execute xtest crypto cases repeatedly, several problems happened. Could you please give us some help? debug log is as follows: problem 1: regression_40VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x50, args->arg2 0x50, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 07_ecc Test TEE Internal API Generate ECC key VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000000, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x84000065, vm->id 0x8001, args->arg1 0x0, args->arg2 0x0, args->arg3 0x0, args->arg4 0x0 D/TC:??? 00 tee_ta_init_pseudo_ta_session:296 Lookup pseudo TA cb3e5ba0-adf1-11e0-998b-0002a5d5c51b D/TC:000 00 ldelf_load_ldelf:96 ldelf load address 0x40002000 D/LD: ldelf:134 Loading TS cb3e5ba0-adf1-11e0-998b-0002a5d5c51b F/TC:??? 00 trace_syscall:190 syscall #3 (syscall_get_property) F/TC:??? 00 trace_syscall:190 syscall #5 (syscall_open_ta_session) D/TC:??? 00 ldelf_syscall_open_bin:142 Lookup user TA ELF cb3e5ba0-adf1-11e0-998b-0002a5d5c51b (Secure Storage TA) VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x50, args->arg2 0x50, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0x1 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x84000065, vm->id 0x8001, args->arg1 0x0, args->arg2 0x0, args->arg3 0x0, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Cipher free ctx done! I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Cipher free ctx done! I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 D/TC:??? 00 ldelf_syscall_open_bin:146 res=0xffff0008 D/TC:??? 00 ldelf_syscall_open_bin:142 Lookup user TA ELF cb3e5ba0-adf1-11e0-998b-0002a5d5c51b (REE) VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x270, args->arg2 0x270, args->arg3 0x0, args->arg4 0x0 ERROR: arch_mm_pte_attrs error! INFO: begin 0x7f3cf000 end 0x7f3d0000 level 0 pte 0x82084059e78 l_end 0x7f400000 entry_size 0x1000! ERROR: mm_ptable_get_attrs_level second error! INFO: begin 0x7f3ce000 end 0x7f3d0000 level 1 pte 0x82084052fc8 l_end 0x80000000 entry_size 0x200000! ERROR: mm_ptable_get_attrs_level second error! INFO: begin 0x7f3ce000 end 0x7f3d0000 level 2 pte 0x82084051008 l_end 0x8000000000 entry_size 0x40000000! ERROR: mm_ptable_get_attrs_level second error! INFO: begin 0x7f3ce000 end 0x7f3d0000 level 3 pte 0x82084035000 l_end 0x1000000000000 entry_size 0x8000000000! ERROR: mm_ptable_get_attrs_level fail! Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0x2 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x84000065, vm->id 0x8001, args->arg1 0x0, args->arg2 0x0, args->arg3 0x0, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 D/TC:??? 00 ldelf_syscall_open_bin:146 res=0 Problem2: VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Cipher free ctx done! I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 D/TC:??? 00 ldelf_syscall_open_bin:146 res=0xffff0008 D/TC:??? 00 ldelf_syscall_open_bin:142 Lookup user TA ELF cb3e5ba0-adf1-11e0-998b-0002a5d5c51b (REE) VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x270, args->arg2 0x270, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0x2 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 ERROR: Failed to allocate memory for page table VERBOSE: Insufficient memory to update recipient page table. Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 E/TC:000 00 spmc_retrieve_req:1418 Failed to fetch cookie 0x2 error code -3 E/TC:000 00 thread_spmc_populate_mobj_from_rx:1486 Failed to retrieve cookie from rx buffer 0x2 E/TC:??? 00 mobj_ffa_get_by_cookie:423 Failed to get cookie 0x2 internal_offs 0 D/TC:??? 00 thread_rpc_alloc:1261 mobj_ffa_get_by_cookie(0x2, 0): failed D/TC:??? 00 ldelf_syscall_open_bin:146 res=0xffff000c Can anyone figure out what the problem is and give some debugging directions? Thanks! regards, wangyuan

2 years, 2 months

1
0
0 0

Re: ffa memory problems ask for help

by Wangyuan (ange, IT)

Hi, Olivier, Thank you for replying. For the question 1, I don’t have a better idea. Currently, I temporarily mask the exception handling of this branch. When a problem occurs, I only print error information. The log is as follows: ERROR: mm_ptable_get_attrs_level table 0x82084032000 begin 0x7b98e000 end 0x7b990000 max_level 3 attrs 0x820840f8bf8 fail! For the question 2, I’ve solved the problem by modifying the parameter heap_pages from 60 to 180. After question 2 fixed, problem 1 seems to disappear. Regards, Wangyuan 发件人: Wangyuan (ange, IT) 发送时间: 2023年3月7日 19:30 收件人: 'Olivier Deprez' <Olivier.Deprez(a)arm.com> 抄送: zhouguangwei (C) <zhouguangwei5(a)huawei.com>; lingmingqiang <lingmingqiang(a)huawei.com>; hafnium <hafnium(a)lists.trustedfirmware.org>; Jens Wiklander <jens.wiklander(a)linaro.org> 主题: 答复: ffa memory problems ask for help Hi, Olivier, Thank you for replying. For the question 1, I don’t have a better idea. Currently, I temporarily mask the exception handling of this branch. When a problem occurs, I only print error information. The log is as follows: ERROR: mm_ptable_get_attrs_level table 0x82084032000 begin 0x7b98e000 end 0x7b990000 max_level 3 attrs 0x820840f8bf8 fail! For the question 2, I’ve solved the problem by modifying the parameter heap_pages from 60 to 180. After question 2 fixed, problem 1 seems to disappear. Regards, Wangyuan 发件人: Olivier Deprez [mailto:Olivier.Deprez@arm.com] 发送时间: 2023年3月7日 18:10 收件人: Wangyuan (ange, IT) <wangyuan46(a)huawei.com<mailto:wangyuan46@huawei.com>> 抄送: zhouguangwei (C) <zhouguangwei5(a)huawei.com<mailto:zhouguangwei5@huawei.com>>; lingmingqiang <lingmingqiang(a)huawei.com<mailto:lingmingqiang@huawei.com>>; hafnium <hafnium(a)lists.trustedfirmware.org<mailto:hafnium@lists.trustedfirmware.org>>; Jens Wiklander <jens.wiklander(a)linaro.org<mailto:jens.wiklander@linaro.org>> 主题: Re: ffa memory problems ask for help Hi Wangyuan, Sorry for the delay. In case those issues are still relevant, problem 1: AFAIU the error message comes from additional code added on top of upstream hafnium. I cannot see a question related to problem 1, can you please elaborate about what you think is an issue? problem 2: This is probably caused by lacking "heap space", and the mm lib cannot allocate additional page tables. Did you attempt adjusting (increasing) this property for your project target: https://git.trustedfirmware.org/hafnium/project/reference.git/tree/BUILD.gn… Regards, Olivier. ________________________________ From: Wangyuan (ange, IT) <wangyuan46(a)huawei.com<mailto:wangyuan46@huawei.com>> Sent: 14 February 2023 04:32 To: hafnium <hafnium(a)lists.trustedfirmware.org<mailto:hafnium@lists.trustedfirmware.org>>; Olivier Deprez <Olivier.Deprez(a)arm.com<mailto:Olivier.Deprez@arm.com>>; Jens Wiklander <jens.wiklander(a)linaro.org<mailto:jens.wiklander@linaro.org>> Cc: zhouguangwei (C) <zhouguangwei5(a)huawei.com<mailto:zhouguangwei5@huawei.com>>; lingmingqiang <lingmingqiang(a)huawei.com<mailto:lingmingqiang@huawei.com>> Subject: ffa memory problems ask for help Hi, expert When I built test environment with hafnium v2.7 and optee 3.20.0, then execute xtest crypto cases repeatedly, several problems happened. Could you please give us some help? debug log is as follows: problem 1: regression_40VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x50, args->arg2 0x50, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 07_ecc Test TEE Internal API Generate ECC key VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000000, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x84000065, vm->id 0x8001, args->arg1 0x0, args->arg2 0x0, args->arg3 0x0, args->arg4 0x0 D/TC:??? 00 tee_ta_init_pseudo_ta_session:296 Lookup pseudo TA cb3e5ba0-adf1-11e0-998b-0002a5d5c51b D/TC:000 00 ldelf_load_ldelf:96 ldelf load address 0x40002000 D/LD: ldelf:134 Loading TS cb3e5ba0-adf1-11e0-998b-0002a5d5c51b F/TC:??? 00 trace_syscall:190 syscall #3 (syscall_get_property) F/TC:??? 00 trace_syscall:190 syscall #5 (syscall_open_ta_session) D/TC:??? 00 ldelf_syscall_open_bin:142 Lookup user TA ELF cb3e5ba0-adf1-11e0-998b-0002a5d5c51b (Secure Storage TA) VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x50, args->arg2 0x50, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0x1 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x84000065, vm->id 0x8001, args->arg1 0x0, args->arg2 0x0, args->arg3 0x0, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Cipher free ctx done! I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Cipher free ctx done! I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 D/TC:??? 00 ldelf_syscall_open_bin:146 res=0xffff0008 D/TC:??? 00 ldelf_syscall_open_bin:142 Lookup user TA ELF cb3e5ba0-adf1-11e0-998b-0002a5d5c51b (REE) VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x270, args->arg2 0x270, args->arg3 0x0, args->arg4 0x0 ERROR: arch_mm_pte_attrs error! INFO: begin 0x7f3cf000 end 0x7f3d0000 level 0 pte 0x82084059e78 l_end 0x7f400000 entry_size 0x1000! ERROR: mm_ptable_get_attrs_level second error! INFO: begin 0x7f3ce000 end 0x7f3d0000 level 1 pte 0x82084052fc8 l_end 0x80000000 entry_size 0x200000! ERROR: mm_ptable_get_attrs_level second error! INFO: begin 0x7f3ce000 end 0x7f3d0000 level 2 pte 0x82084051008 l_end 0x8000000000 entry_size 0x40000000! ERROR: mm_ptable_get_attrs_level second error! INFO: begin 0x7f3ce000 end 0x7f3d0000 level 3 pte 0x82084035000 l_end 0x1000000000000 entry_size 0x8000000000! ERROR: mm_ptable_get_attrs_level fail! Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0x2 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x84000065, vm->id 0x8001, args->arg1 0x0, args->arg2 0x0, args->arg3 0x0, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 D/TC:??? 00 ldelf_syscall_open_bin:146 res=0 Problem2: VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 I/TC: Cipher free ctx done! I/TC: Performing software calc! I/TC: Aead free ctx done! VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 D/TC:??? 00 ldelf_syscall_open_bin:146 res=0xffff0008 D/TC:??? 00 ldelf_syscall_open_bin:142 Lookup user TA ELF cb3e5ba0-adf1-11e0-998b-0002a5d5c51b (REE) VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 VERBOSE: hafnium func 0x84000070, vm->id 0x8001, args->arg1 0x80010000, args->arg2 0x0, args->arg3 0x0, args->arg4 0x1 VERBOSE: hafnium func 0x84000073, vm->id 0x0, args->arg1 0x270, args->arg2 0x270, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 VERBOSE: hafnium func 0x8400006f, vm->id 0x0, args->arg1 0x8001, args->arg2 0x0, args->arg3 0x80000001, args->arg4 0x0 E/TC:000 00 mobj_ffa_get_by_cookie:384 Populating mobj from rx buffer, cookie 0x2 VERBOSE: hafnium func 0x84000074, vm->id 0x8001, args->arg1 0x30, args->arg2 0x30, args->arg3 0x0, args->arg4 0x0 Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 ERROR: Failed to allocate memory for page table VERBOSE: Insufficient memory to update recipient page table. Current share states: SHARE 0x0 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x1 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 1 retrieved, sender's original mode: 0x7 SHARE 0x2 (from VM 0x0, attributes 0x2f, flags 0x8, tag 0, to 1 recipients [VM 0x8001: 0x6 (offset 48)]): fully sent with 1 fragments, 0 retrieved, sender's original mode: 0x7 E/TC:000 00 spmc_retrieve_req:1418 Failed to fetch cookie 0x2 error code -3 E/TC:000 00 thread_spmc_populate_mobj_from_rx:1486 Failed to retrieve cookie from rx buffer 0x2 E/TC:??? 00 mobj_ffa_get_by_cookie:423 Failed to get cookie 0x2 internal_offs 0 D/TC:??? 00 thread_rpc_alloc:1261 mobj_ffa_get_by_cookie(0x2, 0): failed D/TC:??? 00 ldelf_syscall_open_bin:146 res=0xffff000c Can anyone figure out what the problem is and give some debugging directions? Thanks! regards, wangyuan

2 years, 2 months

2
1
0 0

2025

2024

2023

2022

2021

2020

Hafnium