From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: Pierrick Bouvier <pierrick.bouvier@linaro.org>,
Anton Johansson <anjo@rev.ng>, Stafford Horne <shorne@gmail.com>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH] target/openrisc: Replace VMSTATE_UINTTL() -> VMSTATE_UINT32()
Date: Mon, 6 Oct 2025 06:12:42 +0200 [thread overview]
Message-ID: <d65a63ca-9c54-4855-979c-56b1c1b351a7@linaro.org> (raw)
In-Reply-To: <20250925004855.59084-1-philmd@linaro.org>
ping
On 25/9/25 02:48, Philippe Mathieu-Daudé wrote:
> Both OpenRISCTLBEntry fields are of uint32_t type. Use the
> appropriate VMSTATE_UINT32() macro.
>
> There is no functional change (the migration stream is not
> modified), because the OpenRISC targets are only built as 32-bit:
>
> $ git grep TARGET_LONG_BITS configs/targets/or1k-*
> configs/targets/or1k-linux-user.mak:5:TARGET_LONG_BITS=32
> configs/targets/or1k-softmmu.mak:5:TARGET_LONG_BITS=32
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> target/openrisc/machine.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/openrisc/machine.c b/target/openrisc/machine.c
> index 081c706d02c..fa054e528bd 100644
> --- a/target/openrisc/machine.c
> +++ b/target/openrisc/machine.c
> @@ -26,8 +26,8 @@ static const VMStateDescription vmstate_tlb_entry = {
> .version_id = 1,
> .minimum_version_id = 1,
> .fields = (const VMStateField[]) {
> - VMSTATE_UINTTL(mr, OpenRISCTLBEntry),
> - VMSTATE_UINTTL(tr, OpenRISCTLBEntry),
> + VMSTATE_UINT32(mr, OpenRISCTLBEntry),
> + VMSTATE_UINT32(tr, OpenRISCTLBEntry),
> VMSTATE_END_OF_LIST()
> }
> };
next prev parent reply other threads:[~2025-10-06 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 0:48 [PATCH] target/openrisc: Replace VMSTATE_UINTTL() -> VMSTATE_UINT32() Philippe Mathieu-Daudé
2025-10-06 4:12 ` Philippe Mathieu-Daudé [this message]
2025-10-06 11:15 ` Anton Johansson via
2025-10-07 8:22 ` Philippe Mathieu-Daudé
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=d65a63ca-9c54-4855-979c-56b1c1b351a7@linaro.org \
--to=philmd@linaro.org \
--cc=anjo@rev.ng \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shorne@gmail.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).