From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Jiang, Haochen" <haochen.jiang@intel.com>,
Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 3/5] x86: support AVX10.1/512
Date: Wed, 30 Aug 2023 08:28:40 -0700 [thread overview]
Message-ID: <CAMe9rOqX27Gc0TkHAN5yhkzw7-8M4GmF2hBkbigAys9e8kEXGg@mail.gmail.com> (raw)
In-Reply-To: <194c4c39-8af0-3eac-9138-df04bc3b2f87@suse.com>
On Wed, Aug 30, 2023 at 12:48 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 30.08.2023 03:10, Jiang, Haochen wrote:
> >> I don't think we need to make AVX10 to imply AES and VPCLMULQDQ in
> >> assembler. The AES and PCLMULQDQ changes aren't needed.
> >>
> >
> > AVX10 should not imply them. However, I suppose we are talking about
> > the relation between AES/VAES and PCLMULQDQ/VPCLMULQDQ.
>
> Correct. Some change needs to be done; the question is whether as
> posted, or whether with a prereq patch adding those two connections
> (with, as said before, me intending to go the latter route unless I
> hear otherwise).
>
I agree. VAES should imply AES and VPCLMULQDQ should imply
PCLMULQDQ.
--
H.J.
next prev parent reply other threads:[~2023-08-30 15:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 12:43 [PATCH 0/5] x86: AVX10.1 (alternative attempt) Jan Beulich
2023-08-25 12:44 ` [PATCH 1/5] x86: correct source used for two non-AVX512 VEXWIG tests Jan Beulich
2023-08-25 12:45 ` [PATCH 2/5] x86: rename CpuPCLMUL Jan Beulich
2023-08-25 12:46 ` [PATCH 3/5] x86: support AVX10.1/512 Jan Beulich
2023-08-28 2:34 ` Jiang, Haochen
2023-08-28 6:45 ` Jan Beulich
2023-08-28 6:59 ` Jiang, Haochen
2023-08-28 7:09 ` Jan Beulich
2023-08-29 16:18 ` H.J. Lu
2023-08-30 1:10 ` Jiang, Haochen
2023-08-30 7:47 ` Jan Beulich
2023-08-30 15:28 ` H.J. Lu [this message]
2023-09-01 8:41 ` Jan Beulich
2023-09-01 8:52 ` Jiang, Haochen
2023-09-01 9:57 ` Jan Beulich
2023-09-05 7:04 ` Jiang, Haochen
2023-09-05 7:25 ` Jan Beulich
2023-08-25 12:47 ` [PATCH 4/5] x86: unindent most of set_cpu_arch() Jan Beulich
2023-08-25 12:47 ` [PATCH 5/5] x86: support AVX10.1 vector size restrictions Jan Beulich
2023-08-29 16:26 ` H.J. Lu
2023-08-30 7:57 ` Jan Beulich
2023-08-30 15:25 ` H.J. Lu
2023-08-30 16:16 ` Jan Beulich
2023-08-30 18:00 ` H.J. Lu
2023-08-31 5:56 ` Jiang, Haochen
2023-08-31 7:18 ` Jan Beulich
2023-09-01 6:21 ` Jiang, Haochen
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=CAMe9rOqX27Gc0TkHAN5yhkzw7-8M4GmF2hBkbigAys9e8kEXGg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=haochen.jiang@intel.com \
--cc=jbeulich@suse.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 read-only IMAP folder(s) and NNTP newsgroup(s).