From: "H. Peter Anvin" <hpa@zytor.com>
To: Alex Chiang <achiang@hp.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
Andi Kleen <andi@firstfloor.org>,
"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 15:04:07 -0700 [thread overview]
Message-ID: <4A8DC857.7060002@zytor.com> (raw)
In-Reply-To: <20090820215954.GH13061@ldl.fc.hp.com>
On 08/20/2009 02:59 PM, Alex Chiang wrote:
>
> Once you go down this path of thinking though, ACPI starts
> looming, and that has other issues associated with it (in my
> mind, mostly around the cleanliness of implementation as ACPI
> starts poking its fingers everywhere).
>
Seems more like DMI than ACPI to me, but this kind of stuff is already
creeping into everything no matter what.
*However* the whole point of this is to not muck with data structures
that the kernel actually cares about in any way, and have a separate
field which is only for human consumption.
-hpa
next prev parent reply other threads:[~2009-08-20 22:05 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 [this message]
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
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=4A8DC857.7060002@zytor.com \
--to=hpa@zytor.com \
--cc=achiang@hp.com \
--cc=andi@firstfloor.org \
--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