From: Paolo Bonzini <pbonzini@redhat.com>
To: "Zhao Liu" <zhao1.liu@intel.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Chang S . Bae" <chang.seok.bae@intel.com>,
Zide Chen <zide.chen@intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH v2 0/9] i386/cpu: Support APX for KVM
Date: Thu, 11 Dec 2025 09:08:33 +0100 [thread overview]
Message-ID: <16e0fc49-0cdf-4e54-b692-5f58e18c747b@redhat.com> (raw)
In-Reply-To: <20251211070942.3612547-1-zhao1.liu@intel.com>
On 12/11/25 08:09, Zhao Liu wrote:
> Hi,
>
> This series adds APX (Advanced Performance Extensions) support in QEMU
> to enable APX in Guest based on KVM (RFC v1 [1]).
>
> This series is based on CET v5:
>
> https://lore.kernel.org/qemu-devel/20251211060801.3600039-1-zhao1.liu@intel.com/
>
> And you can also find the code here:
>
> https://gitlab.com/zhao.liu/qemu/-/commits/i386-all-for-dmr-v2.1-12-10-2025
>
> Compared with v1 [2], v2 adds:
> * HMP support ("print" & "info registers").
> * gdbstub support.
>
> Thanks for your review!
Great, thanks! Just one question, should the CPUID feature be "apx" or
"apxf" (and therefore CPUID_7_1_EDX_APXF)? I can fix that myself of course.
Thanks,
Paolo
>
> Overview
> ========
>
> Intel Advanced Performance Extensions (Intel APX) expands the Intel 64
> instruction set architecture with access to more registers (16
> additional general-purpose registers (GPRs) R16–R31) and adds various
> new features that improve general-purpose performance. The extensions
> are designed to provide efficient performance gains across a variety of
> workloads without significantly increasing silicon area or power
> consumption of the core.
>
> APX spec link (rev.07) is:
> https://cdrdv2.intel.com/v1/dl/getContent/861610
>
> At QEMU side, the enabling work mainly includes three parts:
>
> 1. save/restore/migrate the xstate of APX.
> * APX xstate is a user xstate, but it reuses MPX xstate area in
> un-compacted XSAVE buffer.
> * To address this, QEMU will reject both APX and MPX if their CPUID
> feature bits are set at the same (in Patch 1).
>
> 2. add related CPUIDs support in feature words.
>
> 3. debug support, including HMP & gdbstub.
>
>
> Change Log
> ==========
>
> Changes sicne v1:
> * Expend current GPR array (CPUX86State.regs) to 32 elements instead of
> a new array.
> * HMP support ("print" & "info registers").
> * gdbstub support.
>
> [1]: KVM RFC: https://lore.kernel.org/kvm/20251110180131.28264-1-chang.seok.bae@intel.com/
> [2]: QEMU APX v1: https://lore.kernel.org/qemu-devel/20251118065817.835017-1-zhao1.liu@intel.com/
>
> Thanks and Best Regards,
> Zhao
> ---
> Zhao Liu (6):
> i386/machine: Use VMSTATE_UINTTL_SUB_ARRAY for vmstate of
> CPUX86State.regs
> i386/gdbstub: Add APX support for gdbstub
> i386/cpu-dump: Dump entended GPRs for APX supported guest
> i386/monitor: Support EGPRs in hmp_print
> i386/cpu: Support APX CPUIDs
> i386/cpu: Mark APX xstate as migratable
>
> Zide Chen (3):
> i386/cpu: Add APX EGPRs into xsave area
> i386/cpu: Cache EGPRs in CPUX86State
> i386/cpu: Add APX migration support
>
> configs/targets/x86_64-softmmu.mak | 2 +-
> gdb-xml/i386-64bit-apx.xml | 26 +++++++++++
> include/migration/cpu.h | 4 ++
> target/i386/cpu-dump.c | 30 +++++++++++--
> target/i386/cpu.c | 68 ++++++++++++++++++++++++++++-
> target/i386/cpu.h | 48 +++++++++++++++++++--
> target/i386/gdbstub.c | 69 +++++++++++++++++++++++++++++-
> target/i386/machine.c | 27 +++++++++++-
> target/i386/monitor.c | 16 +++++++
> target/i386/xsave_helper.c | 16 +++++++
> 10 files changed, 293 insertions(+), 13 deletions(-)
> create mode 100644 gdb-xml/i386-64bit-apx.xml
>
next prev parent reply other threads:[~2025-12-11 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 7:09 [PATCH v2 0/9] i386/cpu: Support APX for KVM Zhao Liu
2025-12-11 7:09 ` [PATCH v2 1/9] i386/cpu: Add APX EGPRs into xsave area Zhao Liu
2025-12-11 7:09 ` [PATCH v2 2/9] i386/machine: Use VMSTATE_UINTTL_SUB_ARRAY for vmstate of CPUX86State.regs Zhao Liu
2025-12-11 7:09 ` [PATCH v2 3/9] i386/cpu: Cache EGPRs in CPUX86State Zhao Liu
2025-12-11 7:09 ` [PATCH v2 4/9] i386/gdbstub: Add APX support for gdbstub Zhao Liu
2025-12-11 7:09 ` [PATCH v2 5/9] i386/cpu-dump: Dump entended GPRs for APX supported guest Zhao Liu
2025-12-11 7:09 ` [PATCH v2 6/9] i386/monitor: Support EGPRs in hmp_print Zhao Liu
2025-12-11 7:09 ` [PATCH v2 7/9] i386/cpu: Add APX migration support Zhao Liu
2025-12-11 7:09 ` [PATCH v2 8/9] i386/cpu: Support APX CPUIDs Zhao Liu
2025-12-11 7:09 ` [PATCH v2 9/9] i386/cpu: Mark APX xstate as migratable Zhao Liu
2025-12-11 8:08 ` Paolo Bonzini [this message]
2025-12-11 9:16 ` [PATCH v2 0/9] i386/cpu: Support APX for KVM Zhao Liu
2025-12-11 9:42 ` Paolo Bonzini
2025-12-11 11:42 ` Zhao Liu
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=16e0fc49-0cdf-4e54-b692-5f58e18c747b@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=chang.seok.bae@intel.com \
--cc=farosas@suse.de \
--cc=kvm@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=xudong.hao@intel.com \
--cc=zhao1.liu@intel.com \
--cc=zide.chen@intel.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 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).