From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: V6: [PATCH] x86: Install <sys/platform/x86.h> [BZ #26124]
Date: Mon, 29 Jun 2020 17:29:42 -0700 [thread overview]
Message-ID: <CAMe9rOqQTXW9Ged0QuRy6+y10OjuJTeo0nHiNwOYRhAUsZii6Q@mail.gmail.com> (raw)
In-Reply-To: <87k0zpvmuj.fsf@oldenburg2.str.redhat.com>
On Mon, Jun 29, 2020 at 9:49 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> >> One thing I still dislike (sorry) is the asymmetry between the usable
> >> and feature checks. For example, why is there are usability check for
> >> VAES, but not for AES? I believe the reason is that VAES depends on
> >> AVX/AVX2, but AES only depends on SSE2. But even that suggests to me
> >> that for 32-bit, there should be a usable gate for that (which is false
> >> if SSE2 support has been masked).
> >
> > CPU with AES must have SSE2. I don't think we need explicit check
> > for SSE2.
>
> But SSE2 needs operating system support, so we get the usable vs
> available distinction this way. I think.
>
We don't check if OS supports SSE2.
--
H.J.
next prev parent reply other threads:[~2020-06-30 0:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 19:31 [PATCH] x86: Install <cpu-features.h> " H.J. Lu
2020-06-17 20:54 ` Joseph Myers
2020-06-18 0:08 ` [PATCH] x86: Install <sys/platform/x86.h> " H.J. Lu
2020-06-18 8:45 ` Florian Weimer
2020-06-18 16:14 ` V2: " H.J. Lu
2020-06-22 9:09 ` Florian Weimer
2020-06-22 20:25 ` V3: " H.J. Lu
2020-06-22 20:41 ` Florian Weimer
2020-06-22 20:53 ` H.J. Lu
2020-06-22 21:14 ` Florian Weimer
2020-06-22 22:18 ` H.J. Lu
2020-06-22 23:14 ` V4: " H.J. Lu
2020-06-24 14:33 ` Florian Weimer
2020-06-24 20:04 ` Adhemerval Zanella
2020-06-24 21:10 ` H.J. Lu
2020-06-25 7:33 ` Florian Weimer
2020-06-25 12:30 ` V5: " H.J. Lu
2020-06-25 13:20 ` V6: " H.J. Lu
2020-06-26 12:52 ` H.J. Lu
2020-06-26 13:20 ` Florian Weimer
2020-06-26 13:44 ` H.J. Lu
2020-06-29 16:13 ` Florian Weimer
2020-06-29 16:44 ` H.J. Lu
2020-06-29 16:49 ` Florian Weimer
2020-06-30 0:29 ` H.J. Lu [this message]
2020-06-30 9:46 ` Florian Weimer
2020-06-30 12:19 ` H.J. Lu
2020-06-24 22:07 ` V4: " Joseph Myers
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=CAMe9rOqQTXW9Ged0QuRy6+y10OjuJTeo0nHiNwOYRhAUsZii6Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).