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 v3 2/5] plugins: add read-only property for registers
Date: Mon, 26 Jan 2026 20:46:54 +0000 [thread overview]
Message-ID: <87pl6wcda9.fsf@draig.linaro.org> (raw)
In-Reply-To: <871pjcdt5q.fsf@draig.linaro.org> ("Alex Bennée"'s message of "Mon, 26 Jan 2026 20:18:41 +0000")
Alex Bennée <alex.bennee@linaro.org> writes:
> Florian Hofhammer <florian.hofhammer@epfl.ch> writes:
>
>> Some registers should be marked as read-only from a plugin API
>> perspective, as writing to them via qemu_plugin_write_register has no
>> effect. This includes the program counter, and we expose this fact to
>> the plugins with this patch.
>>
>> Signed-off-by: Florian Hofhammer <florian.hofhammer@epfl.ch>
>> ---
>> include/qemu/qemu-plugin.h | 2 ++
>> plugins/api.c | 17 +++++++++++++++++
>> 2 files changed, 19 insertions(+)
>>
>> diff --git a/include/qemu/qemu-plugin.h b/include/qemu/qemu-plugin.h
>> index f976b62030..1f25fb2b40 100644
>> --- a/include/qemu/qemu-plugin.h
>> +++ b/include/qemu/qemu-plugin.h
>> @@ -942,11 +942,13 @@ struct qemu_plugin_register;
>> * writing value with qemu_plugin_write_register
>> * @name: register name
>> * @feature: optional feature descriptor, can be NULL
>> + * @is_readonly: true if the register cannot be written via qemu_plugin_write_register
>> */
>> typedef struct {
>> struct qemu_plugin_register *handle;
>> const char *name;
>> const char *feature;
>> + bool is_readonly;
>> } qemu_plugin_reg_descriptor;
>>
>> /**
>> diff --git a/plugins/api.c b/plugins/api.c
>> index fc19bdb40b..de8c32db50 100644
>> --- a/plugins/api.c
>> +++ b/plugins/api.c
>> @@ -403,6 +403,12 @@ bool qemu_plugin_bool_parse(const char *name, const char *value, bool *ret)
>> * ancillary data the plugin might find useful.
>> */
>>
>> +static const char pc_str[] = "pc"; // generic name for program counter
>> +static const char eip_str[] = "eip"; // x86 specific name for program counter
>> +static const char rip_str[] = "rip"; // x86_64 specific name for program counter
>> +static const char pswa_str[] = "pswa"; // s390x specific name for program counter
>> +static const char iaoq_str[] = "iaoq"; // HP/PA specific name for program counter
>> +static const char rpc_str[] = "rpc"; // microblaze specific name for
>> program counter
>
> It's ugly but I can't think of anything better as you say in the commit message.
>
>> static GArray *create_register_handles(GArray *gdbstub_regs)
>> {
>> GArray *find_data = g_array_new(true, true,
>> @@ -417,9 +423,20 @@ static GArray *create_register_handles(GArray *gdbstub_regs)
>> continue;
>> }
>>
>> + gint plugin_ro_bit = 0;
>> /* Create a record for the plugin */
>> desc.handle = GINT_TO_POINTER(grd->gdb_reg + 1);
>> desc.name = g_intern_string(grd->name);
>
> Lets just set desc.is_readonly to false here.
>
>> + if (!strcmp(desc.name, pc_str)
>> + || !strcmp(desc.name, eip_str)
>> + || !strcmp(desc.name, rip_str)
>> + || !strcmp(desc.name, pswa_str)
>> + || !strcmp(desc.name, iaoq_str)
>> + || !strcmp(desc.name, rpc_str)
>> + ) {
>> + plugin_ro_bit = 1;
>> + }
>> + desc.is_readonly = plugin_ro_bit == 1 ? true : false;
>
> And fold setting it to true into the if statement. I have a marginal
> preference for g_strcmp0(desc.name, eip_str) == 0 style tests.
The option of course would be to skip the register all together. Do we
have code which will have multiple vaddr's for the same TB where using
the TB data wouldn't be sufficient?
>
>> desc.feature = g_intern_string(grd->feature_name);
>> g_array_append_val(find_data, desc);
>> }
>
> Otherwise:
>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-01-26 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 15:19 [PATCH v3 0/5] Enable PC diversion via the plugin API Florian Hofhammer
2026-01-20 15:22 ` [PATCH v3 1/5] plugins: add PC diversion API function Florian Hofhammer
2026-01-26 20:31 ` Alex Bennée
2026-01-20 15:23 ` [PATCH v3 2/5] plugins: add read-only property for registers Florian Hofhammer
2026-01-26 20:18 ` Alex Bennée
2026-01-26 20:46 ` Alex Bennée [this message]
2026-02-13 13:38 ` Florian Hofhammer
2026-02-13 18:36 ` Pierrick Bouvier
2026-02-16 12:54 ` Florian Hofhammer
2026-02-17 2:30 ` Pierrick Bouvier
2026-02-20 16:34 ` Alex Bennée
2026-01-20 15:23 ` [PATCH v3 3/5] plugins: prohibit writing to read-only registers Florian Hofhammer
2026-01-20 15:24 ` [PATCH v3 4/5] tests/tcg: add test for qemu_plugin_set_pc API Florian Hofhammer
2026-01-20 15:26 ` [PATCH v3 5/5] tests/tcg/plugins: test register readonly feature Florian Hofhammer
2026-01-26 19:17 ` [PATCH v3 0/5] 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=87pl6wcda9.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.