| Message ID | 20240214172127.1022199-1-arnaud.pouliquen@foss.st.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Introduction of a remoteproc tee to load signed firmware | expand |
On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: > Updates from the previous version [1]: > > This version proposes another approach based on an alternate load and boot > of the coprocessor. Therefore, the constraint introduced by tee_remoteproc > is that the firmware has to be authenticated and loaded before the resource > table can be obtained. > > The existing boot sequence is: > > 1) Get the resource table and store it in a cache, > calling rproc->ops->parse_fw(). > 2) Parse the resource table and handle resources, > calling rproc_handle_resources. > 3) Load the firmware, calling rproc->ops->load(). > 4) Start the firmware, calling rproc->ops->start(). > > => Steps 1 and 2 are executed in rproc_fw_boot(), while steps 3 and 4 are > executed in rproc_start(). > => the use of rproc->ops->load() ops is mandatory > > The boot sequence needed for TEE boot is: > > 1) Load the firmware. > 2) Get the loaded resource, no cache. > 3) Parse the resource table and handle resources. > 4) Start the firmware. Hi, What problem are we really addressing here by reordering load, parse of FW resources? Basically, what are the limitations of the current design you are referring to? I understood that TEE is designed that way. > > Then the crash recovery also has to be managed.For recovery, the cache is > used to temporarily save the resource table and then reapply it on > restart: > 1) Stop the remote processor, calling rproc->ops->stop(). > 2) Load the firmware, calling rproc->ops->load(). > 3) Copy cached resource table. > 4) Start the remote processor, calling rproc->ops->start(). > > => This sequence is also needed when TEE manages the boot of the remote > processor. > => The rproc->ops->load() is also used in recovery sequence. > > Based on the sequences described above, the proposal is to: > > - Rework tee_rproc API to better match the rproc_ops structure. > This allows to simply map the function to implement the load ops, which > is not optional. The tee_rproc_load_fw() is updated in consequence. > - Remove the call of rproc_load_segments from rproc_start() to dissociate > the load and the start. This is necessary to implement the boot sequence > requested for the TEE remote proc support. > - Introduce an rproc_alt_fw_boot() function that is an alternative boot > sequence, which implements the sequence requested for the TEE remoteproc > support. > > > [1] https://lore.kernel.org/lkml/20240118100433.3984196-1-arnaud.pouliquen@foss.st.com/T/ > > > Description of the feature: > > This series proposes the implementation of a remoteproc tee driver to > communicate with a TEE trusted application responsible for authenticating and > loading the remoteproc firmware image in an Arm secure context. > > 1) Principle: > > The remoteproc tee driver provides services to communicate with the OP-TEE > trusted application running on the Trusted Execution Context (TEE). s/Context/Environment? > The trusted application in TEE manages the remote processor lifecycle: > > - authenticating and loading firmware images, > - isolating and securing the remote processor memories, > - supporting multi-firmware (e.g., TF-M + Zephyr on a Cortex-M33), > - managing the start and stop of the firmware by the TEE. > Regards, Naman Jain
Hello Naman, On 2/22/24 06:43, Naman Jain wrote: > On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: >> Updates from the previous version [1]: >> >> This version proposes another approach based on an alternate load and boot >> of the coprocessor. Therefore, the constraint introduced by tee_remoteproc >> is that the firmware has to be authenticated and loaded before the resource >> table can be obtained. >> >> The existing boot sequence is: > >> 1) Get the resource table and store it in a cache, >> calling rproc->ops->parse_fw(). >> 2) Parse the resource table and handle resources, >> calling rproc_handle_resources. >> 3) Load the firmware, calling rproc->ops->load(). >> 4) Start the firmware, calling rproc->ops->start(). >> => Steps 1 and 2 are executed in rproc_fw_boot(), while steps 3 and 4 are >> executed in rproc_start(). >> => the use of rproc->ops->load() ops is mandatory >> >> The boot sequence needed for TEE boot is: >> >> 1) Load the firmware. >> 2) Get the loaded resource, no cache. >> 3) Parse the resource table and handle resources. >> 4) Start the firmware. > > Hi, > What problem are we really addressing here by reordering load, parse of > FW resources? The feature introduced in TEE is the signature of the firmware images. That means that before getting the resource table, we need to first authenticate the firmware images. Authenticating a firmware image means that we have to copy the firmware into protected memory that cannot be corrupted by the non-secure and then verify the signature. The strategy implemented in OP-TEE is to load the firmware into destination memory and then authenticate it. This strategy avoids having a temporary copy of the whole images in a secure memory. This strategy imposes loading the firmware images before retrieving the resource table. > Basically, what are the limitations of the current design you are referring to? > I understood that TEE is designed that way. The limitation of the current design is that we obtain the resource table before loading the firmware. Following the current design would impose constraints in TEE that are not straightforward. Step 1 (getting the resource table and storing it in a cache) would require having a copy of the resource table in TEE after authenticating the images. However, authenticating the firmware, as explained before, depends on the strategy implemented. In TEE implementation, we load the firmware to authenticate it in the destination memory. Regards, Arnaud > >> >> Then the crash recovery also has to be managed.For recovery, the cache is >> used to temporarily save the resource table and then reapply it on >> restart: >> 1) Stop the remote processor, calling rproc->ops->stop(). >> 2) Load the firmware, calling rproc->ops->load(). >> 3) Copy cached resource table. >> 4) Start the remote processor, calling rproc->ops->start(). >> >> => This sequence is also needed when TEE manages the boot of the remote >> processor. >> => The rproc->ops->load() is also used in recovery sequence. >> >> Based on the sequences described above, the proposal is to: >> >> - Rework tee_rproc API to better match the rproc_ops structure. >> This allows to simply map the function to implement the load ops, which >> is not optional. The tee_rproc_load_fw() is updated in consequence. >> - Remove the call of rproc_load_segments from rproc_start() to dissociate >> the load and the start. This is necessary to implement the boot sequence >> requested for the TEE remote proc support. >> - Introduce an rproc_alt_fw_boot() function that is an alternative boot >> sequence, which implements the sequence requested for the TEE remoteproc >> support. >> >> >> [1] >> https://lore.kernel.org/lkml/20240118100433.3984196-1-arnaud.pouliquen@foss.st.com/T/ >> >> >> Description of the feature: >> >> This series proposes the implementation of a remoteproc tee driver to >> communicate with a TEE trusted application responsible for authenticating and >> loading the remoteproc firmware image in an Arm secure context. >> >> 1) Principle: >> >> The remoteproc tee driver provides services to communicate with the OP-TEE >> trusted application running on the Trusted Execution Context (TEE). > > s/Context/Environment? > >> The trusted application in TEE manages the remote processor lifecycle: >> >> - authenticating and loading firmware images, >> - isolating and securing the remote processor memories, >> - supporting multi-firmware (e.g., TF-M + Zephyr on a Cortex-M33), >> - managing the start and stop of the firmware by the TEE. >> > > Regards, > Naman Jain >
On 2/22/2024 2:17 PM, Arnaud POULIQUEN wrote: > Hello Naman, > > On 2/22/24 06:43, Naman Jain wrote: >> On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: >>> Updates from the previous version [1]: >>> >>> This version proposes another approach based on an alternate load and boot >>> of the coprocessor. Therefore, the constraint introduced by tee_remoteproc >>> is that the firmware has to be authenticated and loaded before the resource >>> table can be obtained. >>> >>> The existing boot sequence is: > >>> 1) Get the resource table and store it in a cache, >>> calling rproc->ops->parse_fw(). >>> 2) Parse the resource table and handle resources, >>> calling rproc_handle_resources. >>> 3) Load the firmware, calling rproc->ops->load(). >>> 4) Start the firmware, calling rproc->ops->start(). >>> => Steps 1 and 2 are executed in rproc_fw_boot(), while steps 3 and 4 are >>> executed in rproc_start(). >>> => the use of rproc->ops->load() ops is mandatory >>> >>> The boot sequence needed for TEE boot is: >>> >>> 1) Load the firmware. >>> 2) Get the loaded resource, no cache. >>> 3) Parse the resource table and handle resources. >>> 4) Start the firmware. >> >> Hi, >> What problem are we really addressing here by reordering load, parse of >> FW resources? > > The feature introduced in TEE is the signature of the firmware images. That > means that before getting the resource table, we need to first authenticate the > firmware images. > Authenticating a firmware image means that we have to copy the firmware into > protected memory that cannot be corrupted by the non-secure and then verify the > signature. > The strategy implemented in OP-TEE is to load the firmware into destination > memory and then authenticate it. > This strategy avoids having a temporary copy of the whole images in a secure memory. > This strategy imposes loading the firmware images before retrieving the resource > table. > >> Basically, what are the limitations of the current design you are referring to? >> I understood that TEE is designed that way. > > The limitation of the current design is that we obtain the resource table before > loading the firmware. Following the current design would impose constraints in > TEE that are not straightforward. Step 1 (getting the resource table and storing > it in a cache) would require having a copy of the resource table in TEE after > authenticating the images. However, authenticating the firmware, as explained > before, depends on the strategy implemented. In TEE implementation, we load the > firmware to authenticate it in the destination memory. > > Regards, > Arnaud Hello Arnaud, I think now I got your point. In TEE, you don't want to do anything(read resource table) with FW images, until its loaded and authenticated. Since current design was not allowing you to do it, you had to reorganize the code so that this can be achieved. Generally speaking, in current design, if authentication fails for some reason later, one can handle it, but it depends on the implementation of parse_fw op if the damage is already done. Please correct me if this is wrong assumption. Patch looks good to me. Regards, Naman Jain
On 2/22/24 10:55, Naman Jain wrote: > On 2/22/2024 2:17 PM, Arnaud POULIQUEN wrote: >> Hello Naman, >> >> On 2/22/24 06:43, Naman Jain wrote: >>> On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: >>>> Updates from the previous version [1]: >>>> >>>> This version proposes another approach based on an alternate load and boot >>>> of the coprocessor. Therefore, the constraint introduced by tee_remoteproc >>>> is that the firmware has to be authenticated and loaded before the resource >>>> table can be obtained. >>>> >>>> The existing boot sequence is: > >>>> 1) Get the resource table and store it in a cache, >>>> calling rproc->ops->parse_fw(). >>>> 2) Parse the resource table and handle resources, >>>> calling rproc_handle_resources. >>>> 3) Load the firmware, calling rproc->ops->load(). >>>> 4) Start the firmware, calling rproc->ops->start(). >>>> => Steps 1 and 2 are executed in rproc_fw_boot(), while steps 3 and 4 are >>>> executed in rproc_start(). >>>> => the use of rproc->ops->load() ops is mandatory >>>> >>>> The boot sequence needed for TEE boot is: >>>> >>>> 1) Load the firmware. >>>> 2) Get the loaded resource, no cache. >>>> 3) Parse the resource table and handle resources. >>>> 4) Start the firmware. >>> >>> Hi, >>> What problem are we really addressing here by reordering load, parse of >>> FW resources? >> >> The feature introduced in TEE is the signature of the firmware images. That >> means that before getting the resource table, we need to first authenticate the >> firmware images. >> Authenticating a firmware image means that we have to copy the firmware into >> protected memory that cannot be corrupted by the non-secure and then verify the >> signature. >> The strategy implemented in OP-TEE is to load the firmware into destination >> memory and then authenticate it. >> This strategy avoids having a temporary copy of the whole images in a secure >> memory. >> This strategy imposes loading the firmware images before retrieving the resource >> table. >> >>> Basically, what are the limitations of the current design you are referring to? >>> I understood that TEE is designed that way. >> >> The limitation of the current design is that we obtain the resource table before >> loading the firmware. Following the current design would impose constraints in >> TEE that are not straightforward. Step 1 (getting the resource table and storing >> it in a cache) would require having a copy of the resource table in TEE after >> authenticating the images. However, authenticating the firmware, as explained >> before, depends on the strategy implemented. In TEE implementation, we load the >> firmware to authenticate it in the destination memory. >> >> Regards, >> Arnaud > > > Hello Arnaud, > I think now I got your point. In TEE, you don't want to do anything(read > resource table) with FW images, until its loaded and authenticated. > Since current design was not allowing you to do it, you had to reorganize the > code so that this can be achieved. > > Generally speaking, in current design, if authentication fails for some > reason later, one can handle it, but it depends on the implementation of > parse_fw op if the damage is already done. > > Please correct me if this is wrong assumption. That's correct. Regards, Arnaud > Patch looks good to me. > > Regards, > Naman Jain
Updates from the previous version [1]: This version proposes another approach based on an alternate load and boot of the coprocessor. Therefore, the constraint introduced by tee_remoteproc is that the firmware has to be authenticated and loaded before the resource table can be obtained. The existing boot sequence is: 1) Get the resource table and store it in a cache, calling rproc->ops->parse_fw(). 2) Parse the resource table and handle resources, calling rproc_handle_resources. 3) Load the firmware, calling rproc->ops->load(). 4) Start the firmware, calling rproc->ops->start(). => Steps 1 and 2 are executed in rproc_fw_boot(), while steps 3 and 4 are executed in rproc_start(). => the use of rproc->ops->load() ops is mandatory The boot sequence needed for TEE boot is: 1) Load the firmware. 2) Get the loaded resource, no cache. 3) Parse the resource table and handle resources. 4) Start the firmware. Then the crash recovery also has to be managed.For recovery, the cache is used to temporarily save the resource table and then reapply it on restart: 1) Stop the remote processor, calling rproc->ops->stop(). 2) Load the firmware, calling rproc->ops->load(). 3) Copy cached resource table. 4) Start the remote processor, calling rproc->ops->start(). => This sequence is also needed when TEE manages the boot of the remote processor. => The rproc->ops->load() is also used in recovery sequence. Based on the sequences described above, the proposal is to: - Rework tee_rproc API to better match the rproc_ops structure. This allows to simply map the function to implement the load ops, which is not optional. The tee_rproc_load_fw() is updated in consequence. - Remove the call of rproc_load_segments from rproc_start() to dissociate the load and the start. This is necessary to implement the boot sequence requested for the TEE remote proc support. - Introduce an rproc_alt_fw_boot() function that is an alternative boot sequence, which implements the sequence requested for the TEE remoteproc support. [1] https://lore.kernel.org/lkml/20240118100433.3984196-1-arnaud.pouliquen@foss.st.com/T/ Description of the feature: This series proposes the implementation of a remoteproc tee driver to communicate with a TEE trusted application responsible for authenticating and loading the remoteproc firmware image in an Arm secure context. 1) Principle: The remoteproc tee driver provides services to communicate with the OP-TEE trusted application running on the Trusted Execution Context (TEE). The trusted application in TEE manages the remote processor lifecycle: - authenticating and loading firmware images, - isolating and securing the remote processor memories, - supporting multi-firmware (e.g., TF-M + Zephyr on a Cortex-M33), - managing the start and stop of the firmware by the TEE. 2) Format of the signed image: Refer to: https://github.com/OP-TEE/optee_os/blob/master/ta/remoteproc/src/remoteproc_core.c#L18-L57 3) OP-TEE trusted application API: Refer to: https://github.com/OP-TEE/optee_os/blob/master/ta/remoteproc/include/ta_remoteproc.h 4) OP-TEE signature script Refer to: https://github.com/OP-TEE/optee_os/blob/master/scripts/sign_rproc_fw.py Example of usage: sign_rproc_fw.py --in <fw1.elf> --in <fw2.elf> --out <signed_fw.sign> --key ${OP-TEE_PATH}/keys/default.pem 5) Impact on User space Application No sysfs impact.the user only needs to provide the signed firmware image instead of the ELF image. For more information about the implementation, a presentation is available here (note that the format of the signed image has evolved between the presentation and the integration in OP-TEE). https://resources.linaro.org/en/resource/6c5bGvZwUAjX56fvxthxds Arnaud Pouliquen (7): remoteproc: Add TEE support remoteproc: Extract the firmware load from the start remoteproc: core: Add check on cached_table pointer remoteproc: core: Implement the support of an alternative boot dt-bindings: remoteproc: Add compatibility for TEE support remoteproc: stm32: Create sub-functions to request shutdown and release remoteproc: stm32: Add support of an OP-TEE TA to load the firmware .../bindings/remoteproc/st,stm32-rproc.yaml | 51 ++- drivers/remoteproc/Kconfig | 9 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/remoteproc_core.c | 109 ++++- drivers/remoteproc/stm32_rproc.c | 169 ++++++-- drivers/remoteproc/tee_remoteproc.c | 397 ++++++++++++++++++ include/linux/remoteproc.h | 2 + include/linux/tee_remoteproc.h | 102 +++++ 8 files changed, 784 insertions(+), 56 deletions(-) create mode 100644 drivers/remoteproc/tee_remoteproc.c create mode 100644 include/linux/tee_remoteproc.h