From: Alistair Francis <alistair23@gmail.com>
To: Hou Weiying <weiying_hou@outlook.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v2 0/4] riscv: Add enhanced PMP support
Date: Wed, 10 Feb 2021 12:13:11 -0800 [thread overview]
Message-ID: <CAKmqyKM230JKH4DddGZCmFaPRC-jGufduSDw+KidgqOmA9YpGA@mail.gmail.com> (raw)
In-Reply-To: <SG2PR02MB26340A07DB8609F72486202C93450@SG2PR02MB2634.apcprd02.prod.outlook.com>
On Mon, Aug 10, 2020 at 5:23 PM Hou Weiying <weiying_hou@outlook.com> wrote:
>
> v1 -> v2 :
> * regenerate this patch based on the latest upstream
>
> Hou Weiying (4):
> Define ePMP mseccfg
> Implementation of enhanced PMP(ePMP) support
> Add ePMP CSR accesses
> Add a config option for ePMP.
Thanks for the patches.
Sorry again it has taken so long to get to. I kept hoping that next
week the CSRs would be reserved, but it still hasn't happened.
I have rebased all of the patches and fixed the compile issues. If you
want to pick these up feel free to, otherwise I'll send out the
rebased versions and work on getting them merged.
Alistair
>
> target/riscv/cpu.c | 9 ++
> target/riscv/cpu.h | 3 +
> target/riscv/cpu_bits.h | 3 +
> target/riscv/csr.c | 18 ++++
> target/riscv/gdbstub.c | 2 +
> target/riscv/pmp.c | 174 +++++++++++++++++++++++++++++++++++---
> target/riscv/pmp.h | 12 +++
> target/riscv/trace-events | 4 +
> 8 files changed, 213 insertions(+), 12 deletions(-)
>
> --
> 2.20.1
>
>
prev parent reply other threads:[~2021-02-10 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 0:23 [PATCH v2 0/4] riscv: Add enhanced PMP support Hou Weiying
2021-02-10 20:13 ` Alistair Francis [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=CAKmqyKM230JKH4DddGZCmFaPRC-jGufduSDw+KidgqOmA9YpGA@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
--cc=weiying_hou@outlook.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).