From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/2] more sampling fun 1
Date: Thu, 20 Feb 2020 11:07:45 +0100 [thread overview]
Message-ID: <20200220100745.GA30404@zn.tnic> (raw)
On Thu, Feb 06, 2020 at 02:11:02PM -0800, speck for mark gross wrote:
> From: mark gross <mgross@linux.intel.com>
> Subject: [PATCH 1/2] Add capability to specify a range of steppings in the
>
> Intel has produced processors with the same CPUID family+model. Code
> may need to check the stepping when programming model specific behavior.
>
> Add an API to allow easy specification of stepping or range of steppings
> with a 16 bit bitmask.
>
> Update cpu_vuln_whitelist using this new API.
>
> I implemented this in the way I did to avoid modifying x86_cpu_id as
> that structure is an exported ABI and any change would impact user mode
> code using the structure.
>
> Signed-off-by: mark gross <mgross@linux.intel.com>
> Reviewed-by: tony luck <tony.luck@intel.com>
> ---
> arch/x86/include/asm/cpu_device_id.h | 12 ++++++++++++
> arch/x86/kernel/cpu/common.c | 28 ++++++++++++++--------------
> arch/x86/kernel/cpu/match.c | 26 ++++++++++++++++++++++++++
> 3 files changed, 52 insertions(+), 14 deletions(-)
Why isn't this sent to lkml like a normal patch?
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
--
next reply other threads:[~2020-02-20 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 10:07 Borislav Petkov [this message]
2020-02-20 10:10 ` [MODERATED] Re: [PATCH 1/2] more sampling fun 1 Andrew Cooper
2020-02-20 10:13 ` [MODERATED] " Borislav Petkov
2020-02-20 11:00 ` [MODERATED] " Andrew Cooper
2020-02-20 12:39 ` Greg KH
2020-02-20 17:53 ` mark gross
2020-02-20 18:26 ` Borislav Petkov
2020-02-20 19:24 ` mark gross
2020-02-21 22:12 ` mark gross
[not found] <c79feecdb14c62e3dd8f2680bc68292f99882aeb.158215=?utf-8?q?2322?= .git.mgross@linux.intel.com>
2020-02-20 19:08 ` Ben Hutchings
2020-02-21 22:10 ` mark gross
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=20200220100745.GA30404@zn.tnic \
--to=bp@suse.de \
--cc=speck@linutronix.de \
/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 NNTP newsgroup(s).