From: Borislav Petkov <bp@alien8.de>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, H Peter Anvin <hpa@zytor.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [RFC PATCH] x86/cpufeatures: Enumerate new AVX512 bfloat16 instructions
Date: Mon, 10 Jun 2019 21:20:26 +0200 [thread overview]
Message-ID: <20190610192026.GI5488@zn.tnic> (raw)
In-Reply-To: <1560186158-174788-1-git-send-email-fenghua.yu@intel.com>
On Mon, Jun 10, 2019 at 10:02:38AM -0700, Fenghua Yu wrote:
> AVX512 Vector Neural Network Instructions (VNNI) in Intel Deep Learning
> Boost support bfloat16 format (BF16). BF16 is a short version of FP32 and
> has several advantages over FP16. BF16 offers more than enough range for
> deep learning training tasks and doesn't need to handle hardware exception
> as this is a performance optimization. FP32 accumulation after the
> multiply is essential to achieve sufficient numerical behavior on an
> application level.
>
> AVX512 bfloat16 instructions can be enumerated by:
> CPUID.(EAX=7,ECX=1):EAX[bit 5] AVX512_BF16
>
> Detailed information of the CPUID bit and AVX512 bfloat16 instructions
> can be found in the latest Intel Architecture Instruction Set Extensions
> and Future Features Programming Reference.
>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> ---
>
> Since split lock feature (to-be-upstreamed) occupies the last bit
> of word 7, need to create a new word 19 to host AVX512_BF16 and other
> future features.
Is CPUID.(EAX=7,ECX=1):EAX going to contain only feature bits? If so,
just make it a proper feature word instead of a linux-specific one.
Also, while on the subject, you can recycle word 11
/* Intel-defined CPU QoS Sub-leaf, CPUID level 0x0000000F:0 (EDX), word 11 */
#define X86_FEATURE_CQM_LLC (11*32+ 1) /* LLC QoS if 1 */
and move it to scattered as it is a complete waste. Word 12 too, for
that matter. But do that in separate patches.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-06-10 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 17:02 [RFC PATCH] x86/cpufeatures: Enumerate new AVX512 bfloat16 instructions Fenghua Yu
2019-06-10 19:20 ` Borislav Petkov [this message]
2019-06-11 18:19 ` Fenghua Yu
2019-06-11 19:47 ` Borislav Petkov
2019-06-11 22:28 ` Fenghua Yu
2019-06-12 3:29 ` Yu, Fenghua
2019-06-12 3:59 ` Borislav Petkov
2019-06-12 17:41 ` Fenghua Yu
2019-06-12 3:32 ` Fenghua Yu
2019-06-12 4:02 ` Borislav Petkov
2019-06-12 14:10 ` Sean Christopherson
2019-06-12 17:04 ` Fenghua Yu
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=20190610192026.GI5488@zn.tnic \
--to=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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