Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OP-TEE 4.1.0 fails to boot on zynqmp(ZCU102) #6631

Closed
callmefriend opened this issue Jan 23, 2024 · 9 comments
Closed

OP-TEE 4.1.0 fails to boot on zynqmp(ZCU102) #6631

callmefriend opened this issue Jan 23, 2024 · 9 comments
Labels

Comments

@callmefriend
Copy link

I am compiling OPTEE, my compilation command is as follows:

$ repo init -u https://github.com/OP-TEE/manifest.git -m zynqmp.xml 
$ repo sync
$ cd build
$ make toolchains
$ make PLATFORM=zynqmp-zcu102 image

After the compilation is over, get the following 2 files in Zynqmp/Directory:

BOOT.bin zynqmp-zcu102.ub

Then I replaced the corresponding files in 2021.1-zcu102-release.tar.xz with the above two files, then copied it to the SD card, and finally use the SD card to boot ZCU102.

Got the following error:

Xilinx Zynq MP First Stage Boot Loader 
Release 2021.1   Jun  6 2021  -  07:07:32
NOTICE:  BL31: Secure code at 0x60000000
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v2.8(release):xilinx-v2023.2
NOTICE:  BL31: Built : 10:44:01, Jan 23 2024
INFO:    ARM GICv2 driver initialized
INFO:    BL31: Initializing runtime services
INFO:    BL31: PM Service Init Complete: API v1.1
INFO:    BL31: Initializing BL32
D/TC:0   add_phys_mem:666 VCORE_UNPG_RX_PA type TEE_RAM_RX 0x60000000 size 0x00081000
D/TC:0   add_phys_mem:666 VCORE_UNPG_RW_PA type TEE_RAM_RW 0x60081000 size 0x0017f000
D/TC:0   add_phys_mem:666 ta_base type TA_RAM 0x60200000 size 0x0fe00000
D/TC:0   add_phys_mem:666 ROUNDDOWN(GIC_BASE + GICD_OFFSET, CORE_MMU_PGDIR_SIZE) type IO_SEC 0xf9000000 size 0x00200000
D/TC:0   add_phys_mem:666 ROUNDDOWN(GIC_BASE, CORE_MMU_PGDIR_SIZE) type IO_SEC 0xf9000000 size 0x00200000
D/TC:0   add_phys_mem:680 Physical mem map overlaps 0xf9000000
D/TC:0   add_phys_mem:666 ROUNDDOWN(CONSOLE_UART_BASE, CORE_MMU_PGDIR_SIZE) type IO_SEC 0xff000000 size 0x00200000
D/TC:0   add_phys_mem:666 TEE_SHMEM_START type NSEC_SHM 0x70000000 size 0x10000000
D/TC:0   add_va_space:706 type RES_VASPACE size 0x00a00000
D/TC:0   add_va_space:706 type SHM_VASPACE size 0x02000000
D/TC:0   dump_mmap_table:838 type TEE_RAM_RX   va 0x60000000..0x60080fff pa 0x60000000..0x60080fff size 0x00081000 (smallpg)
D/TC:0   dump_mmap_table:838 type TEE_RAM_RW   va 0x60081000..0x601fffff pa 0x60081000..0x601fffff size 0x0017f000 (smallpg)
D/TC:0   dump_mmap_table:838 type SHM_VASPACE  va 0x60200000..0x621fffff pa 0x00000000..0x01ffffff size 0x02000000 (pgdir)
D/TC:0   dump_mmap_table:838 type RES_VASPACE  va 0x62200000..0x62bfffff pa 0x00000000..0x009fffff size 0x00a00000 (pgdir)
D/TC:0   dump_mmap_table:838 type TA_RAM       va 0x62c00000..0x729fffff pa 0x60200000..0x6fffffff size 0x0fe00000 (pgdir)
D/TC:0   dump_mmap_table:838 type NSEC_SHM     va 0x72a00000..0x829fffff pa 0x70000000..0x7fffffff size 0x10000000 (pgdir)
D/TC:0   dump_mmap_table:838 type IO_SEC       va 0x82a00000..0x82bfffff pa 0xf9000000..0xf91fffff size 0x00200000 (pgdir)
D/TC:0   dump_mmap_table:838 type IO_SEC       va 0x82c00000..0x82dfffff pa 0xff000000..0xff1fffff size 0x00200000 (pgdir)
D/TC:0   core_mmu_xlat_table_alloc:527 xlat tables used 1 / 5
D/TC:0   core_mmu_xlat_table_alloc:527 xlat tables used 2 / 5
D/TC:0   core_mmu_xlat_table_alloc:527 xlat tables used 3 / 5
I/TC: 
I/TC: OP-TEE version: 4.1.0-dev (gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)) #1 Tue Jan 23 02:44:56 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
D/TC:0 0 call_preinitcalls:21 level 2 mobj_mapped_shm_init()
D/TC:0 0 mobj_mapped_shm_init:470 Shared memory address range: 60200000, 62200000
D/TC:0 0 call_initcalls:40 level 1 register_time_source()
D/TC:0 0 call_initcalls:40 level 1 teecore_init_pub_ram()
D/TC:0 0 call_initcalls:40 level 3 check_ta_store()
D/TC:0 0 check_ta_store:454 TA store: "early TA"
D/TC:0 0 check_ta_store:454 TA store: "Secure Storage TA"
D/TC:0 0 check_ta_store:454 TA store: "REE"
D/TC:0 0 call_initcalls:40 level 3 early_ta_init()
D/TC:0 0 early_ta_init:56 Early TA f04a0fe7-1f5d-4b9b-abf7-619b85b4ce8c size 48611 (compressed, uncompressed 109256)
D/TC:0 0 call_initcalls:40 level 3 verify_pseudo_tas_conformance()
D/TC:0 0 call_initcalls:40 level 3 tee_cryp_init()
E/TC:0 0 
E/TC:0 0 Core undef-abort at address 0x60003d24
E/TC:0 0  esr 0x02000000  ttbr0 0x600ab000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x400003c4
E/TC:0 0  x0  000000006009b478 x1  000000006009b4dc
E/TC:0 0  x2  0000000000000000 x3  0000008000000000
E/TC:0 0  x4  000000006009b4d4 x5  0000000000000040
E/TC:0 0  x6  0000000000000007 x7  000000000000cf10
E/TC:0 0  x8  0000000060003f60 x9  000000006009b488
E/TC:0 0  x10 0000000000000000 x11 0000000000000000
E/TC:0 0  x12 0000000000000000 x13 0000000000000020
E/TC:0 0  x14 0000000000000000 x15 0000000000000000
E/TC:0 0  x16 000000006003c7e4 x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 0000000000000007
E/TC:0 0  x20 000000006009b478 x21 000000006009b49c
E/TC:0 0  x22 0000000000000001 x23 00000000600b0190
E/TC:0 0  x24 0000000000000008 x25 000000006009b460
E/TC:0 0  x26 0000000050000004 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 00000000600b0000
E/TC:0 0  x30 000000006000a0e4 elr 0000000060003d24
E/TC:0 0  sp_el0 00000000600b0000
E/TC:0 0 TEE load address @ 0x60000000
E/TC:0 0 Call stack:
E/TC:0 0  0x60003d24
E/TC:0 0  0x60040a84
E/TC:0 0  0x6003c870
E/TC:0 0  0x60018790
E/TC:0 0  0x6002beb4
E/TC:0 0  0x6002bf80
E/TC:0 0  0x6001f95c
E/TC:0 0  0x60007e30
E/TC:0 0  0x60007fb8
E/TC:0 0 Panic '[abort] undefined abort (trap CPU)' at core/arch/arm/kernel/abort.c:500 <get_fault_type>
E/TC:0 0 TEE load address @ 0x60000000
E/TC:0 0 Call stack:
E/TC:0 0  0x6000818c
E/TC:0 0  0x6001dd60
E/TC:0 0  0x6000787c
E/TC:0 0  0x60004a90

