qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Alexandre Iooss" <erdnaxe@crans.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	"Yanan Wang" <wangyanan55@huawei.com>,
	"Mahmoud Mandour" <ma.mandourr@gmail.com>,
	qemu-ppc@nongnu.org, "Zhao Liu" <zhao1.liu@intel.com>,
	"Xingtao Yao" <yaoxt.fnst@fujitsu.com>
Subject: Re: [PATCH v8 6/6] tests/tcg/multiarch: add test for plugin memory access
Date: Wed, 11 Sep 2024 18:13:29 +0100	[thread overview]
Message-ID: <874j6mw1ty.fsf@draig.linaro.org> (raw)
In-Reply-To: <20240910172033.1427812-7-pierrick.bouvier@linaro.org> (Pierrick Bouvier's message of "Tue, 10 Sep 2024 10:20:33 -0700")

Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:

> Add an explicit test to check expected memory values are read/written.
> 8,16,32 load/store are tested for all arch.
> 64,128 load/store are tested for aarch64/x64.
> atomic operations (8,16,32,64) are tested for x64 only.
>
> By default, atomic accesses are non atomic if a single cpu is running,
> so we force creation of a second one by creating a new thread first.
>
> load/store helpers code path can't be triggered easily in user mode (no
> softmmu), so we can't test it here.
>
> Output of test-plugin-mem-access.c is the list of expected patterns in
> plugin output. By reading stdout, we can compare to plugins output and
> have a multiarch test.
>
> Can be run with:
> make -C build/tests/tcg/$ARCH-linux-user
> run-plugin-test-plugin-mem-access-with-libmem.so

Queued to plugins/next, thanks.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2024-09-11 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 17:20 [PATCH v8 0/6] plugins: access values during a memory read/write Pierrick Bouvier
2024-09-10 17:20 ` [PATCH v8 1/6] plugins: save value during memory accesses Pierrick Bouvier
2024-09-10 17:20 ` [PATCH v8 2/6] plugins: extend API to get latest memory value accessed Pierrick Bouvier
2024-09-10 17:20 ` [PATCH v8 3/6] tests/tcg: add mechanism to run specific tests with plugins Pierrick Bouvier
2024-09-10 17:20 ` [PATCH v8 4/6] tests/tcg: allow to check output of plugins Pierrick Bouvier
2024-09-10 17:20 ` [PATCH v8 5/6] tests/tcg/plugins/mem: add option to print memory accesses Pierrick Bouvier
2024-09-10 17:20 ` [PATCH v8 6/6] tests/tcg/multiarch: add test for plugin memory access Pierrick Bouvier
2024-09-11 17:13   ` Alex Bennée [this message]
2024-09-11 19:57     ` Pierrick Bouvier

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=874j6mw1ty.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=danielhb413@gmail.com \
    --cc=eduardo@habkost.net \
    --cc=erdnaxe@crans.org \
    --cc=ma.mandourr@gmail.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=npiggin@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=wangyanan55@huawei.com \
    --cc=yaoxt.fnst@fujitsu.com \
    --cc=zhao1.liu@intel.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).