From: Andi Kleen <andi@firstfloor.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, 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: Fri, 21 Aug 2009 02:38:04 +0200 [thread overview]
Message-ID: <20090821003804.GE29994@basil.fritz.box> (raw)
In-Reply-To: <1250803348.2754.26.camel@sbs-t61.sc.intel.com>
> 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.
It's not just the cpuinfo, but also the socketid reported for
machine check. But yes converting it only for those two
would be a possibility.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-08-21 0:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 16:36 [PATCH] x86: add /proc/cpuinfo/physical id quirks 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
2009-08-21 0:38 ` Andi Kleen [this message]
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=20090821003804.GE29994@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=achiang@hp.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.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