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 07/10] target/arm/cpu: Expose x-mig-hidden-regs and x-mig-safe-missing-regs properties
Date: Tue, 23 Dec 2025 15:27:11 +0100 [thread overview]
Message-ID: <87cy45p934.fsf@redhat.com> (raw)
In-Reply-To: <20251222134110.3649287-8-eric.auger@redhat.com>
On Mon, Dec 22 2025, Eric Auger <eric.auger@redhat.com> wrote:
> Allows to set both array properties along with arm cpus. Their "x-" prefix
> reminds that those shall be used carefully for distro specific use cases
> to enable cross kernel migration.
>
> This will allow to define such compat machine props like:
>
> static GlobalProperty arm_virt_kernel_compat_10_1[] = {
> /* KVM_REG_ARM_VENDOR_HYP_BMAP_2 */
> { TYPE_ARM_CPU, "x-mig-hidden-regs", "0x6030000000160003" },
> { TYPE_ARM_CPU, "x-mig-safe-missing-regs",
> /* TCR_EL1, PIRE0_EL1, PIR_EL1 */
> "0x603000000013c103, 0x603000000013c512, 0x603000000013c513" },
> }
>
> The first one means KVM_REG_ARM_VENDOR_HYP_BMAP_2 shall always
> be hidden for machine types older than 10.1. The second one means
> that along with 10.1 machine type we may receive in the incoming
> migration stream, 3 registers that are unknown on destination.
>
> Obviously, using the reg index as defined in
> linux/Documentation/virt/kvm/api.rst is not user friendly. However
> These options are supposed to be used to enable specific, rare cases,
> and in general, by people trying to configure distribution defaults
> familiar with those specific cases.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>
> ---
>
> v3 -> v4:
> - typo and rewording in the commit description (Connie)
> ---
> target/arm/cpu.c | 5 +++++
> 1 file changed, 5 insertions(+)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2025-12-23 14:27 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 [this message]
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
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=87cy45p934.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.