linux-kernel - optee: os: toolchains would include linux target macros likes __linux_

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <bfba8d2c-646d-4d62-9f71-8e388e70f782@soulik.info>
Date:   Mon, 4 Dec 2023 21:39:14 +0800
From:   Randy Li <ayaka@...lik.info>
To:     op-tee@...ts.trustedfirmware.org
Cc:     linux-kernel@...r.kernel.org, sumit.garg@...aro.org,
        jens.wiklander@...aro.org
Subject: optee: os: toolchains would include linux target macros likes
 __linux__

Hello

I wonder why Optee OS would use a linux target toolchains but not a bare 
metal target(none os)?

gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-gcc 
-dM -E - < /dev/null|grep linux
#define __linux 1
#define __gnu_linux__ 1
#define linux 1
#define __linux__ 1

That makes hard to share a header files between Linux kernel and Optee.  
We like to pass some structure in SHM, but optee don't have all those 
Linux types likes <linux/types.h>.

If optee didn't choose the toolchains for the Linux, we could easily 
decide which part would use for Client Agent(Linux kernel) side or TEE 
OS side.

Why we don't use bare metal toolchains ?

Thank you

Randy Li