From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>
Subject: Re: [PATCH v3 7/8] plugins: distinct types for callbacks
Date: Tue, 26 Mar 2024 16:26:10 +0400 [thread overview]
Message-ID: <479d5efe-37c8-4d69-9bdb-340452e49ba8@linaro.org> (raw)
In-Reply-To: <32cec6a3-3535-4464-983a-894d3ba937bf@linaro.org>
On 3/25/24 23:23, Richard Henderson wrote:
> On 3/25/24 02:41, Pierrick Bouvier wrote:
>> To prevent errors when writing new types of callbacks or inline
>> operations, we split callbacks data to distinct types.
>>
>> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>> ---
>> include/qemu/plugin.h | 46 ++++++++++++++-----------
>> plugins/plugin.h | 2 +-
>> accel/tcg/plugin-gen.c | 58 +++++++++++++++++---------------
>> plugins/core.c | 76 ++++++++++++++++++++++--------------------
>> 4 files changed, 98 insertions(+), 84 deletions(-)
>>
>> diff --git a/include/qemu/plugin.h b/include/qemu/plugin.h
>> index bb224b8e4c7..a078229942f 100644
>> --- a/include/qemu/plugin.h
>> +++ b/include/qemu/plugin.h
>> @@ -73,34 +73,40 @@ enum plugin_dyn_cb_type {
>> PLUGIN_CB_INLINE_STORE_U64,
>> };
>>
>> +struct qemu_plugin_regular_cb {
>> + union qemu_plugin_cb_sig f;
>> + TCGHelperInfo *info;
>> + void *userp;
>> + enum qemu_plugin_mem_rw rw;
>> +};
>> +
>> +struct qemu_plugin_inline_cb {
>> + qemu_plugin_u64 entry;
>> + enum qemu_plugin_op op;
>> + uint64_t imm;
>> + enum qemu_plugin_mem_rw rw;
>> +};
>
> Do you still need 'op' anymore here?
> It seems redundant with 'type'.
>
You're right, removed it in a new commit, will post new series.
> Otherwise,
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
>
> r~
next prev parent reply other threads:[~2024-03-26 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:41 [PATCH v3 0/8] TCG plugins new inline operations Pierrick Bouvier
2024-03-25 12:41 ` [PATCH v3 1/8] plugins: prepare introduction of new inline ops Pierrick Bouvier
2024-03-25 12:41 ` [PATCH v3 2/8] plugins: extract generate ptr for qemu_plugin_u64 Pierrick Bouvier
2024-03-25 19:09 ` Richard Henderson
2024-03-25 12:41 ` [PATCH v3 3/8] plugins: add new inline op STORE_U64 Pierrick Bouvier
2024-03-25 19:11 ` Richard Henderson
2024-03-25 12:41 ` [PATCH v3 4/8] tests/plugin/inline: add test for STORE_U64 inline op Pierrick Bouvier
2024-03-25 19:11 ` Richard Henderson
2024-03-25 12:41 ` [PATCH v3 5/8] plugins: conditional callbacks Pierrick Bouvier
2024-03-25 19:17 ` Richard Henderson
2024-03-25 12:41 ` [PATCH v3 6/8] tests/plugin/inline: add test for conditional callback Pierrick Bouvier
2024-03-25 12:41 ` [PATCH v3 7/8] plugins: distinct types for callbacks Pierrick Bouvier
2024-03-25 19:23 ` Richard Henderson
2024-03-26 12:26 ` Pierrick Bouvier [this message]
2024-03-25 12:41 ` [PATCH v3 8/8] plugins: extract cpu_index generate Pierrick Bouvier
2024-03-25 19:19 ` Richard Henderson
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=479d5efe-37c8-4d69-9bdb-340452e49ba8@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=pbonzini@redhat.com \
--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 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).