mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Alex Chiang <achiang@hp.com>, "hpa@zytor.com" <hpa@zytor.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: add /proc/cpuinfo/physical id quirks
Date: Thu, 20 Aug 2009 14:22:28 -0700	[thread overview]
Message-ID: <1250803348.2754.26.camel@sbs-t61.sc.intel.com> (raw)
In-Reply-To: <20090820210342.GC29994@basil.fritz.box>

On Thu, 2009-08-20 at 14:03 -0700, Andi Kleen wrote:
> > I am leaning towards sysfs, and prefer:
> > 
> >  	/sys/devices/system/cpu/$cpu/chassis_id
> > 
> > How does that sound?
> 
> I would prefer to simply use the existing physical id for this like
> in your original patch.  We already have a bewildering zoo of different
> CPU IDs, no need to increase the confusion even more.
> 
> Incidentially mcelog already knows how to use physical ID for this,
> would need to be changed for a new sysfs interface

Andi, Based on our past experiences, I am nervous if there are some
software/firmware interactions that can negatively affect the cpu
topology detection.

If we really think overloading the "physical id" helps with existing
software, then I am ok with changing the user visible part of the /proc/
or /sys files but not with the kernel's per cpu info's phys_proc_id,
which is used for topology detection etc.

thanks,
suresh


  parent reply	other threads:[~2009-08-20 21:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 16:36 Alex Chiang
2009-08-14 19:07 ` Suresh Siddha
2009-08-14 19:27   ` Alex Chiang
2009-08-14 19:56     ` Suresh Siddha
2009-08-19 21:02       ` Alex Chiang
2009-08-20 18:56         ` Suresh Siddha
2009-08-20 20:54           ` Alex Chiang
2009-08-20 21:03             ` Andi Kleen
2009-08-20 21:20               ` Alex Chiang
2009-08-20 21:26                 ` Suresh Siddha
2009-08-20 21:42                   ` H. Peter Anvin
2009-08-20 21:59                     ` Alex Chiang
2009-08-20 22:04                       ` H. Peter Anvin
2009-08-21  0:32                     ` Andi Kleen
2009-08-21  1:51                       ` H. Peter Anvin
2009-08-21  5:02                       ` Alex Chiang
2009-08-20 21:22               ` Suresh Siddha [this message]
2009-08-21  0:38                 ` Andi Kleen
2009-08-20 21:11             ` Suresh Siddha

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=1250803348.2754.26.camel@sbs-t61.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=achiang@hp.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®