From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH 0/8] x86: support AVX10.1
Date: Thu, 11 Jan 2024 16:15:42 +0100 [thread overview]
Message-ID: <298db76f-d0ee-4d47-931f-1baa1a7546cf@suse.com> (raw)
AVX10.1 is just a re-branding of certain AVX512 (sub)features, i.e.
adds no new instructions. Therefore it's mostly relaxation that needs
doing, plus dealing with the 256-bit-only case that AVX512 itself
does not allow for. Luckily an unnecessary restriction on the mask
register insns was taken out again, simplifying the actual emulator
adjustments quite a bit.
While it probably can be rebased ahead, the series in this form
depends on the previously submitted
[PATCH 0/4] x86emul: support further AVX extensions
[PATCH v4 0/8] x86emul: misc additions
[PATCH v4 0/3] x86/CPUID: leaf pruning
I've tried to be very careful in rebasing ahead of AMX and KeyLocker
patches I've been carrying, but almost all testing I've done is with
all of those collectively in place.
1: x86/CPUID: enable AVX10 leaf
2: x86emul/test: rename "cp"
3: x86emul: introduce a struct cpu_policy * local in x86_emulate()
4: x86emul: support AVX10.1
5: x86emul/test: use simd_check_avx512*() in main()
6: x86emul/test: drop cpu_has_avx512vl
7: x86emul: AVX10.1 testing
8: x86emul/test: engage AVX512VL via command line option
Jan
next reply other threads:[~2024-01-11 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 15:15 Jan Beulich [this message]
2024-01-11 15:17 ` [PATCH 1/8] x86/CPUID: enable AVX10 leaf Jan Beulich
2024-01-11 15:18 ` [PATCH 2/8] x86emul/test: rename "cp" Jan Beulich
2024-01-11 15:18 ` [PATCH 3/8] x86emul: introduce a struct cpu_policy * local in x86_emulate() Jan Beulich
2024-01-11 15:19 ` [PATCH 4/8] x86emul: support AVX10.1 Jan Beulich
2024-01-11 15:20 ` [PATCH 5/8] x86emul/test: use simd_check_avx512*() in main() Jan Beulich
2024-01-11 15:21 ` [PATCH 6/8] x86emul/test: drop cpu_has_avx512vl Jan Beulich
2024-01-11 15:21 ` [PATCH 7/8] x86emul: AVX10.1 testing Jan Beulich
2024-01-11 15:22 ` [PATCH 8/8] x86emul/test: engage AVX512VL via command line option Jan Beulich
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=298db76f-d0ee-4d47-931f-1baa1a7546cf@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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).