qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, hector.cao@canonical.com, lk@c--e.de,
	berrange@redhat.com
Subject: Re: [RFT PATCH v2 2/2] target/i386: add compatibility property for pdcm feature
Date: Fri, 26 Sep 2025 00:10:10 +0800	[thread overview]
Message-ID: <aNVpYlFmo2dXgoSF@intel.com> (raw)
In-Reply-To: <20250923104136.133875-3-pbonzini@redhat.com>

On Tue, Sep 23, 2025 at 12:41:36PM +0200, Paolo Bonzini wrote:
> Date: Tue, 23 Sep 2025 12:41:36 +0200
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: [RFT PATCH v2 2/2] target/i386: add compatibility property for
>  pdcm feature
> X-Mailer: git-send-email 2.51.0
> 
> From: Hector Cao <hector.cao@canonical.com>
> 
> The pdcm feature is supposed to be disabled when PMU is not
> available. Up until v10.1, pdcm feature is enabled even when PMU
> is off. This behavior has been fixed but this change breaks the
> migration of VMs that are run with QEMU < 10.0 and expect the pdcm
> feature to be enabled on the destination host.
> 
> This commit restores the legacy behavior for machines with version
> prior to 10.1 to allow the migration from older QEMU to QEMU 10.1.
> 
> Signed-off-by: Hector Cao <hector.cao@canonical.com>
> Link: https://lore.kernel.org/r/20250910115733.21149-3-hector.cao@canonical.com
> Fixes: e68ec298090 ("i386/cpu: Move adjustment of CPUID_EXT_PDCM before feature_dependencies[] check", 2025-06-20)
> [Move property from migration object to CPU. - Paolo]
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  target/i386/cpu.h |  6 ++++++
>  hw/i386/pc.c      |  1 +
>  target/i386/cpu.c | 15 ++++++++++++---
>  3 files changed, 19 insertions(+), 3 deletions(-)

Reviewed-by: Zhao Liu <zhao1.liu@intel.com>



  reply	other threads:[~2025-09-25 15:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 10:41 [RFT PATCH v2 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities Paolo Bonzini
2025-09-23 10:41 ` [RFT PATCH v2 1/2] target/i386: add compatibility property for arch_capabilities Paolo Bonzini
2025-09-25 16:09   ` Zhao Liu
2025-09-23 10:41 ` [RFT PATCH v2 2/2] target/i386: add compatibility property for pdcm feature Paolo Bonzini
2025-09-25 16:10   ` Zhao Liu [this message]
2025-09-25 16:17 ` [RFT PATCH v2 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities Zhao Liu
2025-09-28  9:41   ` Paolo Bonzini
2025-10-08  8:47     ` Michael Tokarev
2025-10-08 13:32   ` Michael Tokarev
2025-10-10 17:40   ` Michael Tokarev
2025-10-13  7:22     ` Zhao Liu
2025-10-13 17:22       ` Michael Tokarev
2025-10-14 10:49         ` Hector Cao
2025-10-14 13:53           ` Paolo Bonzini
2025-10-14 14:40             ` Michael Tokarev

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=aNVpYlFmo2dXgoSF@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=berrange@redhat.com \
    --cc=hector.cao@canonical.com \
    --cc=lk@c--e.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).