Thanks for spotting that Jamie! That fixed my issue. I was using “RelWithDebInfo” in v1.1 and changed to “Debug” for v1.7 since RelWithDebInfo was no longer an option. Call times are all improved in v1.7 over v1.1 as expected when using
“Release” build type.
V1.8 is a bit worse than V1.7 though.
Psa_connect() call time in cycles:
|
TF-M version |
Psa_connect() in cycles |
|
1.1 |
3406 |
|
1.7 |
2872 |
|
1.8 |
3130 |
Psa_version() call time in cycles:
|
TF-M version |
Psa_version() in cycles |
|
1.1 |
343 |
|
1.7 |
389 |
|
1.8 |
500 |
Psa_call() call time in cycles: 1 invec, 3 outvec
|
TF-M version |
Psa_call() in cycles |
|
1.1 |
4406 |
|
1.7 |
3404 |
|
1.8 |
3722 |
Regards,
Brian
From: Jamie Fox <Jamie.Fox@arm.com>
Sent: Tuesday, May 2, 2023 11:09 AM
To: Quach, Brian <brian@ti.com>; Ken Liu <Ken.Liu@arm.com>; tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [EXTERNAL] RE: psa_call performance
Hi Brian,
I think the old ConfigCoreIPC is broadly similar to medium profile with isolation level set to 1. But I noticed in your v1.1 build logs that it is being built with optimization at -O3, whereas in v1.7 you have -DCMAKE_BUILD_TYPE=Debug which
implies -O0. If you change the v1.7 build type to -DCMAKE_BUILD_TYPE=Release then that will get you an optimized -O3 build comparable to the v1.1 one.
Kind regards,
Jamie