From: Tao Su <tao1.su@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, zhao1.liu@intel.com, xiaoyao.li@intel.com
Subject: Re: [PATCH v2 0/8] Add AVX10.1 CPUID support and GraniteRapids-v2 model
Date: Wed, 30 Oct 2024 11:18:30 +0800 [thread overview]
Message-ID: <ZyGlhjFULPac5hpi@linux.bj.intel.com> (raw)
In-Reply-To: <20241029151858.550269-1-pbonzini@redhat.com>
On Tue, Oct 29, 2024 at 04:18:50PM +0100, Paolo Bonzini wrote:
> Most of the patches here are from Tao Su's v1. The main issue in his
> version were two:
>
> - overlooking kvm_cpu_xsave_init(), which currently looks at ExtSaveArea.
> This would get a bit ugly for extended save states that are enabled
> by both AVX512 and AVX10. Patches 1-2 change kvm_cpu_xsave_init()
> to look at ExtSaveArea's size field instead of testing features.
>
> - downgrading silently to KVM reported value if the avx10_version property
> is >= kvm reported value. Xiaoyao Li suggested basing this on
> cpu->check_cpuid and cpu->enforce_cpuid. Also, the check must accept
> any accelerator and not just KVM. I moved the check to
> x86_cpu_filter_features in patch 4.
>
> I don't have a Granite Rapids machine, so please test! :)
I test it on Granite Rapids and all meet expection with my minor changes on
patch4 :)
>
> Paolo
>
> Paolo Bonzini (3):
> target/i386: cpu: set correct supported XCR0 features for TCG
> target/i386: do not rely on ExtSaveArea for accelerator-supported XCR0 bits
> target/i386: return bool from x86_cpu_filter_features
>
> Tao Su (5):
> target/i386: add AVX10 feature and AVX10 version property
> target/i386: add CPUID.24 features for AVX10
> target/i386: Add feature dependencies for AVX10
> target/i386: Add AVX512 state when AVX10 is supported
> target/i386: Introduce GraniteRapids-v2 model
>
> target/i386/cpu.h | 16 ++++
> target/i386/cpu.c | 175 ++++++++++++++++++++++++++++++++++----
> target/i386/kvm/kvm-cpu.c | 8 --
> target/i386/kvm/kvm.c | 3 +-
> 4 files changed, 175 insertions(+), 27 deletions(-)
>
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-10-30 3:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 15:18 [PATCH v2 0/8] Add AVX10.1 CPUID support and GraniteRapids-v2 model Paolo Bonzini
2024-10-29 15:18 ` [PATCH 1/8] target/i386: cpu: set correct supported XCR0 features for TCG Paolo Bonzini
2024-10-30 2:56 ` Zhao Liu
2024-10-29 15:18 ` [PATCH 2/8] target/i386: do not rely on ExtSaveArea for accelerator-supported XCR0 bits Paolo Bonzini
2024-10-30 3:50 ` Zhao Liu
2024-10-29 15:18 ` [PATCH 3/8] target/i386: return bool from x86_cpu_filter_features Paolo Bonzini
2024-10-30 5:19 ` Zhao Liu
2024-10-29 15:18 ` [PATCH 4/8] target/i386: add AVX10 feature and AVX10 version property Paolo Bonzini
2024-10-30 3:05 ` Tao Su
2024-10-30 8:09 ` Zhao Liu
2024-10-30 8:44 ` Zhao Liu
2024-10-30 9:37 ` Tao Su
2024-10-30 13:21 ` Zhao Liu
2024-10-30 14:05 ` Tao Su
2024-10-30 15:55 ` Zhao Liu
2024-10-31 4:39 ` Tao Su
2024-10-31 5:52 ` Xiaoyao Li
2024-10-31 6:07 ` Tao Su
2024-10-31 7:12 ` Zhao Liu
2024-10-31 7:18 ` Zhao Liu
2024-10-31 7:19 ` Tao Su
2024-10-29 15:18 ` [PATCH 5/8] target/i386: add CPUID.24 features for AVX10 Paolo Bonzini
2024-10-30 8:50 ` Zhao Liu
2024-10-29 15:18 ` [PATCH 6/8] target/i386: Add feature dependencies " Paolo Bonzini
2024-10-29 15:18 ` [PATCH 7/8] target/i386: Add AVX512 state when AVX10 is supported Paolo Bonzini
2024-10-29 20:11 ` Paolo Bonzini
2024-10-30 8:54 ` Zhao Liu
2024-10-29 15:18 ` [PATCH 8/8] target/i386: Introduce GraniteRapids-v2 model Paolo Bonzini
2024-10-30 3:18 ` Tao Su [this message]
2024-10-30 8:35 ` [PATCH v2 0/8] Add AVX10.1 CPUID support and " Paolo Bonzini
2024-10-30 8:52 ` Tao Su
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=ZyGlhjFULPac5hpi@linux.bj.intel.com \
--to=tao1.su@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoyao.li@intel.com \
--cc=zhao1.liu@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).