From: Dave Jones <davej@redhat.com>
To: "Lamont R. Peterson" <lamont@gurulabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Transition /proc/cpuinfo -> sysfs
Date: Thu, 12 Aug 2004 11:56:29 +0100 [thread overview]
Message-ID: <20040812105629.GA7359@redhat.com> (raw)
In-Reply-To: <1092287009.2250.9.camel@wraith.lrp.advansoft.us>
On Wed, Aug 11, 2004 at 11:03:29PM -0600, Lamont R. Peterson wrote:
> > - On an HT setup, do we want link(s) pointing to sibling(s)?
>
> I like this idea, even if it is not necessary because siblings should be
> listed sequentially together. i.e. two physical CPUs with HT would be
> cpu0, cpu1, cpu2 & cpu3. Obviously, cpu0 & cpu1 go together and cpu2 &
> cpu3 also go together.
I'll bet *any* userspace code wanting to know this info would be simpler
to write if you do the cpuid calls in the app and parse internally than
walking sysfs to form an interpretation.
> > - Instead of dumping the "flags" field, should we just dump cpu
> > registers as hex strings and let the user decode (as the comment
> > for the x86_cap_flags implies.
>
> I like this. In fact, if it goes this way, then I will write a
> "cpuinfo" program that will do all the decoding as a generic tool.
http://www.codemonkey.org.uk/projects/x86info/
Ok, its x86/amd64 specific, but it does all this parsing and the like
where it should be -- userspace.
Dave
prev parent reply other threads:[~2004-08-12 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 22:41 [PATCH 0/3] Transition /proc/cpuinfo -> sysfs Deepak Saxena
2004-08-11 22:42 ` [PATCH 1/3] [Generic] " Deepak Saxena
2004-08-11 22:44 ` [PATCH 2/3] [i386] " Deepak Saxena
2004-08-11 22:47 ` [PATCH 3/3] [ARM] " Deepak Saxena
2004-08-11 22:47 ` [PATCH 0/3] " Deepak Saxena
2004-08-11 23:13 ` Dave Jones
2004-08-11 23:42 ` Deepak Saxena
2004-08-11 23:59 ` Dave Jones
2004-08-12 2:45 ` Deepak Saxena
2004-08-12 11:07 ` Dave Jones
2004-08-15 6:11 ` Andrew Morton
2004-08-15 6:33 ` Greg KH
2004-08-12 5:03 ` Lamont R. Peterson
2004-08-12 10:56 ` Dave Jones [this message]
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=20040812105629.GA7359@redhat.com \
--to=davej@redhat.com \
--cc=lamont@gurulabs.com \
--cc=linux-kernel@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