mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hpa@zytor.com
To: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
	peterz@infradead.org, tglx@linutronix.de, dave.hansen@intel.com,
	torvalds@linux-foundation.org, piotr.luc@intel.com,
	luto@kernel.org, brgerst@gmail.com, linux-kernel@vger.kernel.org,
	dvlasenk@redhat.com, jpoimboe@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features
Date: Sun, 16 Oct 2016 09:02:51 -0700	[thread overview]
Message-ID: <A31EBDF6-87E7-4857-9E93-CD471BA7C5C0@zytor.com> (raw)
In-Reply-To: <20161016142233.xuqrahty6gcwq7en@pd.tnic>

On October 16, 2016 7:22:33 AM PDT, Borislav Petkov <bp@alien8.de> wrote:
>On Sun, Oct 16, 2016 at 04:21:49AM -0700, tip-bot for Piotr Luc wrote:
>> Commit-ID:  a518dcc82b6162009c8ca3d169fe61c81536ff17
>> Gitweb:    
>http://git.kernel.org/tip/a518dcc82b6162009c8ca3d169fe61c81536ff17
>> Author:     Piotr Luc <piotr.luc@intel.com>
>> AuthorDate: Wed, 12 Oct 2016 19:57:31 +0200
>> Committer:  Ingo Molnar <mingo@kernel.org>
>> CommitDate: Sun, 16 Oct 2016 11:32:11 +0200
>> 
>> x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features
>> 
>> AVX512_4VNNIW  - Vector instructions for deep learning enhanced word
>> variable precision.
>> AVX512_4FMAPS - Vector instructions for deep learning floating-point
>> single precision.
>> 
>> The new instructions are to be used in future Intel Xeon & Xeon Phi
>> processors.
>> 
>> The spec can be found in Intel Software Developer Manual or in
>> Instruction Set Extensions Programming Reference. See
>>
>https://software.intel.com/sites/default/files/managed/69/78/319433-025.pdf.
>> 
>> Signed-off-by: Piotr Luc <piotr.luc@intel.com>
>> Reviewed-by: Dave Hansen <dave.hansen@intel.com>
>> Cc: Andy Lutomirski <luto@kernel.org>
>> Cc: Borislav Petkov <bp@alien8.de>
>> Cc: Brian Gerst <brgerst@gmail.com>
>> Cc: Denys Vlasenko <dvlasenk@redhat.com>
>> Cc: H. Peter Anvin <hpa@zytor.com>
>> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
>> Cc: Linus Torvalds <torvalds@linux-foundation.org>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Link:
>http://lkml.kernel.org/r/20161012175731.29619-1-piotr.luc@intel.com
>> Signed-off-by: Ingo Molnar <mingo@kernel.org>
>
>...
>
>> diff --git a/arch/x86/include/asm/cpufeatures.h
>b/arch/x86/include/asm/cpufeatures.h
>> index 1188bc8..6697b75 100644
>> --- a/arch/x86/include/asm/cpufeatures.h
>> +++ b/arch/x86/include/asm/cpufeatures.h
>> @@ -12,7 +12,7 @@
>>  /*
>>   * Defines x86 CPU feature bits
>>   */
>> -#define NCAPINTS	18	/* N 32-bit words worth of info */
>> +#define NCAPINTS	19	/* N 32-bit words worth of info */
>>  #define NBUGINTS	1	/* N 32-bit bug flags */
>>  
>>  /*
>> @@ -285,6 +285,10 @@
>>  #define X86_FEATURE_SUCCOR	(17*32+1) /* Uncorrectable error
>containment and recovery */
>>  #define X86_FEATURE_SMCA	(17*32+3) /* Scalable MCA */
>>  
>> +/* Intel-defined CPU features, CPUID level 0x00000007:0 (edx), word
>18 */
>> +#define X86_FEATURE_AVX512_4VNNIW  (18*32+2) /* AVX-512 Neural
>Network Instructions */
>> +#define X86_FEATURE_AVX512_4FMAPS  (18*32+3) /* AVX-512 Multiply
>Accumulation Single precision */
>
>This is getting ridiculous: we keep adding new leafs to
>->x86_capability, thus bloating cpuinfo_x86 but then it is not even
>worth it - this patch defines only two bits.
>
>I know, I know, it is a CPUID leaf of features, we will need them,
>yadda
>yadda but until we do, I'd suggest these all new feature bits to to
>init_scattered_cpuid_features() and be carved out to a leaf of their
>own *only* when we really, actually add them and fill up that leaf.
>Otherwise, we have one fat and sparse x86_capability array.

No, please.  That would be worse than the disease.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2016-10-16 16:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 17:57 [PATCH] " Piotr Luc
2016-10-16 11:21 ` [tip:x86/urgent] " tip-bot for Piotr Luc
2016-10-16 14:22   ` Borislav Petkov
2016-10-16 16:02     ` hpa [this message]
2016-10-16 16:35       ` Borislav Petkov
2016-10-16 18:42         ` hpa
2016-10-16 22:42           ` Borislav Petkov
2016-10-17  9:55             ` Luc, Piotr
2016-10-17  7:55     ` Thomas Gleixner
2016-10-17  8:20       ` Luc, Piotr
2016-10-17  8:47         ` Ingo Molnar
2016-10-17  9:53           ` Luc, Piotr
2016-10-17  9:54             ` Thomas Gleixner
2016-10-17 15:03               ` [PATCH v2] " Piotr Luc
2016-10-18 13:00                 ` [v2] " Luc, Piotr
2016-10-18 13:08                   ` Ingo Molnar
2016-10-18 15:01                     ` [PATCH v3] " Piotr Luc
2016-10-19 15:43                       ` [tip:x86/urgent] " tip-bot for Piotr Luc

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=A31EBDF6-87E7-4857-9E93-CD471BA7C5C0@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=dvlasenk@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=piotr.luc@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®