It seems that it got crash when"crypto_rng_init() -> key_from_data() -> hash_final() -> crypto_hash_final() -> sha256_done() call chains is executed.This code is located in OPTEE OS.

what's wrong with it?

@jforissier
Copy link
Contributor

Hi friend,

It seems that it got crash when"crypto_rng_init() -> key_from_data() -> hash_final() -> crypto_hash_final() -> sha256_done() call chains is executed.This code is located in OPTEE OS.

You may use scripts/symbolize.py to decode the call stack, see https://optee.readthedocs.io/en/latest/debug/abort_dumps.html.

The undef-abort means "abort due to undefined instruction". Since the crash seems to relate to crypto stuff, could it be that you need CFG_CRYPTO_WITH_CE=n?

@callmefriend
Copy link
Author

Hi friend,

It seems that it got crash when"crypto_rng_init() -> key_from_data() -> hash_final() -> crypto_hash_final() -> sha256_done() call chains is executed.This code is located in OPTEE OS.

You may use scripts/symbolize.py to decode the call stack, see https://optee.readthedocs.io/en/latest/debug/abort_dumps.html.

The undef-abort means "abort due to undefined instruction". Since the crash seems to relate to crypto stuff, could it be that you need CFG_CRYPTO_WITH_CE=n?

thank you for your reply. After processing, the output is as follows:

