From: Cornelia Huck <cohuck@redhat.com>
To: Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, eric.auger@redhat.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
peter.maydell@linaro.org, maz@kernel.org, oliver.upton@linux.dev,
sebott@redhat.com, gshan@redhat.com, ddutile@redhat.com,
peterx@redhat.com, philmd@linaro.org, pbonzini@redhat.com
Subject: Re: [PATCH v4 08/10] hw/arm/virt: Declare AArch32 DBGDTRTX as safe to ignore in incoming stream
Date: Tue, 23 Dec 2025 15:30:14 +0100 [thread overview]
Message-ID: <87a4z9p8y1.fsf@redhat.com> (raw)
In-Reply-To: <20251222134110.3649287-9-eric.auger@redhat.com>
On Mon, Dec 22 2025, Eric Auger <eric.auger@redhat.com> wrote:
> With the new infrastructure in place it is now feasible to teach
> qemu that it is safe to ignore a sysreg in the incoming migration
> stream. So with the plan to revert commit 4f2b82f60431 ("target/arm:
> Reinstate bogus AArch32 DBGDTRTX register for migration compat) from
<pedantic> Missing closing '"' </pedantic>
> qemu 11 onwards, let's add a compat in 10.2 machine options stating
QEMU 11.0?
> that this reg is safe to ignore. from 11.0 onwards we will not need
> that register anymore.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>
> ---
>
> v3 -> v4:
> - add a comment related to DBGDTRTX (Connie)
> ---
> hw/arm/virt.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index ec0af8e6e7..00948887a2 100644
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -100,6 +100,15 @@ static GlobalProperty arm_virt_compat_defaults[] = {
> static const size_t arm_virt_compat_defaults_len =
> G_N_ELEMENTS(arm_virt_compat_defaults);
>
> +/* Register erronously exposed on 10.2 and earlier */
> +#define DBGDTRTX 0x40200000200e0298
> +
> +static GlobalProperty arm_virt_compat_10_2[] = {
> + { TYPE_ARM_CPU, "x-mig-safe-missing-regs", stringify(DBGDTRTX)},
> +};
> +static const size_t arm_virt_compat_10_2_len =
> + G_N_ELEMENTS(arm_virt_compat_10_2);
> +
> /*
> * This cannot be called from the virt_machine_class_init() because
> * TYPE_VIRT_MACHINE is abstract and mc->compat_props g_ptr_array_new()
> @@ -3536,6 +3545,7 @@ type_init(machvirt_machine_init);
>
> static void virt_machine_10_2_options(MachineClass *mc)
> {
> + compat_props_add(mc->compat_props, arm_virt_compat_10_2, arm_virt_compat_10_2_len);
> }
> DEFINE_VIRT_MACHINE_AS_LATEST(10, 2)
>
Hm, maybe rebase this on top of the new machine types?
next prev parent reply other threads:[~2025-12-23 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 13:39 [PATCH v4 00/10] Mitigation of "failed to load cpu:cpreg_vmstate_array_len" migration failures Eric Auger
2025-12-22 13:39 ` [PATCH v4 01/10] hw/arm/virt: Rename arm_virt_compat into arm_virt_compat_defaults Eric Auger
2025-12-22 13:39 ` [PATCH v4 02/10] target/arm/machine: Improve traces on register mismatch during migration Eric Auger
2025-12-22 13:40 ` [PATCH v4 03/10] target/arm/cpu: Allow registers to be hidden Eric Auger
2025-12-23 14:24 ` Cornelia Huck
2025-12-22 13:40 ` [PATCH v4 04/10] target/arm/machine: Allow extra regs in the incoming stream Eric Auger
2025-12-22 13:40 ` [PATCH v4 05/10] kvm-all: Enforce hidden regs are never accessed Eric Auger
2025-12-22 13:40 ` [PATCH v4 06/10] target/arm/cpu: Implement hide_reg callback() Eric Auger
2025-12-22 13:40 ` [PATCH v4 07/10] target/arm/cpu: Expose x-mig-hidden-regs and x-mig-safe-missing-regs properties Eric Auger
2025-12-23 14:27 ` Cornelia Huck
2025-12-22 13:40 ` [PATCH v4 08/10] hw/arm/virt: Declare AArch32 DBGDTRTX as safe to ignore in incoming stream Eric Auger
2025-12-23 14:30 ` Cornelia Huck [this message]
2026-01-07 17:18 ` Eric Auger
2025-12-22 13:40 ` [PATCH v4 09/10] Revert "target/arm: Reinstate bogus AArch32 DBGDTRTX register for migration compat" Eric Auger
2025-12-22 13:40 ` [PATCH v4 10/10] hw/arm/virt: [DO NOT UPSTREAM] Enforce compatibility with older kernels Eric Auger
2026-01-07 15:02 ` [PATCH v4 00/10] Mitigation of "failed to load cpu:cpreg_vmstate_array_len" migration failures Sebastian Ott
2026-01-07 17:17 ` Eric Auger
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=87a4z9p8y1.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=ddutile@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=gshan@redhat.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sebott@redhat.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.