All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 08/11] target/arm/cpu: Expose x-mig-hidden-regs and x-mig-safe-missing-regs properties
Date: Tue, 25 Nov 2025 18:17:25 +0100	[thread overview]
Message-ID: <87bjkqowuy.fsf@redhat.com> (raw)
In-Reply-To: <20251125100859.506228-9-eric.auger@redhat.com>

On Tue, Nov 25 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 garantee cross kernel migration.

s/garantee/enable/ ?

>
> 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
> been hidden for machine types older than 10.1. The second one means

s/been/be/

> that along with 10.1 machine type we may receive in the incoming
> migration stream, 3 registers that are unknown on destination.
>
> Obvioulsy, using the reg index as defined in

s/Obvioulsy/Obviously/

> linux/Documentation/virt/kvm/api.rst is not user friendly. However
> those options, prefixed with "x-" are supposed to be used
> rarely by people who know the details.

"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." ?

I'm not sure whether the "x-" prefix is the right choice for "do not use
unless you really know what you're doing", but OTOH, it's the prefix we
have...

>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> ---
>  target/arm/cpu.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/target/arm/cpu.c b/target/arm/cpu.c
> index 066746d76f..c41774cb4c 100644
> --- a/target/arm/cpu.c
> +++ b/target/arm/cpu.c
> @@ -2248,6 +2248,11 @@ static const Property arm_cpu_properties[] = {
>      DEFINE_PROP_BOOL("backcompat-cntfrq", ARMCPU, backcompat_cntfrq, false),
>      DEFINE_PROP_BOOL("backcompat-pauth-default-use-qarma5", ARMCPU,
>                        backcompat_pauth_default_use_qarma5, false),
> +    DEFINE_PROP_ARRAY("x-mig-hidden-regs", ARMCPU,
> +                      nr_hidden_regs, hidden_regs, qdev_prop_uint64, uint64_t),
> +    DEFINE_PROP_ARRAY("x-mig-safe-missing-regs", ARMCPU,
> +                      nr_mig_safe_missing_regs, mig_safe_missing_regs,
> +                      qdev_prop_uint64, uint64_t),
>  };
>  
>  static const gchar *arm_gdb_arch_name(CPUState *cs)



  reply	other threads:[~2025-11-25 17:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 10:07 [PATCH v3 00/11] Mitigation of "failed to load cpu:cpreg_vmstate_array_len" migration failures Eric Auger
2025-11-25 10:07 ` [PATCH v3 01/11] hw/arm/virt: Rename arm_virtio_compat into arm_virt_compat_defaults Eric Auger
2025-11-25 16:42   ` Cornelia Huck
2025-11-26 15:30   ` Sebastian Ott
2025-11-26 16:29   ` Sebastian Ott
2025-11-25 10:07 ` [PATCH v3 02/11] target/arm/machine: Improve traces on register mismatch during migration Eric Auger
2025-11-25 10:07 ` [PATCH v3 03/11] target/arm/cpu: Allow registers to be hidden Eric Auger
2025-11-25 17:04   ` Cornelia Huck
2025-12-22 13:17     ` Eric Auger
2025-12-22 13:21       ` Eric Auger
2025-11-26 16:28   ` Sebastian Ott
2025-11-25 10:07 ` [PATCH v3 04/11] target/arm/machine: Allow extra regs in the incoming stream Eric Auger
2025-11-25 17:07   ` Cornelia Huck
2025-11-25 10:07 ` [PATCH v3 05/11] target/arm/helper: Skip hidden registers Eric Auger
2025-11-25 10:07 ` [PATCH v3 06/11] kvm-all: Add the capability to blacklist some KVM regs Eric Auger
2025-11-25 17:09   ` Cornelia Huck
2025-11-26 16:42   ` Sebastian Ott
2025-11-25 10:07 ` [PATCH v3 07/11] target/arm/cpu: Implement hide_reg callback() Eric Auger
2025-11-25 17:10   ` Cornelia Huck
2025-11-26 16:55   ` Sebastian Ott
2025-11-25 10:07 ` [PATCH v3 08/11] target/arm/cpu: Expose x-mig-hidden-regs and x-mig-safe-missing-regs properties Eric Auger
2025-11-25 17:17   ` Cornelia Huck [this message]
2025-11-25 10:07 ` [PATCH v3 09/11] hw/arm/virt: Declare AArch32 DBGDTRTX as safe to ignore in incoming stream Eric Auger
2025-11-25 17:20   ` Cornelia Huck
2025-11-25 10:07 ` [PATCH v3 10/11] Revert "target/arm: Reinstate bogus AArch32 DBGDTRTX register for migration compat" Eric Auger
2025-11-25 10:08 ` [PATCH v3 11/11] hw/arm/virt: [DO NOT UPSTREAM] Enforce compatibility with older kernels 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=87bjkqowuy.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.