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, Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [RFT PATCH v2 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities
Date: Fri, 26 Sep 2025 00:17:06 +0800 [thread overview]
Message-ID: <aNVrAkx+ahn7ZRns@intel.com> (raw)
In-Reply-To: <20250923104136.133875-1-pbonzini@redhat.com>
On Tue, Sep 23, 2025 at 12:41:34PM +0200, Paolo Bonzini wrote:
> Date: Tue, 23 Sep 2025 12:41:34 +0200
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: [RFT PATCH v2 0/2] Fix cross migration issue with missing
> features: pdcm, arch-capabilities
> X-Mailer: git-send-email 2.51.0
>
> Add two compatibility properties to restore legacy behavior of machine types
> prior to QEMU 10.1. Each of them addresses the two changes to CPUID:
>
> - ARCH_CAPABILITIES should not be autoenabled when the CPU model specifies AMD
> as the vendor
>
> - specifying PDCM without PMU now causes an error, instead of being silently
> dropped in cpu_x86_cpuid.
>
> Note, I only tested this lightly.
Sorry for late.
I found the previous 2 fixes were merged into stable 10.0:
24778b1c7ee7aca9721ed4757b0e0df0c16390f7
3d26cb65c27190e57637644ecf6c96b8c3d246a3
Should stable 10.0 revert these 2 fixes, to ensure migration
compatibility?
(+Michael)
Regards,
Zhao
next prev parent reply other threads:[~2025-09-25 15:56 UTC|newest]
Thread overview: 18+ 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
2025-09-25 16:17 ` Zhao Liu [this message]
2025-09-28 9:41 ` [RFT PATCH v2 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities 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
-- strict thread matches above, loose matches on Subject: below --
2025-09-25 8:40 Hector Cao
2025-09-28 9:46 ` Paolo Bonzini
2025-09-30 8:37 Hector Cao
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=aNVrAkx+ahn7ZRns@intel.com \
--to=zhao1.liu@intel.com \
--cc=berrange@redhat.com \
--cc=hector.cao@canonical.com \
--cc=lk@c--e.de \
--cc=mjt@tls.msk.ru \
--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 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.