From: "Alex Bennée" <alex.bennee@linaro.org>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: "Palmer Dabbelt" <palmer@dabbelt.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Bin Meng" <bin.meng@windriver.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Mikhail Tyutin" <m.tyutin@yadro.com>,
"Aleksandr Anenkov" <a.anenkov@yadro.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Fabiano Rosas" <farosas@suse.de>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v7 0/4] gdbstub and TCG plugin improvements
Date: Fri, 15 Dec 2023 15:18:00 +0000 [thread overview]
Message-ID: <87a5qb8pg7.fsf@draig.linaro.org> (raw)
In-Reply-To: <20231213-riscv-v7-0-a760156a337f@daynix.com> (Akihiko Odaki's message of "Wed, 13 Dec 2023 14:19:28 +0900")
Akihiko Odaki <akihiko.odaki@daynix.com> writes:
> This series extracts fixes and refactorings that can be applied
> independently from "[PATCH v9 00/23] plugins: Allow to read registers".
>
> The patch "target/riscv: Move MISA limits to class" was replaced with
> patch "target/riscv: Move misa_mxl_max to class" since I found instances
> may have different misa_ext_mask.
I'm happy to take this through my tree with the register work if the
remaining patches get some review from the RiscV maintainers.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2023-12-15 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 5:19 [PATCH v7 0/4] gdbstub and TCG plugin improvements Akihiko Odaki
2023-12-13 5:19 ` [PATCH v7 1/4] hw/riscv: Use misa_mxl instead of misa_mxl_max Akihiko Odaki
2023-12-13 5:19 ` [PATCH v7 2/4] target/riscv: Remove misa_mxl validation Akihiko Odaki
2023-12-13 5:19 ` [PATCH v7 3/4] target/riscv: Move misa_mxl_max to class Akihiko Odaki
2023-12-15 5:46 ` Alistair Francis
2023-12-13 5:19 ` [PATCH v7 4/4] target/riscv: Validate misa_mxl_max only once Akihiko Odaki
2023-12-15 5:47 ` Alistair Francis
2023-12-15 15:18 ` Alex Bennée [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=87a5qb8pg7.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=a.anenkov@yadro.com \
--cc=akihiko.odaki@daynix.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=farosas@suse.de \
--cc=liwei1518@gmail.com \
--cc=m.tyutin@yadro.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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 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.