From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Rowan Hart" <rowanbhart@gmail.com>
Cc: qemu-devel@nongnu.org,
"Richard Henderson" <richard.henderson@linaro.org>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Alexandre Iooss" <erdnaxe@crans.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v14 0/8] Add additional plugin API functions to read and write memory and registers
Date: Thu, 26 Jun 2025 11:23:03 -0700 [thread overview]
Message-ID: <5606f27e-48c1-40fa-9453-f76f87fecd2e@linaro.org> (raw)
In-Reply-To: <87cyaqzcft.fsf@draig.linaro.org>
On 6/26/25 9:37 AM, Alex Bennée wrote:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> Rowan Hart <rowanbhart@gmail.com> writes:
>>
>>> This patch series adds several new API functions focused on enabling use
>>> cases around reading and writing guest memory from QEMU plugins. To support
>>> these new APIs, some utility functionality around retrieving information about
>>> address spaces is added as well.
>>
>> Queued to plugins/next, thanks.
>
> So this fails a number of the CI tests, mostly due to 32 bit issues:
>
> https://gitlab.com/stsquad/qemu/-/pipelines/1890883927/failures
>
> The tci failure is easy enough:
>
> --8<---------------cut here---------------start------------->8---
> modified tests/tcg/x86_64/Makefile.softmmu-target
> @@ -34,9 +34,11 @@ memory: CFLAGS+=-DCHECK_UNALIGNED=1
> # Running
> QEMU_OPTS+=-device isa-debugcon,chardev=output -device isa-debug-exit,iobase=0xf4,iosize=0x4 -kernel
>
> +ifeq ($(CONFIG_PLUGIN),y)
> run-plugin-patch-target-with-libpatch.so: \
> PLUGIN_ARGS=$(COMMA)target=ffc0$(COMMA)patch=9090$(COMMA)use_hwaddr=true
> run-plugin-patch-target-with-libpatch.so: \
> CHECK_PLUGIN_OUTPUT_COMMAND=$(X64_SYSTEM_SRC)/validate-patch.py $@.out
> run-plugin-patch-target-with-libpatch.so: patch-target libpatch.so
> EXTRA_RUNS+=run-plugin-patch-target-with-libpatch.so
> +endif
> --8<---------------cut here---------------end--------------->8---
>
> The other problem is trying to stuff a uint64_t into a void * on 32 bit.
> We did disable plugins for 32 bit but then reverted because we were able
> to fixup the cases:
>
> cf2a78cbbb (deprecation: don't enable TCG plugins by default on 32 bit hosts)
> db7a06ade1 (configure: reenable plugins by default for 32-bit hosts)
>
> So I don't what is easier:
>
> - re-deprecate for 32 bit systems
> - only build libpatch on 64 bit systems
> - fix libpatch to handle being built on 32 bit systems
>
More context:
../tests/tcg/plugins/patch.c: In function ‘patch_hwaddr’:
../tests/tcg/plugins/patch.c:50:21: error: cast from pointer to integer
of different size [-Werror=pointer-to-int-cast]
50 | uint64_t addr = (uint64_t)userdata;
| ^
../tests/tcg/plugins/patch.c: In function ‘patch_vaddr’:
../tests/tcg/plugins/patch.c:93:21: error: cast from pointer to integer
of different size [-Werror=pointer-to-int-cast]
93 | uint64_t addr = (uint64_t)userdata;
| ^
../tests/tcg/plugins/patch.c: In function ‘vcpu_tb_trans_cb’:
../tests/tcg/plugins/patch.c:159:54: error: cast to pointer from integer
of different size [-Werror=int-to-pointer-cast]
159 | (void *)addr);
| ^
../tests/tcg/plugins/patch.c:163:54: error: cast to pointer from integer
of different size [-Werror=int-to-pointer-cast]
163 | (void *)addr);
|
Since we disabled 64 bit targets on 32 bit hosts, and that data passed
by pointers concern addresses, it should be safe to cast values to
(uintptr_t) instead of (uint64_t).
Pierrick
next prev parent reply other threads:[~2025-06-26 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 17:53 [PATCH v14 0/8] Add additional plugin API functions to read and write memory and registers Rowan Hart
2025-06-24 17:53 ` [PATCH v14 1/8] gdbstub: Expose gdb_write_register function to consumers of gdbstub Rowan Hart
2025-06-24 17:53 ` [PATCH v14 2/8] plugins: Add register write API Rowan Hart
2025-06-24 17:53 ` [PATCH v14 3/8] plugins: Add enforcement of QEMU_PLUGIN_CB flags in register R/W callbacks Rowan Hart
2025-06-24 17:53 ` [PATCH v14 4/8] plugins: Add memory virtual address write API Rowan Hart
2025-06-24 17:53 ` [PATCH v14 5/8] plugins: Add memory hardware address read/write API Rowan Hart
2025-06-24 17:53 ` [PATCH v14 6/8] tests/tcg: Remove copy-pasted notes and from i386 and add x86_64 system tests to tests Rowan Hart
2025-06-24 17:53 ` [PATCH v14 7/8] plugins: Add patcher plugin and test Rowan Hart
2025-06-24 17:53 ` [PATCH v14 8/8] plugins: Update plugin version and add notes Rowan Hart
2025-06-25 14:51 ` [PATCH v14 0/8] Add additional plugin API functions to read and write memory and registers Alex Bennée
2025-06-26 16:37 ` Alex Bennée
2025-06-26 18:23 ` Pierrick Bouvier [this message]
2025-06-27 9:17 ` Alex Bennée
2025-06-27 16:18 ` Pierrick Bouvier
2025-06-27 18:26 ` Alex Bennée
2025-06-27 18:40 ` 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=5606f27e-48c1-40fa-9453-f76f87fecd2e@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=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rowanbhart@gmail.com \
--cc=wangyanan55@huawei.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).