From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Jay Chang <jay.chang@sifive.com>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
Chao Liu <chao.liu.zevorn@gmail.com>,
Frank Chang <frank.chang@sifive.com>
Subject: Re: [PATCH v4 1/2] target/riscv: Align pmp size to pmp-granularity
Date: Mon, 18 May 2026 09:13:40 +0200 [thread overview]
Message-ID: <91c8e98a-d900-4ece-9fce-0d193aa763f9@linaro.org> (raw)
In-Reply-To: <20260518070725.9816-2-jay.chang@sifive.com>
Hi,
On 18/5/26 09:07, Jay Chang wrote:
> When configuring pmpcfg (TOR, NA4, or NAPOT) and pmpaddr, if the
> value is smaller than the PMP granularity, it needs to be aligned
> to the PMP granularity.
>
> Signed-off-by: Jay Chang <jay.chang@sifive.com>
> Reviewed-by: Frank Chang <frank.chang@sifive.com>
> Reviewed-by: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
> ---
> target/riscv/pmp.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
> @@ -263,6 +264,11 @@ void pmp_update_rule_addr(CPURISCVState *env, uint32_t pmp_index)
> break;
>
> case PMP_AMATCH_NAPOT:
> + /* Bits [g-2:0] need to be all one to align pmp granularity */
> + if (g >= 2) {
> + this_addr |= ((1ULL << (g - 1ULL)) - 1ULL);
deposit64() could be easier to read here.
> + }
> +
> pmp_decode_napot(this_addr, &sa, &ea);
> break;
>
next prev parent reply other threads:[~2026-05-18 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 7:07 [PATCH v4 0/2] target/riscv: Fix PMP address alignment Jay Chang
2026-05-18 7:07 ` [PATCH v4 1/2] target/riscv: Align pmp size to pmp-granularity Jay Chang
2026-05-18 7:13 ` Philippe Mathieu-Daudé [this message]
2026-05-18 7:07 ` [PATCH v4 2/2] target/riscv: Use macros for PMP address alignment Jay Chang
2026-05-18 7:19 ` Philippe Mathieu-Daudé
2026-05-18 16:53 ` Daniel Henrique Barboza
2026-05-18 17:12 ` Anton Johansson via qemu development
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=91c8e98a-d900-4ece-9fce-0d193aa763f9@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=chao.liu.zevorn@gmail.com \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=frank.chang@sifive.com \
--cc=jay.chang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.