From: Alistair Francis <alistair23@gmail.com>
To: Alvin Chang <alvinga@andestech.com>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
alistair.francis@wdc.com, bin.meng@windriver.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com
Subject: Re: [PATCH v2 1/2] target/riscv: Preliminary textra trigger CSR writting support
Date: Fri, 19 Jul 2024 19:40:28 +1000 [thread overview]
Message-ID: <CAKmqyKPPt2o8emeWKYQjYdpw4V652eLfpsaay52ZyMLLgzS=6g@mail.gmail.com> (raw)
In-Reply-To: <20240710100010.814934-2-alvinga@andestech.com>
On Wed, Jul 10, 2024 at 8:01 PM Alvin Chang via <qemu-devel@nongnu.org> wrote:
>
> This commit allows program to write textra trigger CSR for type 2, 3, 6
> triggers. In this preliminary patch, the textra.MHVALUE and the
> textra.MHSELECT fields are allowed to be configured. Other fields, such
> as textra.SBYTEMASK, textra.SVALUE, and textra.SSELECT, are hardwired to
> zero for now.
>
> For textra.MHSELECT field, the only legal values are 0 (ignore) and 4
> (mcontext). Writing 1~3 into textra.MHSELECT will be changed to 0, and
> writing 5~7 into textra.MHSELECT will be changed to 4. This behavior is
> aligned to RISC-V SPIKE simulator.
>
> Signed-off-by: Alvin Chang <alvinga@andestech.com>
> ---
> target/riscv/cpu_bits.h | 10 ++++++
> target/riscv/debug.c | 75 +++++++++++++++++++++++++++++++++++++----
> 2 files changed, 79 insertions(+), 6 deletions(-)
>
> diff --git a/target/riscv/cpu_bits.h b/target/riscv/cpu_bits.h
> index c257c5ed7d..0530b4f9f4 100644
> --- a/target/riscv/cpu_bits.h
> +++ b/target/riscv/cpu_bits.h
> @@ -906,6 +906,16 @@ typedef enum RISCVException {
> #define JVT_BASE (~0x3F)
>
> /* Debug Sdtrig CSR masks */
> +#define TEXTRA32_MHVALUE 0xFC000000
> +#define TEXTRA32_MHSELECT 0x03800000
> +#define TEXTRA32_SBYTEMASK 0x000C0000
> +#define TEXTRA32_SVALUE 0x0003FFFC
> +#define TEXTRA32_SSELECT 0x00000003
> +#define TEXTRA64_MHVALUE 0xFFF8000000000000ULL
> +#define TEXTRA64_MHSELECT 0x0007000000000000ULL
> +#define TEXTRA64_SBYTEMASK 0x000000F000000000ULL
> +#define TEXTRA64_SVALUE 0x00000003FFFFFFFCULL
> +#define TEXTRA64_SSELECT 0x0000000000000003ULL
> #define MCONTEXT32 0x0000003F
> #define MCONTEXT64 0x0000000000001FFFULL
> #define MCONTEXT32_HCONTEXT 0x0000007F
> diff --git a/target/riscv/debug.c b/target/riscv/debug.c
> index 0b5099ff9a..139b722a7e 100644
> --- a/target/riscv/debug.c
> +++ b/target/riscv/debug.c
> @@ -217,6 +217,72 @@ static inline void warn_always_zero_bit(target_ulong val, target_ulong mask,
> }
> }
>
> +static target_ulong textra_validate(CPURISCVState *env, target_ulong tdata3)
> +{
> + target_ulong mhvalue, mhselect;
> + target_ulong mhselect_new;
> + target_ulong textra;
> + const uint32_t mhselect_no_rvh[8] = { 0, 0, 0, 0, 4, 4, 4, 4 };
> +
> + switch (riscv_cpu_mxl(env)) {
> + case MXL_RV32:
> + mhvalue = get_field(tdata3, TEXTRA32_MHVALUE);
> + mhselect = get_field(tdata3, TEXTRA32_MHSELECT);
> + /* Validate unimplemented (always zero) bits */
> + warn_always_zero_bit(tdata3, (target_ulong)TEXTRA32_SBYTEMASK,
> + "sbytemask");
> + warn_always_zero_bit(tdata3, (target_ulong)TEXTRA32_SVALUE,
> + "svalue");
> + warn_always_zero_bit(tdata3, (target_ulong)TEXTRA32_SSELECT,
> + "sselect");
> + break;
> + case MXL_RV64:
> + case MXL_RV128:
> + mhvalue = get_field(tdata3, TEXTRA64_MHVALUE);
> + mhselect = get_field(tdata3, TEXTRA64_MHSELECT);
> + /* Validate unimplemented (always zero) bits */
> + warn_always_zero_bit(tdata3, (target_ulong)TEXTRA64_SBYTEMASK,
> + "sbytemask");
> + warn_always_zero_bit(tdata3, (target_ulong)TEXTRA64_SVALUE,
> + "svalue");
> + warn_always_zero_bit(tdata3, (target_ulong)TEXTRA64_SSELECT,
> + "sselect");
> + break;
> + default:
> + g_assert_not_reached();
> + }
> +
> + /* Validate mhselect. */
> + mhselect_new = mhselect_no_rvh[mhselect];
> + if (mhselect != mhselect_new) {
> + qemu_log_mask(LOG_UNIMP, "mhselect only supports 0 or 4 for now\n");
> + }
> +
> + /* Write legal values into textra */
> + textra = 0;
> + switch (riscv_cpu_mxl(env)) {
> + case MXL_RV32:
> + textra = set_field(textra, TEXTRA32_MHVALUE, mhvalue);
> + textra = set_field(textra, TEXTRA32_MHSELECT, mhselect_new);
> + break;
> + case MXL_RV64:
> + case MXL_RV128:
> + textra = set_field(textra, TEXTRA64_MHVALUE, mhvalue);
> + textra = set_field(textra, TEXTRA64_MHSELECT, mhselect_new);
> + break;
> + default:
> + g_assert_not_reached();
> + }
> +
> + if (textra != tdata3) {
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "different value 0x" TARGET_FMT_lx " write to tdata3\n",
> + textra);
> + }
You don't need this, you have already reported on all of the possible
differences
With the above removed
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
next prev parent reply other threads:[~2024-07-19 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:00 [PATCH v2 0/2] RISC-V: Add preliminary textra trigger CSR functions Alvin Chang via
2024-07-10 10:00 ` [PATCH v2 1/2] target/riscv: Preliminary textra trigger CSR writting support Alvin Chang via
2024-07-19 9:40 ` Alistair Francis [this message]
2024-07-10 10:00 ` [PATCH v2 2/2] target/riscv: Add textra matching condition for the triggers Alvin Chang via
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='CAKmqyKPPt2o8emeWKYQjYdpw4V652eLfpsaay52ZyMLLgzS=6g@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=alvinga@andestech.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.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).