From: Alistair Francis <alistair23@gmail.com> To: Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>, Sagar Karandikar <sagark@eecs.berkeley.edu>, Bastian Koppelmann <kbastian@mail.uni-paderborn.de>, Palmer Dabbelt <palmer@sifive.com>, "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>, Alistair Francis <Alistair.Francis@wdc.com> Subject: Re: [Qemu-devel] [PATCHv3 1/5] RISC-V: Only Check PMP if MMU translation succeeds Date: Tue, 21 May 2019 15:27:38 -0700 [thread overview] Message-ID: <CAKmqyKP=n3p7-Nae29kqWSizo_=U6Pyrq_jnnVRzBtHok=tGpA@mail.gmail.com> (raw) In-Reply-To: <20190521104324.12835-1-Hesham.Almatary@cl.cam.ac.uk> On Tue, May 21, 2019 at 3:44 AM Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> wrote: > > The current implementation unnecessarily checks for PMP even if MMU translation > failed. This may trigger a wrong PMP access exception instead of > a page exception. > > For example, the very first instruction fetched after the first satp write in > S-Mode will trigger a PMP access fault instead of an instruction fetch page > fault. > > This patch prioritises MMU exceptions over PMP exceptions and only checks for > PMP if MMU translation succeeds. It's probably worth noting in the commit message that this commit is only required for the future commits. Otherwise it is a little confusing. Alistair > > Signed-off-by: Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> > --- > target/riscv/cpu_helper.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c > index 41d6db41c3..40fb47e794 100644 > --- a/target/riscv/cpu_helper.c > +++ b/target/riscv/cpu_helper.c > @@ -401,6 +401,7 @@ bool riscv_cpu_tlb_fill(CPUState *cs, vaddr address, int size, > " prot %d\n", __func__, address, ret, pa, prot); > > if (riscv_feature(env, RISCV_FEATURE_PMP) && > + (ret == TRANSLATE_SUCCESS) && > !pmp_hart_has_privs(env, pa, TARGET_PAGE_SIZE, 1 << access_type)) { > ret = TRANSLATE_FAIL; > } > -- > 2.17.1 > >
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Francis <alistair23@gmail.com> To: Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>, Sagar Karandikar <sagark@eecs.berkeley.edu>, Bastian Koppelmann <kbastian@mail.uni-paderborn.de>, Palmer Dabbelt <palmer@sifive.com>, "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>, Alistair Francis <Alistair.Francis@wdc.com> Subject: Re: [Qemu-riscv] [Qemu-devel] [PATCHv3 1/5] RISC-V: Only Check PMP if MMU translation succeeds Date: Tue, 21 May 2019 15:27:38 -0700 [thread overview] Message-ID: <CAKmqyKP=n3p7-Nae29kqWSizo_=U6Pyrq_jnnVRzBtHok=tGpA@mail.gmail.com> (raw) In-Reply-To: <20190521104324.12835-1-Hesham.Almatary@cl.cam.ac.uk> On Tue, May 21, 2019 at 3:44 AM Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> wrote: > > The current implementation unnecessarily checks for PMP even if MMU translation > failed. This may trigger a wrong PMP access exception instead of > a page exception. > > For example, the very first instruction fetched after the first satp write in > S-Mode will trigger a PMP access fault instead of an instruction fetch page > fault. > > This patch prioritises MMU exceptions over PMP exceptions and only checks for > PMP if MMU translation succeeds. It's probably worth noting in the commit message that this commit is only required for the future commits. Otherwise it is a little confusing. Alistair > > Signed-off-by: Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> > --- > target/riscv/cpu_helper.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c > index 41d6db41c3..40fb47e794 100644 > --- a/target/riscv/cpu_helper.c > +++ b/target/riscv/cpu_helper.c > @@ -401,6 +401,7 @@ bool riscv_cpu_tlb_fill(CPUState *cs, vaddr address, int size, > " prot %d\n", __func__, address, ret, pa, prot); > > if (riscv_feature(env, RISCV_FEATURE_PMP) && > + (ret == TRANSLATE_SUCCESS) && > !pmp_hart_has_privs(env, pa, TARGET_PAGE_SIZE, 1 << access_type)) { > ret = TRANSLATE_FAIL; > } > -- > 2.17.1 > >
next prev parent reply other threads:[~2019-05-21 22:31 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-21 10:43 [Qemu-devel] [PATCHv3 1/5] RISC-V: Only Check PMP if MMU translation succeeds Hesham Almatary 2019-05-21 10:43 ` [Qemu-riscv] " Hesham Almatary 2019-05-21 10:43 ` [Qemu-devel] [PATCHv3 2/5] RISC-V: Raise access fault exceptions on PMP violations Hesham Almatary 2019-05-21 10:43 ` [Qemu-riscv] " Hesham Almatary 2019-05-21 10:43 ` [Qemu-devel] [PATCHv3 3/5] RISC-V: Check PMP during Page Table Walks Hesham Almatary 2019-05-21 10:43 ` [Qemu-riscv] " Hesham Almatary 2019-05-21 22:37 ` [Qemu-devel] " Alistair Francis 2019-05-21 22:37 ` [Qemu-riscv] " Alistair Francis 2019-05-22 9:26 ` Hesham Almatary 2019-05-22 9:26 ` [Qemu-riscv] " Hesham Almatary 2019-05-29 18:25 ` Hesham Almatary 2019-05-29 18:25 ` [Qemu-riscv] " Hesham Almatary 2019-05-30 3:07 ` Alistair Francis 2019-05-30 3:07 ` [Qemu-riscv] " Alistair Francis 2019-05-30 13:09 ` Hesham Almatary 2019-05-30 13:09 ` [Qemu-riscv] " Hesham Almatary 2019-05-21 10:43 ` [Qemu-devel] [PATCHv3 4/5] RISC-V: Fix a PMP bug where it succeeds even if PMP entry is off Hesham Almatary 2019-05-21 10:43 ` [Qemu-riscv] " Hesham Almatary 2019-05-21 22:38 ` [Qemu-devel] " Alistair Francis 2019-05-21 22:38 ` [Qemu-riscv] " Alistair Francis 2019-05-21 10:43 ` [Qemu-devel] [PATCHv3 5/5] RISC-V: Fix a PMP check with the correct access size Hesham Almatary 2019-05-21 10:43 ` [Qemu-riscv] " Hesham Almatary 2019-05-21 22:31 ` [Qemu-devel] " Alistair Francis 2019-05-21 22:31 ` [Qemu-riscv] " Alistair Francis 2019-05-22 2:24 ` [Qemu-devel] [Qemu-riscv] " Jonathan Behrens 2019-05-22 2:24 ` [Qemu-riscv] [Qemu-devel] " Jonathan Behrens 2019-05-22 8:55 ` [Qemu-devel] [Qemu-riscv] " Hesham Almatary 2019-05-22 8:55 ` [Qemu-riscv] [Qemu-devel] " Hesham Almatary 2019-05-21 22:27 ` Alistair Francis [this message] 2019-05-21 22:27 ` [Qemu-riscv] [Qemu-devel] [PATCHv3 1/5] RISC-V: Only Check PMP if MMU translation succeeds Alistair Francis 2019-05-22 9:09 Hesham Almatary 2019-05-30 3:11 ` Alistair Francis
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='CAKmqyKP=n3p7-Nae29kqWSizo_=U6Pyrq_jnnVRzBtHok=tGpA@mail.gmail.com' \ --to=alistair23@gmail.com \ --cc=Alistair.Francis@wdc.com \ --cc=Hesham.Almatary@cl.cam.ac.uk \ --cc=kbastian@mail.uni-paderborn.de \ --cc=palmer@sifive.com \ --cc=qemu-devel@nongnu.org \ --cc=qemu-riscv@nongnu.org \ --cc=sagark@eecs.berkeley.edu \ /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: linkBe 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.