qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mayuresh Chitale <mchitale@ventanamicro.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
	 Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v2] target/riscv: pmp: Ignore writes when RW=01
Date: Wed, 11 Oct 2023 21:04:04 +0530	[thread overview]
Message-ID: <CAN37VV7YBOn0OZ-ih4thwqNdbF9LAo9p9zJOBsWK6QsUXaDi=g@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKP5kWQRUHBhHsXOFKuiB+Ac6cJGTRq9sBXsGD9G+1SNZA@mail.gmail.com>

On Mon, Oct 9, 2023 at 6:56 AM Alistair Francis <alistair23@gmail.com> wrote:
>
> On Mon, Sep 25, 2023 at 9:11 PM Mayuresh Chitale
> <mchitale@ventanamicro.com> wrote:
> >
> > As per the Priv spec: "The R, W, and X fields form a collective WARL
> > field for which the combinations with R=0 and W=1 are reserved."
> > However currently such writes are not ignored as ought to be. The
> > combinations with RW=01 are allowed only when the Smepmp extension
> > is enabled and mseccfg.MML is set.
> >
> > Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
>
> Do you mind rebasing this on
> https://github.com/alistair23/qemu/tree/riscv-to-apply.next
Ok, will do that.
>
> Alistair
>
> > ---
> >  target/riscv/pmp.c | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/target/riscv/pmp.c b/target/riscv/pmp.c
> > index 5b14eb511a..8e25f145e0 100644
> > --- a/target/riscv/pmp.c
> > +++ b/target/riscv/pmp.c
> > @@ -120,6 +120,11 @@ static void pmp_write_cfg(CPURISCVState *env, uint32_t pmp_index, uint8_t val)
> >          if (locked) {
> >              qemu_log_mask(LOG_GUEST_ERROR, "ignoring pmpcfg write - locked\n");
> >          } else {
> > +            /* If !mseccfg.MML then ignore writes with encoding RW=01 */
> > +            if ((val & PMP_WRITE) && !(val & PMP_READ) &&
> > +                !MSECCFG_MML_ISSET(env)) {
> > +                val &= ~(PMP_WRITE | PMP_READ);
> > +            }
> >              env->pmp_state.pmp[pmp_index].cfg_reg = val;
> >              pmp_update_rule(env, pmp_index);
> >          }
> > --
> > 2.34.1
> >
> >


      reply	other threads:[~2023-10-11 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 11:10 [PATCH v2] target/riscv: pmp: Ignore writes when RW=01 Mayuresh Chitale
2023-10-09  1:22 ` Alistair Francis
2023-10-09  1:25 ` Alistair Francis
2023-10-11 15:34   ` Mayuresh Chitale [this message]

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='CAN37VV7YBOn0OZ-ih4thwqNdbF9LAo9p9zJOBsWK6QsUXaDi=g@mail.gmail.com' \
    --to=mchitale@ventanamicro.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    /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).