From: Hesham Almatary <hesham.almatary@cl.cam.ac.uk>
To: Jonathan Behrens <fintelia@gmail.com>
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] [Qemu-riscv] [PATCH 1/2] RISC-V: Raise access fault exceptions on PMP violations
Date: Sun, 19 May 2019 00:16:05 +0100 [thread overview]
Message-ID: <CA+wsVCAhH+2gxQwcaJY5_w4FSPjO9Vv7nN2En9t_56p_UuHfmw@mail.gmail.com> (raw)
In-Reply-To: <CANnJOVHoc3fAx=_iuOxaKjtWoUg2_npXu+CzQ+CcppevBmddtA@mail.gmail.com>
Hi Jonathan,
Thanks for your feedback.
On Sat, 18 May 2019 at 22:51, Jonathan Behrens <fintelia@gmail.com> wrote:
>
> This patch assumes that translation failure should always raise a paging fault, but it should be possible for it to raise an access fault as well (since according to the spec "PMP checks are also applied to page-table accesses for virtual-address translation, for which the effective privilege mode is S."). I think the code to actually do the PMP checking during page table walks is currently unimplemented though...
>
The patch actually fixes (rather than assumes) one issue of the
current implementation which always raises a paging fault "when
translation succeeds and PMP fails". The second issue that you report
here which happens "when the PTW fails the PMP check" could be another
future separate fix.
I am happy to submit another patch to fix the second issue.
> Jonathan
>
> On Sat, May 18, 2019 at 3:14 PM Hesham Almatary <Hesham.Almatary@cl.cam.ac.uk> wrote:
>>
>> Section 3.6 in RISC-V v1.10 privilege specification states that PMP violations
>> report "access exceptions." The current PMP implementation has
>> a bug which wrongly reports "page exceptions" on PMP violations.
>>
>> This patch fixes this bug by reporting the correct PMP access exceptions
>> trap values.
>>
>> Signed-off-by: Hesham Almatary <hesham.almatary@cl.cam.ac.uk>
>> ---
>> target/riscv/cpu_helper.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
>> index 41d6db41c3..b48de36114 100644
>> --- a/target/riscv/cpu_helper.c
>> +++ b/target/riscv/cpu_helper.c
>> @@ -318,12 +318,13 @@ restart:
>> }
>>
>> static void raise_mmu_exception(CPURISCVState *env, target_ulong address,
>> - MMUAccessType access_type)
>> + MMUAccessType access_type, bool pmp_violation)
>> {
>> CPUState *cs = CPU(riscv_env_get_cpu(env));
>> int page_fault_exceptions =
>> (env->priv_ver >= PRIV_VERSION_1_10_0) &&
>> - get_field(env->satp, SATP_MODE) != VM_1_10_MBARE;
>> + get_field(env->satp, SATP_MODE) != VM_1_10_MBARE &&
>> + !pmp_violation;
>> switch (access_type) {
>> case MMU_INST_FETCH:
>> cs->exception_index = page_fault_exceptions ?
>> @@ -389,6 +390,7 @@ bool riscv_cpu_tlb_fill(CPUState *cs, vaddr address, int size,
>> CPURISCVState *env = &cpu->env;
>> hwaddr pa = 0;
>> int prot;
>> + bool pmp_violation = false;
>> int ret = TRANSLATE_FAIL;
>>
>> qemu_log_mask(CPU_LOG_MMU, "%s ad %" VADDR_PRIx " rw %d mmu_idx %d\n",
>> @@ -402,6 +404,7 @@ bool riscv_cpu_tlb_fill(CPUState *cs, vaddr address, int size,
>>
>> if (riscv_feature(env, RISCV_FEATURE_PMP) &&
>> !pmp_hart_has_privs(env, pa, TARGET_PAGE_SIZE, 1 << access_type)) {
>> + pmp_violation = true;
>> ret = TRANSLATE_FAIL;
>> }
>> if (ret == TRANSLATE_SUCCESS) {
>> @@ -411,7 +414,7 @@ bool riscv_cpu_tlb_fill(CPUState *cs, vaddr address, int size,
>> } else if (probe) {
>> return false;
>> } else {
>> - raise_mmu_exception(env, address, access_type);
>> + raise_mmu_exception(env, address, access_type, pmp_violation);
>> riscv_raise_exception(env, cs->exception_index, retaddr);
>> }
>> #else
>> --
>> 2.17.1
>>
>>
prev parent reply other threads:[~2019-05-19 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 19:13 [Qemu-devel] [PATCH 1/2] RISC-V: Raise access fault exceptions on PMP violations Hesham Almatary
2019-05-18 19:13 ` [Qemu-devel] [PATCH 2/2] RISC-V: Only Check PMP if MMU translation succeeds Hesham Almatary
2019-05-18 21:50 ` [Qemu-devel] [Qemu-riscv] [PATCH 1/2] RISC-V: Raise access fault exceptions on PMP violations Jonathan Behrens
2019-05-18 23:16 ` Hesham Almatary [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=CA+wsVCAhH+2gxQwcaJY5_w4FSPjO9Vv7nN2En9t_56p_UuHfmw@mail.gmail.com \
--to=hesham.almatary@cl.cam.ac.uk \
--cc=Alistair.Francis@wdc.com \
--cc=fintelia@gmail.com \
--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: 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).