I/TC: OP-TEE version: 4.1.0-dev (gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)) #1 Tue Jan 23 02:44:56 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
D/TC:0 0 call_preinitcalls:21 level 2 mobj_mapped_shm_init()
D/TC:0 0 mobj_mapped_shm_init:470 Shared memory address range: 60200000, 62200000
D/TC:0 0 call_initcalls:40 level 1 register_time_source()
D/TC:0 0 call_initcalls:40 level 1 teecore_init_pub_ram()
D/TC:0 0 call_initcalls:40 level 3 check_ta_store()
D/TC:0 0 check_ta_store:454 TA store: "early TA"
D/TC:0 0 check_ta_store:454 TA store: "Secure Storage TA"
D/TC:0 0 check_ta_store:454 TA store: "REE"
D/TC:0 0 call_initcalls:40 level 3 early_ta_init()
D/TC:0 0 early_ta_init:56 Early TA f04a0fe7-1f5d-4b9b-abf7-619b85b4ce8c size 48611 (compressed, uncompressed 109256)
D/TC:0 0 call_initcalls:40 level 3 verify_pseudo_tas_conformance()
D/TC:0 0 call_initcalls:40 level 3 tee_cryp_init()
E/TC:0 0 
E/TC:0 0 Core undef-abort at address 0x60003d24
E/TC:0 0  esr 0x02000000  ttbr0 0x600ab000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x400003c4
E/TC:0 0  x0  000000006009b478 x1  000000006009b4dc
E/TC:0 0  x2  0000000000000000 x3  0000008000000000
E/TC:0 0  x4  000000006009b4d4 x5  0000000000000040
E/TC:0 0  x6  0000000000000007 x7  000000000000cf10
E/TC:0 0  x8  0000000060003f60 x9  000000006009b488
E/TC:0 0  x10 0000000000000000 x11 0000000000000000
E/TC:0 0  x12 0000000000000000 x13 0000000000000020
E/TC:0 0  x14 0000000000000000 x15 0000000000000000
E/TC:0 0  x16 000000006003c7e4 x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 0000000000000007
E/TC:0 0  x20 000000006009b478 x21 000000006009b49c
E/TC:0 0  x22 0000000000000001 x23 00000000600b0190
E/TC:0 0  x24 0000000000000008 x25 000000006009b460
E/TC:0 0  x26 0000000050000004 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 00000000600b0000
E/TC:0 0  x30 000000006000a0e4 elr 0000000060003d24
E/TC:0 0  sp_el0 00000000600b0000
E/TC:0 0 TEE load address @ 0x60000000
E/TC:0 0 Core undef-abort at address 0x60003d24 .debug_info+15652
E/TC:0 0 Call stack:
E/TC:0 0  0x60003d24 sha256_ce_transform at zcu102/optee_os/core/arch/arm/crypto/sha256_armv8a_ce_a64.S:78
E/TC:0 0  0x60040a84 sha256_compress_nblocks at zcu102/optee_os/core/lib/libtomcrypt/sha256_accel.c:75
E/TC:0 0  0x6003c870 ltc_hash_final at zcu102/optee_os/core/lib/libtomcrypt/hash.c:76
E/TC:0 0  0x60018790 hash_final at zcu102/optee_os/core/crypto/rng_fortuna.c:93
E/TC:0 0  0x6002beb4 plat_rng_init at zcu102/optee_os/core/tee/tee_cryp_utl.c:197
E/TC:0 0  0x6002bf80 tee_cryp_init at zcu102/optee_os/core/tee/tee_cryp_utl.c:210
E/TC:0 0  0x6001f95c call_initcalls at zcu102/optee_os/core/kernel/initcall.c:41
E/TC:0 0  0x60007e30 init_tee_runtime at zcu102/optee_os/core/arch/arm/kernel/boot.c:1106
E/TC:0 0  0x60007fb8 boot_init_primary_late at zcu102/optee_os/core/arch/arm/kernel/boot.c:1227
E/TC:0 0 Panic '[abort] undefined abort (trap CPU)' at core/arch/arm/kernel/abort.c:500 <get_fault_type>
E/TC:0 0 TEE load address @ 0x60000000
E/TC:0 0 Call stack:
E/TC:0 0  0x6000818c print_kernel_stack at zcu102/optee_os/core/arch/arm/kernel/unwind_arm64.c:89
E/TC:0 0  0x6001dd60 __do_panic at zcu102/optee_os/core/kernel/panic.c:73
E/TC:0 0  0x6000787c abort_handler at zcu102/optee_os/core/arch/arm/kernel/abort.c:584
E/TC:0 0  0x60004a90 el1_sync_abort at zcu102/optee_os/core/arch/arm/kernel/thread_a64.S:964

