qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Mahmoud Mandour" <ma.mandourr@gmail.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alexandre Iooss" <erdnaxe@crans.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/7] plugins: access values during a memory read/write
Date: Wed, 26 Jun 2024 16:39:05 -0700	[thread overview]
Message-ID: <a5870490-0a99-4c95-a342-8a830f8e3ffb@linaro.org> (raw)
In-Reply-To: <20240626231255.339353-1-pierrick.bouvier@linaro.org>

A v2 was sent to fix a compilation issue on aarch64.

On 6/26/24 16:12, Pierrick Bouvier wrote:
> This series allows plugins to know which value is read/written during a memory
> access.
> 
> For every memory access, we know copy this value before calling mem callbacks,
> and those can query it using new API functions:
> - qemu_plugin_mem_get_value_upper_bits
> - qemu_plugin_mem_get_value_lower_bits
> 
> Mem plugin was extended to print accesses, and a new test was added to check
> functionality work as expected. A bug was found where callbacks were not
> called as expected.
> 
> This will open new use cases for plugins, such as following specific values in
> memory.
> 
> Pierrick Bouvier (7):
>    plugins: fix mem callback array size
>    plugins: save value during memory accesses
>    plugins: extend API to get latest memory value accessed
>    tests/tcg: add mechanism to run specific tests with plugins
>    tests/tcg: allow to check output of plugins
>    tests/plugin/mem: add option to print memory accesses
>    tests/tcg/x86_64: add test for plugin memory access
> 
>   accel/tcg/atomic_template.h                 | 64 +++++++++++++--
>   include/qemu/plugin.h                       |  8 ++
>   include/qemu/qemu-plugin.h                  | 20 +++++
>   accel/tcg/plugin-gen.c                      |  3 +-
>   plugins/api.c                               | 21 +++++
>   plugins/core.c                              |  7 ++
>   tcg/tcg-op-ldst.c                           | 72 +++++++++++++++--
>   tests/plugin/mem.c                          | 28 ++++++-
>   tests/tcg/x86_64/test-plugin-mem-access.c   | 89 +++++++++++++++++++++
>   accel/tcg/atomic_common.c.inc               | 13 ++-
>   accel/tcg/ldst_common.c.inc                 | 38 +++++----
>   plugins/qemu-plugins.symbols                |  2 +
>   tests/tcg/Makefile.target                   |  8 +-
>   tests/tcg/x86_64/Makefile.target            |  7 ++
>   tests/tcg/x86_64/check-plugin-mem-access.sh | 48 +++++++++++
>   15 files changed, 393 insertions(+), 35 deletions(-)
>   create mode 100644 tests/tcg/x86_64/test-plugin-mem-access.c
>   create mode 100755 tests/tcg/x86_64/check-plugin-mem-access.sh
> 


      parent reply	other threads:[~2024-06-26 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 23:12 [PATCH 0/7] plugins: access values during a memory read/write Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 1/7] plugins: fix mem callback array size Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 2/7] plugins: save value during memory accesses Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 3/7] plugins: extend API to get latest memory value accessed Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 4/7] tests/tcg: add mechanism to run specific tests with plugins Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 5/7] tests/tcg: allow to check output of plugins Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 6/7] tests/plugin/mem: add option to print memory accesses Pierrick Bouvier
2024-06-26 23:12 ` [PATCH 7/7] tests/tcg/x86_64: add test for plugin memory access Pierrick Bouvier
2024-06-26 23:39 ` 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=a5870490-0a99-4c95-a342-8a830f8e3ffb@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 \
    /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).