From: Richard Henderson <richard.henderson@linaro.org>
To: Alexey Baturo <baturo.alexey@gmail.com>
Cc: qemu-riscv@nongnu.org, sagark@eecs.berkeley.edu,
kbastian@mail.uni-paderborn.de, Bin Meng <bin.meng@windriver.com>,
qemu-devel@nongnu.org, space.monkey.delivers@gmail.com,
Alistair.Francis@wdc.com, kupokupokupopo@gmail.com,
palmer@dabbelt.com
Subject: Re: [PATCH v13 7/7] [RISCV_PM] Allow experimental J-ext to be turned on
Date: Fri, 15 Oct 2021 17:04:22 -0700 [thread overview]
Message-ID: <58571939-2bb5-40c7-548a-22ba6222b5db@linaro.org> (raw)
In-Reply-To: <20211015192931.227387-8-space.monkey.delivers@gmail.com>
On 10/15/21 12:29 PM, Alexey Baturo wrote:
> Signed-off-by: Alexey Baturo<space.monkey.delivers@gmail.com>
> ---
> target/riscv/cpu.c | 4 ++++
> 1 file changed, 4 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2021-10-16 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 19:29 [PATCH v13 0/7] RISC-V Pointer Masking implementatio Alexey Baturo
2021-10-15 19:29 ` [PATCH v13 1/7] [RISCV_PM] Add J-extension into RISC-V Alexey Baturo
2021-10-15 19:29 ` [PATCH v13 2/7] [RISCV_PM] Add CSR defines for RISC-V PM extension Alexey Baturo
2021-10-15 19:29 ` [PATCH v13 3/7] [RISCV_PM] Support CSRs required for RISC-V PM extension except for the h-mode Alexey Baturo
2021-10-16 0:03 ` Richard Henderson
2021-10-15 19:29 ` [PATCH v13 4/7] [RISCV_PM] Print new PM CSRs in QEMU logs Alexey Baturo
2021-10-15 19:29 ` [PATCH v13 5/7] [RISCV_PM] Support pointer masking for RISC-V for i/c/f/d/a types of instructions Alexey Baturo
2021-10-15 23:49 ` Richard Henderson
2021-10-17 17:21 ` Alexey Baturo
2021-10-15 19:29 ` [PATCH v13 6/7] [RISCV_PM] Implement address masking functions required for RISC-V Pointer Masking extension Alexey Baturo
2021-10-16 0:01 ` Richard Henderson
2021-10-17 17:14 ` Alexey Baturo
2021-10-15 19:29 ` [PATCH v13 7/7] [RISCV_PM] Allow experimental J-ext to be turned on Alexey Baturo
2021-10-16 0:04 ` Richard Henderson [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=58571939-2bb5-40c7-548a-22ba6222b5db@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=baturo.alexey@gmail.com \
--cc=bin.meng@windriver.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=kupokupokupopo@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
--cc=space.monkey.delivers@gmail.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).