From: Zhao Liu <zhao1.liu@intel.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: Sergio Lopez <slp@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
imammedo@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v5] hw/i386/cpu: remove default_cpu_version and simplify
Date: Thu, 23 Jan 2025 20:35:18 +0800 [thread overview]
Message-ID: <Z5I3hkmDtb6thaK3@intel.com> (raw)
In-Reply-To: <20250123115613.1537173-1-anisinha@redhat.com>
> hw/i386/microvm.c | 3 +-
> hw/i386/pc.c | 14 +++++++++
> hw/i386/pc_piix.c | 6 ++--
> hw/i386/pc_q35.c | 6 ++--
> hw/i386/x86-common.c | 4 +--
> include/hw/i386/pc.h | 7 +++--
> include/hw/i386/x86.h | 2 +-
> target/i386/cpu.c | 69 ++++++++++++++++++++++---------------------
> target/i386/cpu.h | 21 +++----------
> 9 files changed, 67 insertions(+), 65 deletions(-)
>
> changelog:
> v2: explain in commit log why use of CPU_VERSION_LATEST for machines
> is problematic.
> v3: fix a bug that broke the pipeline
> https://gitlab.com/mstredhat/qemu/-/pipelines/1626171267
> when cpu versions are explicitly specified in the command line,
> respect that and do not enforce legacy (unversioned) cpu logic.
> The pipeline is green now with the fix:
> https://gitlab.com/anisinha/qemu/-/pipelines/1626783632
> v4: made changes as per Zhao's suggestions.
> Pipeline passes https://gitlab.com/anisinha/qemu/-/pipelines/1635829877
> v5: adjustment of pc_init_cpus() declaration as per Zhao's suggestion. This
> simplifies things and also passes compilation.
> CI still passes https://gitlab.com/anisinha/qemu/-/pipelines/1637657451
v5 is fine for me, so
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
Let's see if anyone else has comments.
next prev parent reply other threads:[~2025-01-23 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 11:56 [PATCH v5] hw/i386/cpu: remove default_cpu_version and simplify Ani Sinha
2025-01-23 12:35 ` Zhao Liu [this message]
2025-01-23 14:22 ` Igor Mammedov
2025-01-25 3:28 ` Ani Sinha
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=Z5I3hkmDtb6thaK3@intel.com \
--to=zhao1.liu@intel.com \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=slp@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.