From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: qemu-devel@nongnu.org,
Mario Fleischmann <mario.fleischmann@lauterbach.com>
Cc: alex.bennee@linaro.org, philmd@linaro.org, armbru@redhat.com,
christian.boenig@lauterbach.com,
Mario Fleischmann <mario.fleischmann@lauterbach.com>
Subject: Re: [PATCH v2 16/20] gdbstub: Expose gdb_write_register
Date: Mon, 19 May 2025 11:38:40 +0300 [thread overview]
Message-ID: <swi2rj.3jwvaeg7bc4oy@linaro.org> (raw)
In-Reply-To: <20250430052741.21145-17-mario.fleischmann@lauterbach.com>
On Wed, 30 Apr 2025 08:27, Mario Fleischmann <mario.fleischmann@lauterbach.com> wrote:
>Signed-off-by: Mario Fleischmann <mario.fleischmann@lauterbach.com>
>---
> gdbstub/gdbstub.c | 2 +-
> include/exec/gdbstub.h | 10 ++++++++++
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
>diff --git a/gdbstub/gdbstub.c b/gdbstub/gdbstub.c
>index 291ac55..6ace944 100644
>--- a/gdbstub/gdbstub.c
>+++ b/gdbstub/gdbstub.c
>@@ -527,7 +527,7 @@ int gdb_read_register(CPUState *cpu, GByteArray *buf, int reg)
> return 0;
> }
>
>-static int gdb_write_register(CPUState *cpu, uint8_t *mem_buf, int reg)
>+int gdb_write_register(CPUState *cpu, uint8_t *mem_buf, int reg)
> {
> GDBRegisterState *r;
>
>diff --git a/include/exec/gdbstub.h b/include/exec/gdbstub.h
>index c2941e5..e2d8488 100644
>--- a/include/exec/gdbstub.h
>+++ b/include/exec/gdbstub.h
>@@ -130,6 +130,16 @@ const GDBFeature *gdb_find_static_feature(const char *xmlname);
> */
> int gdb_read_register(CPUState *cpu, GByteArray *buf, int reg);
>
>+/**
>+ * gdb_write_register() - Write a register associated with a CPU.
>+ * @cpu: The CPU associated with the register.
>+ * @mem_buf: The buffer that the register will be written from.
I think this is more explanatory:
"The buffer holding the bytes value that will be written to the register."
Either way,
Reviewed-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
>+ * @reg: The register's number returned by gdb_find_feature_register().
>+ *
>+ * Return: The number of written bytes.
>+ */
>+int gdb_write_register(CPUState *cpu, uint8_t *mem_buf, int reg);
>+
> /**
> * typedef GDBRegDesc - a register description from gdbstub
> */
>--
>2.34.1
>
>
next prev parent reply other threads:[~2025-05-19 8:41 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 5:27 [PATCH v2 00/20] Add Multi-Core Debug (MCD) API support Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 01/20] mcd: Introduce Multi-Core Debug (MCD) API Mario Fleischmann
2025-04-30 8:19 ` Daniel P. Berrangé
2025-04-30 12:47 ` Mario Fleischmann
2025-04-30 12:55 ` Daniel P. Berrangé
2025-04-30 15:22 ` Mario Fleischmann
2025-04-30 16:00 ` Daniel P. Berrangé
2025-04-30 5:27 ` [PATCH v2 02/20] meson: Add --enable-mcd option Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 03/20] mcd: Introduce MCD server Mario Fleischmann
2025-05-15 9:46 ` Daniel P. Berrangé
2025-04-30 5:27 ` [PATCH v2 04/20] qapi: Introduce MCD schema Mario Fleischmann
2025-05-08 11:07 ` Markus Armbruster
2025-05-20 7:10 ` Markus Armbruster
2025-04-30 5:27 ` [PATCH v2 05/20] mcd: Introduce MCD server stub Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 06/20] qtest: Introduce MCD test suite Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 07/20] mcd: Implement target initialization API Mario Fleischmann
2025-05-08 12:03 ` Markus Armbruster
2025-05-14 13:59 ` Mario Fleischmann
2025-05-15 9:33 ` Markus Armbruster
2025-05-15 13:02 ` Markus Armbruster
2025-05-19 16:52 ` Mario Fleischmann
2025-05-20 7:13 ` Markus Armbruster
2025-04-30 5:27 ` [PATCH v2 08/20] mcd: Implement server connection API Mario Fleischmann
2025-05-15 9:58 ` Daniel P. Berrangé
2025-05-19 16:54 ` Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 09/20] mcd: Implement target system query Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 10/20] mcd: Implement core connection control Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 11/20] mcd: Implement memory space query Mario Fleischmann
2025-05-19 9:41 ` Manos Pitsidianakis
2025-05-19 18:24 ` Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 12/20] gdbstub: Expose GDBRegisterState Mario Fleischmann
2025-05-19 8:41 ` Manos Pitsidianakis
2025-05-19 18:26 ` Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 13/20] mcd: Implement register query Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 14/20] mcd: Implement runstate control Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 15/20] mcd test: Implement core state query Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 16/20] gdbstub: Expose gdb_write_register Mario Fleischmann
2025-05-19 8:38 ` Manos Pitsidianakis [this message]
2025-04-30 5:27 ` [PATCH v2 17/20] mcd: Implement register/memory access Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 18/20] mcd: Implement single stepping Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 19/20] mcd: Implement trigger control Mario Fleischmann
2025-04-30 5:27 ` [PATCH v2 20/20] mcd: Implement reset control Mario Fleischmann
2025-05-08 11:37 ` [PATCH v2 00/20] Add Multi-Core Debug (MCD) API support Markus Armbruster
2025-05-14 14:05 ` Mario Fleischmann
2025-05-20 7:35 ` Markus Armbruster
2025-05-20 14:16 ` Mario Fleischmann
2025-07-24 5:28 ` Markus Armbruster
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=swi2rj.3jwvaeg7bc4oy@linaro.org \
--to=manos.pitsidianakis@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=christian.boenig@lauterbach.com \
--cc=mario.fleischmann@lauterbach.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 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).