public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [git-pull -tip] x86: cpu_debug patches
Date: Wed, 29 Apr 2009 12:50:21 +0200	[thread overview]
Message-ID: <20090429105021.GG2373@elte.hu> (raw)
In-Reply-To: <1240977176.3028.0.camel@ht.satnam>


* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:

> On Tue, 2009-04-28 at 19:28 +0200, Ingo Molnar wrote:
> > * Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> > 
> > > @@ -850,10 +903,10 @@ static int cpu_init_cpu(void)
> > >  		cpui = &cpu_data(cpu);
> > >  		if (!cpu_has(cpui, X86_FEATURE_MSR))
> > >  			continue;
> > > -		per_cpu(cpu_model, cpu) = ((cpui->x86_vendor << 16) |
> > > -					   (cpui->x86 << 8) |
> > > -					   (cpui->x86_model));
> > > -		per_cpu(cpu_modelflag, cpu) = get_cpu_modelflag(cpu);
> > > +		per_cpu(cpu_modelflag, cpu) = get_cpu_flag(cpui);
> > > +		if (!per_cpu(cpu_modelflag, cpu))
> > > +			send_report(per_cpu(cpu_priv_count, cpu), cpui);
> > 
> > This means that if the CPU is not enumerated in the model table 
> > explicitly, we'll fall back to some really minimal output, right?
> > 
> 
> Yes.

That's a bug really: it means that for every new CPU type that comes 
around we need to update this code. I.e. precisely for those CPUs 
where we might need the most help from such a debug facility, we 
wont have much info to look at ... New CPUs generally support all 
the CPU features that are displayed here, in a compatible manner.

So that needs to be improved/changed to not be tied to such a static 
'cpu model' enumeration but instead be CPU feature flags driven. See 
all the existing cpu_has_*() tests we have.

	Ingo

  reply	other threads:[~2009-04-29 10:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20  1:15 [git-pull -tip] x86: cpu_debug patches Jaswinder Singh Rajput
2009-04-20  1:35 ` Jaswinder Singh Rajput
2009-04-20  8:50   ` Jaswinder Singh Rajput
2009-04-20 11:16     ` Ingo Molnar
2009-04-28 15:43       ` Jaswinder Singh Rajput
2009-04-28 17:28         ` Ingo Molnar
2009-04-29  3:52           ` Jaswinder Singh Rajput
2009-04-29 10:50             ` Ingo Molnar [this message]
2009-04-29 12:14               ` Jaswinder Singh Rajput
2009-04-29 12:30                 ` Ingo Molnar
2009-05-03  9:09                 ` Ingo Molnar
2009-05-06  9:57                   ` [RFC][git-pull -tip] x86: cpu_debug and cpufeature patches Jaswinder Singh Rajput
2009-05-06 12:25                     ` Ingo Molnar
2009-05-06 12:49                       ` Jaswinder Singh Rajput
2009-05-08  0:39                     ` Jaswinder Singh Rajput
2009-05-09 18:36                     ` Jaswinder Singh Rajput
2009-05-11 14:07                       ` Ingo Molnar
2009-05-19 11:57                   ` [git-pull -tip] x86: cpu_debug patches Jaswinder Singh Rajput

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=20090429105021.GG2373@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jaswinder@kernel.org \
    --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