From: Borislav Petkov <bp@alien8.de>
To: Piotr Luc <piotr.luc@intel.com>
Cc: x86@kernel.org, "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] x86/cpufeature: Add AVX512_VPOPCNTDQ feature
Date: Mon, 16 Jan 2017 18:23:48 +0100 [thread overview]
Message-ID: <20170116172348.e67p3c6fvyepsq5r@pd.tnic> (raw)
In-Reply-To: <20170110173403.6010-2-piotr.luc@intel.com>
On Tue, Jan 10, 2017 at 06:34:02PM +0100, Piotr Luc wrote:
> Vector population count instructions for dwords and qwords are to be
> used in future Intel Xeon & Xeon Phi processors. The bit 14 of
> CPUID[level:0x07, ECX] indicates that the new instructions are
> supported by a processor.
>
> The spec can be found in the Intel Software Developer Manual (SDM)
> or in the Instruction Set Extensions Programming Reference (ISE).
>
> Define new feature flag to enumerate the new instructions set in
> /proc/cpuinfo according to new CPUID bit.
> Clear the feature bit in case xsave is disabled.
>
> Signed-off-by: Piotr Luc <piotr.luc@intel.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: x86@kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
Reviewed-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-01-16 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:34 [PATCH v1 0/2] vpopcntdq support Piotr Luc
2017-01-10 17:34 ` [PATCH v1 1/2] x86/cpufeature: Add AVX512_VPOPCNTDQ feature Piotr Luc
2017-01-16 17:23 ` Borislav Petkov [this message]
2017-01-16 19:43 ` [tip:x86/cpufeature] " tip-bot for Piotr Luc
2017-01-10 17:34 ` [PATCH v1 2/2] kvm: x86: Expose Intel VPOPCNTDQ feature to guest Piotr Luc
2017-01-20 18:00 ` Radim Krčmář
2017-01-10 17:39 ` [PATCH v1 0/2] vpopcntdq support Paolo Bonzini
2017-01-11 13:02 ` Luc, Piotr
2017-01-16 19:43 ` Thomas Gleixner
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=20170116172348.e67p3c6fvyepsq5r@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=piotr.luc@intel.com \
--cc=rkrcmar@redhat.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
all inboxes | Powered by JetHome®