From: "zhao1.liu" <zhao1.liu@intel.com>
To: Hao Xiang <hao.xiang@linux.alibaba.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
pbonzini <pbonzini@redhat.com>, mst <mst@redhat.com>,
farosas <farosas@suse.de>, lvivier <lvivier@redhat.com>,
Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [PATCH] i386/cpu: Rename AVX10_VNNI_INT to AVX10_V1_AUX
Date: Tue, 27 Oct 2026 17:31:06 +0800 [thread overview]
Message-ID: <auBvWpwtCZm8vxwb@intel.com> (raw)
In-Reply-To: <11491981-b61f-453b-9c12-96ec85063c4a.hao.xiang@linux.alibaba.com>
Hi Xiang,
On Tue, Oct 27, 2026 at 04:30:27PM +0800, Hao Xiang wrote:
> Date: Tue, 27 Oct 2026 16:30:27 +0800
> From: Hao Xiang <hao.xiang@linux.alibaba.com>
> Subject: [PATCH] i386/cpu: Rename AVX10_VNNI_INT to AVX10_V1_AUX
> X-Mailer: [Alimail-Mailagent revision 74][W4_0.2.3][v5ForWebDing][Chrome]
>
> Rename AVX10_VNNI_INT is to AVX10_V1_AUX to match the most recent version
> of the AVX10.2 spec (revision 7.0) [*]. Intel renamed the CPUID flag to
> apply to a variety of "convert" instructions as well as VNNI instructions.
>
> The recent KVM patch has renamed AVX10_VNNI_INT to AVX10_V1_AUX. QEMU needs
> to update the CPUID macro, feature property, AVX10.2 feature model and
> Diamond Rapids CPU definition. Keep the CPUID location and bit unchanged.
>
> [*] Intel® Advanced Vector Extensions 10.2 Architecture Specification
> (rev 7.0)
>
> Signed-off-by: Hao Xiang <hao.xiang@linux.alibaba.com>
> ---
> target/i386/cpu.c | 6 +++---
> target/i386/cpu.h | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
Thanks for this patch! I posted something similar before :)
https://lore.kernel.org/qemu-devel/20260930045237.784060-1-zhao1.liu@intel.com/
(There is one additional change: I add an alias for the vnni-int bit to avoid
potential API compatibility issues.)
Regards,
Zhao
prev parent reply other threads:[~2026-10-27 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 8:30 [PATCH] i386/cpu: Rename AVX10_VNNI_INT to AVX10_V1_AUX Hao Xiang
2026-10-27 9:31 ` zhao1.liu [this message]
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=auBvWpwtCZm8vxwb@intel.com \
--to=zhao1.liu@intel.com \
--cc=farosas@suse.de \
--cc=hao.xiang@linux.alibaba.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--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.