public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Andi Kleen <andi@firstfloor.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86: Report Intel platform_id in /proc/cpuinfo
Date: Thu, 2 Jun 2016 15:54:40 -0700	[thread overview]
Message-ID: <20160602225439.GF13997@two.firstfloor.org> (raw)
In-Reply-To: <20160602182707.GA15431@khazad-dum.debian.net>

On Thu, Jun 02, 2016 at 03:27:07PM -0300, Henrique de Moraes Holschuh wrote:
> On Tue, 31 May 2016, Andi Kleen wrote:
> > We have a need to distinguish systems based on their platform ID.
> > For example this is useful to distinguish systems with L4 cache
> > versus ones without.
> > 
> > There is a 5 bit identifier (also called processor flags) in
> 
> There is a 3 bit identifier...

Thanks.

> > diff --git a/arch/x86/kernel/cpu/microcode/intel.c b/arch/x86/kernel/cpu/microcode/intel.c
> > index ee81c54..6244a88 100644
> > --- a/arch/x86/kernel/cpu/microcode/intel.c
> > +++ b/arch/x86/kernel/cpu/microcode/intel.c
> > @@ -812,6 +812,7 @@ static int collect_cpu_info(int cpu_num, struct cpu_signature *csig)
> >  		/* get processor flags from MSR 0x17 */
> >  		rdmsr(MSR_IA32_PLATFORM_ID, val[0], val[1]);
> >  		csig->pf = 1 << ((val[1] >> 18) & 7);
> > +		cpu_data(cpu_num).platform_id = (val[1] >> 18) & 7;
> 
> See below.  It might be better to have "cpu_data(cpu_num).platform_id =
> csig->pf" instead.

Ok.

> 
> > diff --git a/arch/x86/kernel/cpu/proc.c b/arch/x86/kernel/cpu/proc.c
> > index 18ca99f..1c4e4f5 100644
> > --- a/arch/x86/kernel/cpu/proc.c
> > +++ b/arch/x86/kernel/cpu/proc.c
> > @@ -76,6 +76,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)
> >  		seq_puts(m, "stepping\t: unknown\n");
> >  	if (c->microcode)
> >  		seq_printf(m, "microcode\t: 0x%x\n", c->microcode);
> > +	if (c->platform_id)
> > +		seq_printf(m, "platform_id\t: %d\n", c->platform_id);
> 
> platform_id can meaningfully be zero on Intel, and in fact it often is (just
> look for output from the microcode driver that logs pf=0x1).  In those
> processors, (MSR(17) >> 18 & 7) is zero, and csig->pf is 1.
> 
> May I humbly suggest using the mask "(1 << value)" notation for platform_id
> as used by the microcode driver?  We already do it for csig->pf, and it has
> the advantage that mask notation will never be zero (so, the field is always
> non-zero where relevant).

That would be confusing because the value is used in some documents.
I would prefer to match them.

> 
> Alterntively, the patch could be changed to always print platform_id on
> Intel processors, instead of just printing it out when it is non-zero.

What I can do is to add an extra flag and print it when the flag is set,
even if it is zero.

Thanks for the review.

-Andi

  reply	other threads:[~2016-06-02 22:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 21:24 [PATCH] x86: Report Intel platform_id in /proc/cpuinfo Andi Kleen
2016-06-02 18:27 ` Henrique de Moraes Holschuh
2016-06-02 22:54   ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-18 23:23 Andi Kleen
2016-09-23 18:02 Andi Kleen
2016-09-23  0:48 Andi Kleen
2016-09-23  8:12 ` Thomas Gleixner
2016-06-02 15:51 Andi Kleen
2016-06-21 16:05 ` Andi Kleen
2016-06-22 11:54   ` Henrique de Moraes Holschuh
2016-09-21 12:30 ` Thomas Gleixner
2016-05-05 10:12 Andi Kleen
2016-05-06 12:42 ` Henrique de Moraes Holschuh

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=20160602225439.GF13997@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox