From: Ben Hutchings <ben@decadent.org.uk>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/2] more sampling fun 1
Date: Thu, 20 Feb 2020 19:08:45 +0000 [thread overview]
Message-ID: <2847e79bd70becdc174a4bd890c1be6b37247e43.camel@decadent.org.uk> (raw)
In-Reply-To: <c79feecdb14c62e3dd8f2680bc68292f99882aeb.158215=?utf-8?q?2322?= .git.mgross@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
On Thu, 2020-02-06 at 14:11 -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
[...]
> --- a/arch/x86/include/asm/cpu_device_id.h
> +++ b/arch/x86/include/asm/cpu_device_id.h
> @@ -35,7 +35,19 @@ struct x86_cpu_desc {
> .x86_microcode_rev = (revision), \
> }
>
> +/*
> + * Match a range of steppings
> + */
> +
> +struct x86_cpu_id_ext {
> + struct x86_cpu_id id;
> + __u16 steppings; /* bit map of steppings to match against */
> +};
> +
> +#define X86_STEPPING_ANY 0
[...]
Minor point, but wouldn't it make more sense to define X86_STEPPING_ANY
as GENMASK(15, 0)? Then it's no longer a special case.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2020-02-20 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c79feecdb14c62e3dd8f2680bc68292f99882aeb.158215=?utf-8?q?2322?= .git.mgross@linux.intel.com>
2020-02-20 19:08 ` Ben Hutchings [this message]
2020-02-21 22:10 ` mark gross
2020-02-20 10:07 Borislav Petkov
2020-02-20 10:10 ` 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
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=2847e79bd70becdc174a4bd890c1be6b37247e43.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=speck@linutronix.de \
--subject='[MODERATED] Re: [PATCH 1/2] more sampling fun 1' \
/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
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).