From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, "Yanan Wang" <wangyanan55@huawei.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v7 00/12] TCG Plugin inline operation enhancement
Date: Mon, 04 Mar 2024 18:07:50 +0000 [thread overview]
Message-ID: <877cihyio9.fsf@draig.linaro.org> (raw)
In-Reply-To: <20240304130036.124418-1-pierrick.bouvier@linaro.org> (Pierrick Bouvier's message of "Mon, 4 Mar 2024 17:00:24 +0400")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
> This series adds a new thread-safe API to declare inline operation
> inside plugins. As well, it removes the existing non thread-safe API,
> and migrates all existing plugins to use it.
>
> Tested on Linux (user, system) for i386, x86_64 and aarch64.
>
> To give some context, this a long term series of work around plugins,
> with the goal to be able to do basic operations in a more performant and
> accurate way. This will mean to add more inline operations and
> conditional callbacks.
>
> One final target of this work is to implement a plugin that implements
> the icount=auto feature, and allow QEMU to run at a given "frequency"
> based on number of instructions executed, without QEMU needing to keep
> track of this.
>
> Another final target is to be able to detect control flow changes in an
> efficient and elegant way, by combining inline operation and conditional
> callbacks.
Queued to plugins/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2024-03-04 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:00 [PATCH v7 00/12] TCG Plugin inline operation enhancement Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 01/12] plugins: scoreboard API Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 02/12] plugins: define qemu_plugin_u64 Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 03/12] plugins: implement inline operation relative to cpu_index Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 04/12] plugins: add inline operation per vcpu Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 05/12] tests/plugin: add test plugin for inline operations Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 06/12] tests/plugin/mem: migrate to new per_vcpu API Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 07/12] tests/plugin/insn: " Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 08/12] tests/plugin/bb: " Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 09/12] contrib/plugins/hotblocks: " Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 10/12] contrib/plugins/howvec: " Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 11/12] plugins: remove non per_vcpu inline operation from API Pierrick Bouvier
2024-03-04 13:00 ` [PATCH v7 12/12] plugins: cleanup codepath for previous inline operation Pierrick Bouvier
2024-03-04 18:07 ` Alex Bennée [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=877cihyio9.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=eduardo@habkost.net \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wangyanan55@huawei.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 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.