From: Richard Henderson <richard.henderson@linaro.org>
To: Deepak Gupta <debug@rivosinc.com>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org, palmer@dabbelt.com,
Alistair.Francis@wdc.com, bmeng.cn@gmail.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, jim.shu@sifive.com,
andy.chiu@sifive.com, kito.cheng@sifive.com
Subject: Re: [PATCH v5 11/15] target/riscv: mmu changes for zicfiss shadow stack protection
Date: Wed, 21 Aug 2024 08:33:31 +1000 [thread overview]
Message-ID: <9376bb6b-0d07-4f00-8004-6df1b0a8ef84@linaro.org> (raw)
In-Reply-To: <ZsTmibCvaZJpEAPO@debug.ba.rivosinc.com>
On 8/21/24 04:55, Deepak Gupta wrote:
> Something on the below lines? I've one question as well for you in comment.
>
> """"
> diff --git a/target/riscv/cpu.h b/target/riscv/cpu.h
> index fee31b8037..b4e04fe849 100644
> --- a/target/riscv/cpu.h
> +++ b/target/riscv/cpu.h
> @@ -46,8 +46,14 @@ typedef struct CPUArchState CPURISCVState;
> /*
> * RISC-V-specific extra insn start words:
> * 1: Original instruction opcode
> + * 2: more information about instruction
> */
> -#define TARGET_INSN_START_EXTRA_WORDS 1
> +#define TARGET_INSN_START_EXTRA_WORDS 2
> +
> +/*
> + * b0: Whether a shadow stack operation/instruction or not.
> + */
> +#define RISCV_INSN_START_WORD2_SS_OP 1
Ah, here: not shadow-stack specific. Set for any insn which should always generate
STORE_AMO, including the actual AMO instructions. It's a current emulation error, IIRC.
> @@ -226,6 +232,7 @@ struct CPUArchState {
> bool elp;
> /* shadow stack register for zicfiss extension */
> target_ulong ssp;
> + bool ss_op;
For generality, maybe just store the whole word as excp_uw2?
> if (!async) {
> + /* shadow stack op, promote load page fault to store page fault */
> + if (env->ss_op && cause == RISCV_EXCP_LOAD_PAGE_FAULT) {
> + cause = RISCV_EXCP_STORE_PAGE_FAULT;
> + }
> /* set tval to badaddr for traps with address information */
> switch (cause) {
> case RISCV_EXCP_SEMIHOST:
case RISCV_EXCP_LOAD_GUEST_ACCESS_FAULT:
if (env->excp_uw2 & RISCV_UW2_ALWAYS_STORE_AMO) {
cause = RISCV_EXCP_STORE_GUEST_AMO_ACCESS_FAULT;
}
goto load_store_fault;
case RISCV_EXCP_LOAD_ACCESS_FAULT:
...
case RISCV_EXCP_LOAD_PAGE_FAULT:
...
case RISCV_EXCP_STORE_PAGE_FAULT:
load_store_fault:
> @@ -1301,6 +1301,14 @@ static void riscv_tr_translate_insn(DisasContextBase *dcbase,
> CPUState *cpu)
> ctx->base.is_jmp = DISAS_NORETURN;
> }
>
> + /* shadow stack index means shadow stack instruction is translated */
> + if (ctx->mem_idx & MMU_IDX_SS_WRITE) {
> + /* Is this needed to set true? */
> + ctx->insn_start_updated = true;
> + tcg_set_insn_start_param(ctx->base.insn_start, 2,
> + RISCV_INSN_START_WORD2_SS_OP);
> + }
No, SS_WRITE is never part of mem_idx, and setting insn_start_updated here would break things.
You'll want to change decode_save_opcode() to take the second parameter (or introduce a
new helper for the second parameter, leaving decode_save_opcode alone). But you do have
to handle the update on a per-insn basis.
r~
next prev parent reply other threads:[~2024-08-20 22:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 0:01 [PATCH v5 00/15] riscv support for control flow integrity extensions Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 01/15] target/riscv: Add zicfilp extension Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 02/15] target/riscv: Introduce elp state and enabling controls for zicfilp Deepak Gupta
2024-08-20 5:17 ` Richard Henderson
2024-08-20 0:01 ` [PATCH v5 03/15] target/riscv: save and restore elp state on priv transitions Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 04/15] target/riscv: additional code information for sw check Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 05/15] target/riscv: tracking indirect branches (fcfi) for zicfilp Deepak Gupta
2024-08-20 5:24 ` Richard Henderson
2024-08-20 0:01 ` [PATCH v5 06/15] target/riscv: zicfilp `lpad` impl and branch tracking Deepak Gupta
2024-08-20 5:29 ` Richard Henderson
2024-08-20 0:01 ` [PATCH v5 07/15] disas/riscv: enable `lpad` disassembly Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 08/15] target/riscv: Add zicfiss extension Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 09/15] target/riscv: introduce ssp and enabling controls for zicfiss Deepak Gupta
2024-08-20 5:34 ` Richard Henderson
2024-08-20 0:01 ` [PATCH v5 10/15] target/riscv: tb flag for shadow stack instructions Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 11/15] target/riscv: mmu changes for zicfiss shadow stack protection Deepak Gupta
2024-08-20 7:35 ` Deepak Gupta
2024-08-20 9:20 ` Richard Henderson
2024-08-20 18:55 ` Deepak Gupta
2024-08-20 19:45 ` Deepak Gupta
2024-08-20 22:33 ` Richard Henderson [this message]
2024-08-20 0:01 ` [PATCH v5 12/15] target/riscv: implement zicfiss instructions Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 13/15] target/riscv: compressed encodings for sspush and sspopchk Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 14/15] disas/riscv: enable disassembly for zicfiss instructions Deepak Gupta
2024-08-20 0:01 ` [PATCH v5 15/15] disas/riscv: enable disassembly for compressed sspush/sspopchk Deepak Gupta
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-all 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=9376bb6b-0d07-4f00-8004-6df1b0a8ef84@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=andy.chiu@sifive.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=debug@rivosinc.com \
--cc=jim.shu@sifive.com \
--cc=kito.cheng@sifive.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
/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;
as well as URLs for NNTP newsgroup(s).