qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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>,
	"Andrew Jones" <ajones@ventanamicro.com>,
	qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v11 0/3] gdbstub and TCG plugin improvements
Date: Sat, 03 Feb 2024 11:08:34 +0000	[thread overview]
Message-ID: <87bk8xpzyl.fsf@draig.linaro.org> (raw)
In-Reply-To: <20240203-riscv-v11-0-a23f4848a628@daynix.com> (Akihiko Odaki's message of "Sat, 03 Feb 2024 19:11:07 +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.

As this is re-based on Alistair's riscv-to-apply.next tree I'll wait for
this to go through the RiscV trees and then re-base the plugin patches
and dropping the merged riscv patches from my tree.

In the meantime feel free to review:

  Message-Id: <20240122145610.413836-1-alex.bennee@linaro.org>
  Date: Mon, 22 Jan 2024 14:55:49 +0000
  Subject: [PATCH v3 00/21] plugin updates (register access) for 9.0 (pre-PR?)
  From: =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>

For:

  contrib/plugins: extend execlog to track register changes
  gdbstub: expose api to find registers

So I can add this to my maintainer omnibus series for the next PR I
send.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  parent reply	other threads:[~2024-02-03 11:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 10:11 [PATCH v11 0/3] gdbstub and TCG plugin improvements Akihiko Odaki
2024-02-03 10:11 ` [PATCH v11 1/3] target/riscv: Remove misa_mxl validation Akihiko Odaki
2024-02-03 10:11 ` [PATCH v11 2/3] target/riscv: Move misa_mxl_max to class Akihiko Odaki
2024-02-03 10:11 ` [PATCH v11 3/3] target/riscv: Validate misa_mxl_max only once Akihiko Odaki
2024-02-03 11:08 ` Alex Bennée [this message]
2024-02-03 11:26   ` [PATCH v11 0/3] gdbstub and TCG plugin improvements Akihiko Odaki
2024-02-03 13:58     ` Alex Bennée
2024-02-04  6:54       ` Akihiko Odaki
2024-02-05  9:31         ` Alex Bennée
2024-02-05 10:03           ` Pierrick Bouvier
2024-02-05 11:20             ` Alex Bennée
2024-02-06  8:36           ` Akihiko Odaki
2024-02-04 23:42 ` Alistair Francis

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=87bk8xpzyl.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=a.anenkov@yadro.com \
    --cc=ajones@ventanamicro.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 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).