public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu_debug.c prepare report if files are inappropriate or CPU is not supported
Date: Wed, 15 Apr 2009 11:04:25 +0530	[thread overview]
Message-ID: <1239773665.15436.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20090414191622.GA797@elte.hu>

On Tue, 2009-04-14 at 21:16 +0200, Ingo Molnar wrote:
> * Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> 
> > > > Do you still think that boot_cpu_data.x86_vendor is better option in
> > > > case for multiple CPUs.
> > > 
> > > yes. Assymetric SMP never really happened on x86.
> > 
> > It did but not between vendors. You can get away with a vendor 
> > assumption but cpu type (mixed 486SX/DX, PII/PIII/Celeron) mixed 
> > steppings and mixed speeds do occur. We've never supported the 
> > mixed 486SX cases but the PII/PIII cases work (or at least 
> > worked).
> 
> yeah - but look at the specific purpose here: we are deciding 
> whether to print out state information related to major CPU 
> features. Mixed steppings/speeds might happen, mixed apic / 
> non-lapic not really.
> 

We are trying to debug each CPU, so we should also collect information
from each CPU.

Just reading information from boot CPU and display information for all
CPU is not correct. If we are getting information from boot CPU then we
only need to show information for boot CPU and ignore others.

I am trying to adding more features which will be unique for each
CPU/core.

So it seems current model is correct where I am collecting information
for each CPU and printing information for each CPU.

Thanks,

--
JSR


  reply	other threads:[~2009-04-15  5:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 16:07 [PATCH -tip] x86: cpu_debug.c prepare report if files are inappropriate or CPU is not supported Jaswinder Singh Rajput
2009-04-14 16:50 ` Ingo Molnar
2009-04-14 17:01   ` Jaswinder Singh Rajput
2009-04-14 18:42     ` Ingo Molnar
2009-04-14 18:54       ` Jaswinder Singh Rajput
2009-04-14 19:02       ` Alan Cox
2009-04-14 19:16         ` Ingo Molnar
2009-04-15  5:34           ` Jaswinder Singh Rajput [this message]
2009-04-15 10:17             ` Ingo Molnar
2009-06-05 17:57               ` Jaswinder Singh Rajput
2009-06-06 10:21                 ` Jaswinder Singh Rajput
2009-06-07 10:20                 ` Ingo Molnar
2009-06-07 12:16                 ` [tip:x86/cpu] x86: cpu_debug: Remove model information to reduce encoding-decoding tip-bot for 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=1239773665.15436.9.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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