qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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, qemu-devel@nongnu.org,
	space.monkey.delivers@gmail.com, Alistair.Francis@wdc.com,
	kupokupokupopo@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH v3 3/5] [RISCV_PM] Print new PM CSRs in QEMU logs
Date: Fri, 16 Oct 2020 16:49:19 -0700	[thread overview]
Message-ID: <08b76ff3-a2a9-8ed5-a117-4168720a31a9@linaro.org> (raw)
In-Reply-To: <20201016221138.10371-4-space.monkey.delivers@gmail.com>

On 10/16/20 3:11 PM, Alexey Baturo wrote:
> Signed-off-by: Alexey Baturo <space.monkey.delivers@gmail.com>
> ---
>  target/riscv/cpu.c | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

r~



  reply	other threads:[~2020-10-16 23:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 22:11 [PATCH v3 0/5] RISC-V Pointer Masking implementation Alexey Baturo
2020-10-16 22:11 ` [PATCH v3 1/5] [RISCV_PM] Add J-extension into RISC-V Alexey Baturo
2020-10-16 23:57   ` Richard Henderson
2020-10-16 22:11 ` [PATCH v3 2/5] [RISCV_PM] Support CSRs required for RISC-V PM extension except for ones in hypervisor mode Alexey Baturo
2020-10-16 23:57   ` Richard Henderson
2020-10-16 22:11 ` [PATCH v3 3/5] [RISCV_PM] Print new PM CSRs in QEMU logs Alexey Baturo
2020-10-16 23:49   ` Richard Henderson [this message]
2020-10-16 22:11 ` [PATCH v3 4/5] [RISCV_PM] Support pointer masking for RISC-V for i/c/f/d/a types of instructions Alexey Baturo
2020-10-16 23:49   ` Richard Henderson
2020-10-16 22:11 ` [PATCH v3 5/5] [RISCV_PM] Implement address masking functions required for RISC-V Pointer Masking extension Alexey Baturo
2020-10-16 23:47   ` Richard Henderson
2020-10-16 22:24 ` [PATCH v3 0/5] RISC-V Pointer Masking implementation no-reply

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=08b76ff3-a2a9-8ed5-a117-4168720a31a9@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=Alistair.Francis@wdc.com \
    --cc=baturo.alexey@gmail.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).