Hi Bohdan,

You are right, the section is standing alone, out of .text, which is not good and shall be fixed.

The origin of this section is here:

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12144

In the comments, there was a concern against adding the section into linker script to prevent potential maintenance issues but probably it’s unavoidable if the section must be present at all.

Thank you for bringing it up. We will follow up with it. Please share your ideas on a possible fix if any.

Anton

From: Bohdan.Hunko@infineon.com <Bohdan.Hunko@infineon.com>
Sent: Monday, May 20, 2024 8:45 AM
To: Anton Komlev <Anton.Komlev@arm.com>; tf-m@lists.trustedfirmware.org
Cc: Roman.Mazurak@infineon.com
Subject: RE: psa_interface_thread_fn_call section

Hi Anton,

Looking into latest an521 build logs here: https://ci.trustedfirmware.org/job/tf-m-build-config/1506009/artifact/ci_build/spe/bin/tfm_s.map/*view*/

I can see that .psa_interface_thread_fn_call is placed as separate section before .tfm_secure_data_start section.

So it does not go into .text/.code section.

Not sure that this is the behavior we want.

Regards,

Bohdan Hunko

Cypress Semiconductor Ukraine

Engineer

CSUKR CSS ICW SW FW

Mobile: +38099 50 19 714
Bohdan.Hunko@infineon.com

From: Anton Komlev <Anton.Komlev@arm.com>
Sent: Friday, May 17, 2024 14:23
To: Hunko Bohdan (CSS ICW SW FW 3) <Bohdan.Hunko@infineon.com>; tf-m@lists.trustedfirmware.org
Cc: Mazurak Roman (CSS ICW SW FW 3) <Roman.Mazurak@infineon.com>
Subject: RE: psa_interface_thread_fn_call section

Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe.

Hi Bohdan,

Apologize for the delayed reply. I think there is no danger that functions marked .psa_interface_thread_fn_call section will appear anywhere outside of Code because linker places sections based on attributes so all code in this section will be combined with default .text and other RO executable elements and placed in the Code segment.

I believe those functions were explicitly gathered in a single section for grouping purposes, but the author can have a better answer.

Hope that helps. Please let me know if you have different thoughts.

Anton

From: Bohdan.Hunko--- via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Tuesday, May 14, 2024 2:36 PM
To: Bohdan.Hunko@infineon.com; tf-m@lists.trustedfirmware.org
Cc: Roman.Mazurak@infineon.com
Subject: [TF-M] Re: psa_interface_thread_fn_call section

Hi all,

Any updates on this?

Regards,

Bohdan Hunko

Cypress Semiconductor Ukraine

Engineer

CSUKR CSS ICW SW FW

Mobile: +38099 50 19 714
Bohdan.Hunko@infineon.com

From: Bohdan.Hunko--- via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Wednesday, April 10, 2024 18:52
To: tf-m@lists.trustedfirmware.org
Cc: Mazurak Roman (CSS ICW SW FW 3) <Roman.Mazurak@infineon.com>
Subject: [TF-M] psa_interface_thread_fn_call section

Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe.

Hi all,

Why does TFM assigns function to psa_interface_thread_fn_call section and then never places them anywhere specific?

This way functions assigned to this section are placed outside of the code region which may result in unpredictable behavior.

Regards,

Bohdan Hunko

Cypress Semiconductor Ukraine

Engineer

CSUKR CSS ICW SW FW

Mobile: +38099 50 19 714
Bohdan.Hunko@infineon.com