From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Rowan Hart <rowanbhart@gmail.com>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PATCH v4 9/9] plugins: Update plugin version and add notes
Date: Thu, 29 May 2025 11:53:05 -0700 [thread overview]
Message-ID: <8e172b99-595b-4a8c-a97b-df679784aca4@linaro.org> (raw)
In-Reply-To: <20250523020344.1341179-10-rowanbhart@gmail.com>
On 5/22/25 7:03 PM, Rowan Hart wrote:
> From: novafacing <rowanbhart@gmail.com>
>
> This patch updates the plugin version to gate new APIs and adds notes
> describing what has been added.
>
> Signed-off-by: Rowan Hart <rowanbhart@gmail.com>
> ---
> include/qemu/qemu-plugin.h | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/include/qemu/qemu-plugin.h b/include/qemu/qemu-plugin.h
> index 2cb5de9f64..170a79e667 100644
> --- a/include/qemu/qemu-plugin.h
> +++ b/include/qemu/qemu-plugin.h
> @@ -65,11 +65,18 @@ typedef uint64_t qemu_plugin_id_t;
> *
> * version 4:
> * - added qemu_plugin_read_memory_vaddr
> + *
> + * version 5:
> + * - added qemu_plugin_write_memory_vaddr
> + * - added qemu_plugin_read_memory_hwaddr
> + * - added qemu_plugin_write_memory_hwaddr
> + * - added qemu_plugin_write_register
> + * - added qemu_plugin_translate_vaddr
> */
>
> extern QEMU_PLUGIN_EXPORT int qemu_plugin_version;
>
> -#define QEMU_PLUGIN_VERSION 4
> +#define QEMU_PLUGIN_VERSION 5
>
> /**
> * struct qemu_info_t - system information for plugins
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
prev parent reply other threads:[~2025-05-29 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 2:03 [PATCH v4 0/9] Add additional plugin API functions to read and write memory and registers Rowan Hart
2025-05-23 2:03 ` [PATCH v4 1/9] gdbstub: Expose gdb_write_register function to consumers of gdbstub Rowan Hart
2025-05-29 18:40 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 2/9] plugins: Add register write API Rowan Hart
2025-05-29 18:41 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 3/9] plugins: Add enforcement of QEMU_PLUGIN_CB flags in register R/W callbacks Rowan Hart
2025-05-29 19:05 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 4/9] plugins: Add memory virtual address write API Rowan Hart
2025-05-29 18:44 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 5/9] plugins: Add memory hardware address read/write API Rowan Hart
2025-05-29 18:46 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 6/9] plugins: Add patcher plugin and test Rowan Hart
2025-05-29 18:53 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 7/9] plugins: Add hypercalls " Rowan Hart
2025-05-23 2:03 ` [PATCH v4 8/9] plugins: Remove use of qemu_plugin_read_register where it is not permitted Rowan Hart
2025-05-29 18:51 ` Pierrick Bouvier
2025-05-23 2:03 ` [PATCH v4 9/9] plugins: Update plugin version and add notes Rowan Hart
2025-05-29 18:53 ` Pierrick Bouvier [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=8e172b99-595b-4a8c-a97b-df679784aca4@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=eduardo@habkost.net \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rowanbhart@gmail.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).