From: Ingo Molnar <mingo@kernel.org>
To: "Luc, Piotr" <Piotr.Luc@intel.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"brgerst@gmail.com" <brgerst@gmail.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"luto@kernel.org" <luto@kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"Hansen, Dave" <dave.hansen@intel.com>,
"dvlasenk@redhat.com" <dvlasenk@redhat.com>
Subject: Re: [v2] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features.
Date: Tue, 18 Oct 2016 15:08:18 +0200 [thread overview]
Message-ID: <20161018130818.GA25251@gmail.com> (raw)
In-Reply-To: <1476795301.10038.4.camel@intel.com>
* Luc, Piotr <Piotr.Luc@intel.com> wrote:
> On Mon, 2016-10-17 at 17:03 +0200, Piotr Luc wrote:
> > v2: Initialize new bits in the scattered group. Add
>
> The commit message is obviously broken. Sorry for that.
> I will resend with fixed message.
In the v3 patchlog please also please describe to what extent new instructions are
enabled by the patch when run on real hardware (or on a simulator).
I.e. can user-space run those new instructions, while it couldn't before - or is
the patch purely for /proc/cpuinfo enumeration?
I.e. a comprehensive before/after comparison.
Thanks,
Ingo
next prev parent reply other threads:[~2016-10-18 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 17:57 [PATCH] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features 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
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 [this message]
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=20161018130818.GA25251@gmail.com \
--to=mingo@kernel.org \
--cc=Piotr.Luc@intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@intel.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.