From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch]:MC/MT enabling/identification for IA-64
Date: Fri, 25 Feb 2005 01:27:05 +0000 [thread overview]
Message-ID: <16926.32489.612083.600628@napali.hpl.hp.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB7506494303077707@scsmsx401.amr.corp.intel.com>
>>>>> On Tue, 22 Feb 2005 10:24:40 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
Rohit> I agree that the format of these fields should match the
Rohit> format of other fields in cpuinfo.....though it will be nice
Rohit> if we have the same format as that of i386 cpuinfo output.
I'm not sure there is much point to that:
(a) The contents of /proc/cpuinfo is by definition architecture-specific
(b) Applications _should_ allow any whitespace when parsing
/proc/cpuinfo, so in properly-written applications, it shouldn't
matter whether whitespace or tabs are used.
Changing the formatting of /proc/cpuinfo only runs the risk of
existing tools, without benefit to properly written applications.
Rohit> I was thinking of this information as something that apps can
Rohit> use to find the information about which logical execution
Rohit> units (leu) are threads on the same core, which leu are on
Rohit> the same package and so on. This is similar to i386(HT
Rohit> enabled processors) where siblings gives the number of
Rohit> threads on the same package.
I'm not a fan of including redudant info in /proc files.
Rohit> Typically the field names in various PAL call related data
Rohit> structures match their definition in SDM....
I don't think we need to constrain ourselves too much to what the PAL
names are. That code is part of the kernel and it should be readable.
--david
next prev parent reply other threads:[~2005-02-25 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 19:19 [patch]:MC/MT enabling/identification for IA-64 Seth, Rohit
2005-02-18 23:41 ` David Mosberger
2005-02-22 18:24 ` Seth, Rohit
2005-02-25 1:27 ` David Mosberger [this message]
2005-02-25 2:22 ` Seth, Rohit
2005-02-25 6:11 ` David Mosberger
2005-02-25 20:12 ` Seth, Rohit
2005-02-25 20:27 ` Ashok Raj
2005-02-25 20:47 ` David Mosberger
2005-02-25 20:47 ` Seth, Rohit
2005-02-25 21:15 ` Seth, Rohit
2005-02-25 22:46 ` David Mosberger
2005-02-25 23:01 ` Seth, Rohit
2005-02-25 23:03 ` David Mosberger
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=16926.32489.612083.600628@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.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