From: "Alex Bennée" <alex.bennee@linaro.org>
To: Florian Hofhammer <florian.hofhammer@epfl.ch>
Cc: qemu-devel@nongnu.org, pierrick.bouvier@linaro.org,
richard.henderson@linaro.org, laurent@vivier.eu,
imp@bsdimp.com, berrange@redhat.com
Subject: Re: [PATCH v4 7/7] tests/tcg/plugins: test register readonly feature
Date: Wed, 25 Feb 2026 09:24:07 +0000 [thread overview]
Message-ID: <87a4wx2n2g.fsf@draig.linaro.org> (raw)
In-Reply-To: <e6be7001-491f-4f5b-9aeb-3d27727d7b9a@epfl.ch> (Florian Hofhammer's message of "Tue, 24 Feb 2026 16:58:25 +0100")
Florian Hofhammer <florian.hofhammer@epfl.ch> writes:
> This commit tests the readonly feature for registers exposed via the
> plugin API introduced earlier in the patch series.
>
> Signed-off-by: Florian Hofhammer <florian.hofhammer@epfl.ch>
Acked-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-02-25 9:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 15:46 [PATCH v4 0/7] Enable PC diversion via the plugin API Florian Hofhammer
2026-02-24 15:48 ` [PATCH v4 1/7] plugins: add flag to specify whether PC is rw Florian Hofhammer
2026-02-24 17:41 ` Alex Bennée
2026-02-24 15:50 ` [PATCH v4 2/7] linux-user: make syscall emulation interruptible Florian Hofhammer
2026-02-24 21:05 ` Pierrick Bouvier
2026-02-25 8:02 ` Florian Hofhammer
2026-02-25 17:00 ` Pierrick Bouvier
2026-02-25 9:25 ` Alex Bennée
2026-02-25 9:29 ` Florian Hofhammer
2026-02-25 12:25 ` Alex Bennée
2026-02-24 15:51 ` [PATCH v4 3/7] plugins: add PC diversion API function Florian Hofhammer
2026-02-24 17:46 ` Alex Bennée
2026-02-24 20:12 ` Pierrick Bouvier
2026-02-25 7:55 ` Florian Hofhammer
2026-02-24 15:52 ` [PATCH v4 4/7] tests/tcg: add test for qemu_plugin_set_pc API Florian Hofhammer
2026-02-24 16:55 ` Brian Cain
2026-02-24 20:24 ` Pierrick Bouvier
2026-02-25 14:58 ` Florian Hofhammer
2026-02-25 17:04 ` Pierrick Bouvier
2026-02-26 8:08 ` Florian Hofhammer
2026-02-24 20:35 ` Pierrick Bouvier
2026-02-25 7:59 ` Florian Hofhammer
2026-02-25 11:49 ` Florian Hofhammer
2026-02-25 17:07 ` Pierrick Bouvier
2026-02-25 17:09 ` Pierrick Bouvier
2026-02-24 21:28 ` Pierrick Bouvier
2026-02-25 8:03 ` Florian Hofhammer
2026-02-25 16:21 ` Florian Hofhammer
2026-02-25 17:30 ` Pierrick Bouvier
2026-02-25 17:39 ` Pierrick Bouvier
2026-02-26 8:30 ` Florian Hofhammer
2026-02-26 19:47 ` Pierrick Bouvier
2026-02-24 15:53 ` [PATCH v4 5/7] plugins: add read-only property for registers Florian Hofhammer
2026-02-24 17:46 ` Alex Bennée
2026-02-26 11:55 ` Florian Hofhammer
2026-02-26 14:33 ` Alex Bennée
2026-02-26 19:43 ` Pierrick Bouvier
2026-02-24 15:57 ` [PATCH v4 6/7] plugins: prohibit writing to read-only registers Florian Hofhammer
2026-02-24 17:49 ` Alex Bennée
2026-03-02 11:52 ` Florian Hofhammer
2026-03-02 13:03 ` Alex Bennée
2026-03-02 13:06 ` Florian Hofhammer
2026-02-24 15:58 ` [PATCH v4 7/7] tests/tcg/plugins: test register readonly feature Florian Hofhammer
2026-02-24 20:17 ` Pierrick Bouvier
2026-02-25 9:24 ` Alex Bennée [this message]
2026-02-24 20:14 ` [PATCH v4 0/7] Enable PC diversion via the plugin API Pierrick Bouvier
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=87a4wx2n2g.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=florian.hofhammer@epfl.ch \
--cc=imp@bsdimp.com \
--cc=laurent@vivier.eu \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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.