I will try this configuration.
I modify CFG_CRYPTO_WITH_CE configuration to "n" in the optee_os/core/arch/arm/plat-zynqmp/conf.mk. Is it?

@jforissier
Copy link
Contributor

jforissier commented Jan 23, 2024

I modify CFG_CRYPTO_WITH_CE configuration to "n" in the optee_os/core/arch/arm/plat-zynqmp/conf.mk. Is it?

Yes it should be it. You may also run make PLATFORM=zynqmp-zcu102 CFG_CRYPTO_WITH_CE=n image just to be sure.

@callmefriend
Copy link
Author

I modify CFG_CRYPTO_WITH_CE configuration to "n" in the optee_os/core/arch/arm/plat-zynqmp/conf.mk. Is it?

Yes it should be it. You may also run make PLATFORM=zynqmp-zcu102 CFG_CRYPTO_WITH_CE=n image just to be sure.

Thank you very much jforissier!It works.

@jforissier
Copy link
Contributor

I modify CFG_CRYPTO_WITH_CE configuration to "n" in the optee_os/core/arch/arm/plat-zynqmp/conf.mk. Is it?

Yes it should be it. You may also run make PLATFORM=zynqmp-zcu102 CFG_CRYPTO_WITH_CE=n image just to be sure.

Thank you very much jforissier!It works.

Good! Then you must have a variant of the ZCU102 board that does not support Cryptographic Extensions.

@igoropaniuk
Copy link
Contributor

Sorry for my two cents: I think runtime detection might be better option to handle such cases (this info can be obtained from CPUID_EXT_ISAR5 on ARMv8, like it's currently done for flags detection for /proc/cpuinfo in kernel).

I'll experiment with that during the weekend :)

@igoropaniuk
Copy link
Contributor

@jforissier hm, I've just checked, so either sw implementation or implementation that uses crypto extensions are compiled it, not both (I guess because of size constraints); so switching in runtime is not an option, as I thought before.

Maybe just a check of CPU capabilities, and if CE are not listed in CPUID_EXT_ISAR5, but CFG_CRYPTO_WITH_CE=y - report an error during init.

@jforissier
Copy link
Contributor

@jforissier hm, I've just checked, so either sw implementation or implementation that uses crypto extensions are compiled it, not both (I guess because of size constraints); so switching in runtime is not an option, as I thought before.

Correct, but we could also have a CFG option to include both implementations and select the best at runtime. Perhaps easier said than done.

Maybe just a check of CPU capabilities, and if CE are not listed in CPUID_EXT_ISAR5, but CFG_CRYPTO_WITH_CE=y - report an error during init.

That would at least be a bit more user-friendly, yes :)

igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check for Crypto Extensions if CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check for Crypto Extensions if CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 27, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 28, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 29, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 29, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Jan 29, 2024
Add runtime check during boot for Crypto Extensions if
CFG_CRYPTO_WITH_CE=y.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 17, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.

Link: OP-TEE#6631
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 19, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 21, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 21, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 21, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Reviewed-by: Jerome Forissier <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 21, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Reviewed-by: Jerome Forissier <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 22, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Reviewed-by: Jerome Forissier <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
Copy link

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Feb 24, 2024
igoropaniuk added a commit to igoropaniuk/optee_os that referenced this issue Feb 27, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: OP-TEE#6631
Acked-by: Etienne Carriere <[email protected]>
Reviewed-by: Jerome Forissier <[email protected]>
Acked-by: Jens Wiklander <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
jforissier pushed a commit that referenced this issue Feb 27, 2024
Add runtime check during boot for supported ARMv8 Crypto Extensions.
Core will panic if configuration enables an ARMv8 CE feature
that the hardware does not support.

Link: #6631
Acked-by: Etienne Carriere <[email protected]>
Reviewed-by: Jerome Forissier <[email protected]>
Acked-by: Jens Wiklander <[email protected]>
Signed-off-by: Igor Opaniuk <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants