From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, lichao@loongson.cn
Cc: "Andrew (EFI) Fish" <afish@apple.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Bob Feng <bob.c.feng@intel.com>,
Yuwei Chen <yuwei.chen@intel.com>
Subject: Re: [edk2-devel] About EDK2 supports Self Modifying Code
Date: Tue, 15 Aug 2023 16:35:10 +0100 [thread overview]
Message-ID: <CAKbZUD1W7LeMMBHD1TDgQ-0uSr-DudcUB038ZeugiqyiDxA14g@mail.gmail.com> (raw)
In-Reply-To: <f60597f8-c4f0-0bad-804c-da845d2c579e@loongson.cn>
On Tue, Aug 15, 2023 at 9:20 AM Chao Li <lichao@loongson.cn> wrote:
>
> Hi Andrew,
>
> Yes, you are right, I also think that SMC is a bit flawed in terms of security, but can we use some security mechanism to protect the SMC, like encryption and decryption? Sorry, I'm not consider mature enough about SMC security.
There isn't any. Actual use cases in something like a kernel are
heavily vetted and read-protected as soon as possible.
>
> I can tell you real problem, there are some CSR instructions in LoongArch64 that can only accept immediate value, for example: `csrrd $a0, 0x1`, the 0x1 is the selection of CSR register number, it can't use the registers to select. This operation should be in the MdePkg base library.
>
> I know that .c or .h files in MdePkg shouldn't depend on a single compiler feature, so I can't use the GNU AT&T style inline ASM function(AT&T style inline supports input parameters being immedite value, use "i" option). In this case, I think using SMC can handle this, that is use register transfer the CSR registers selection, and dynamically modify CSR instructions during execution phase with reference to transfer register value, this way is depend on the .text section or target memory is executable and writable.
FYI, poking instructions willy-nilly is unsafe and unreliable (except
on x86 due to kludges, but then it's slow).
>
> The problem of immediate values can only be handled by preprocessing stage or using SMC, otherwise I can only write a lot of similar functions and use `switch case` to call them. This method will cause the program size to expand a lot.
>
> So, I think I have following choice:
>
> Choice 1:
>
> Use AT&T style inline function, and create a file named: CsrOperationGcc.c, and other future compiler feature-dependent files will be named: CsrOperationClang.c, CsrOperationXlang.c and so on.
If you're going to use inline assembly, just expose them directly? I
don't see the problem there, I don't expect loongarch to be picked up
by visual studio any time soon.
>
>
> Choice 2:
>
> Use SMC.
>
>
> Choice 3:
>
> Write a lot of similar CSR functions.
You /could/ use a GAS macro.
.macro csr_write csr
.global CsrWrite\csr
CsrWrite\csr:
csrw a0, \csr
ret
(this is riscv pseudo-asm but I know your arch is similar enough)
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107767): https://edk2.groups.io/g/devel/message/107767
Mute This Topic: https://groups.io/mt/100751724/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-08-15 15:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 3:06 [edk2-devel] About EDK2 supports Self Modifying Code Chao Li
2023-08-15 4:57 ` Andrew Fish via groups.io
2023-08-15 8:20 ` Chao Li
2023-08-15 8:28 ` Ard Biesheuvel
2023-08-15 8:54 ` Chao Li
2023-08-15 15:05 ` Andrew Fish via groups.io
2023-08-15 15:39 ` Pedro Falcato
2023-08-15 16:30 ` Andrew Fish via groups.io
2023-08-15 18:48 ` Ard Biesheuvel
2023-08-15 21:26 ` Andrew Fish via groups.io
2023-08-17 3:38 ` Chao Li
2023-08-15 15:35 ` Pedro Falcato [this message]
2023-08-17 2:30 ` Chao Li
2023-08-17 19:53 ` Michael D Kinney
2023-08-17 20:55 ` Andrew Fish via groups.io
2023-08-19 2:18 ` Chao Li
2023-08-19 4:29 ` Michael D Kinney
2023-08-25 4:02 ` Chao Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKbZUD1W7LeMMBHD1TDgQ-0uSr-DudcUB038ZeugiqyiDxA14g@mail.gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox