From: Anton Blanchard <anton@samba.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: vsdo_datapage.h WTF?
Date: Sun, 8 Oct 2006 01:21:12 +1000 [thread overview]
Message-ID: <20061007152112.GB4043@krispykreme> (raw)
In-Reply-To: <1160233817.4795.85.camel@pmac.infradead.org>
> ELF auxvec?
Could do, but there may end up being a lot of information we need to
export (L2/L3 caches etc). ia64 stuffed it all into sysfs (but didnt
make it generic which was a bit annoying - arch/ia64/kernel/topology.c).
One other thing that would be nice is a generic way to detect SMT
siblings. We could make our /proc/cpuinfo match x86 in this regard, but
/proc/cpuinfo has so many subtle differences between architectures it is
becoming a pain to parse.
Anton
next prev parent reply other threads:[~2006-10-07 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 15:23 vsdo_datapage.h WTF? David Woodhouse
2006-10-06 21:32 ` Benjamin Herrenschmidt
2006-10-07 14:58 ` Anton Blanchard
2006-10-07 15:10 ` David Woodhouse
2006-10-07 15:16 ` Segher Boessenkool
2006-10-07 15:21 ` Anton Blanchard [this message]
2006-10-07 21:56 ` Benjamin Herrenschmidt
2006-10-07 21:54 ` Benjamin Herrenschmidt
2006-10-07 23:36 ` Nathan Lynch
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=20061007152112.GB4043@krispykreme \
--to=anton@samba.org \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.