From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Anton Blanchard <anton@samba.org>, Jeff Garzik <jgarzik@pobox.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, cliffw@osdl.org, akpm@zip.com.au,
slpratt@austin.ibm.com, levon@movementarian.org,
haveblue@us.ibm.com
Subject: Re: [PATCH] documentation for basic guide to profiling
Date: Fri, 28 Feb 2003 14:43:48 -0800 [thread overview]
Message-ID: <374420000.1046472228@flay> (raw)
In-Reply-To: <20010101052723.GB22212@krispykreme>
>> Alpha is supported too... (as least I saw the kernel part go in)
>
> sparc64 and ppc64 too, but only timer tick profiling so far.
I need the magic incantation for oprofile for these then ...
Actually, better still, we need a wrapper script that works out this
from /proc/cpuinfo and auto-sets it up for you, if someone who knows
enough about different Pentium types knows how ... I'm happy to go
write it if it's easy to detect ...
My laptop says:
model name : Pentium III (Coppermine)
but a list of pattern matches from someone (or list of people) who
know how this works would be very helpful (ie matching up cpuinfo
to magic incantation to oprofile).
M.
next prev parent reply other threads:[~2003-02-28 22:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 8:12 [PATCH] documentation for basic guide to profiling Martin J. Bligh
2003-02-28 8:29 ` Andrew Morton
2003-02-28 11:22 ` Dave Jones
2003-02-28 15:28 ` Jeff Garzik
2001-01-01 5:27 ` Anton Blanchard
2003-02-28 22:43 ` Martin J. Bligh [this message]
2003-02-28 23:05 ` Dave Hansen
2003-02-28 23:11 ` Martin J. Bligh
2003-03-01 17:51 ` Dave Jones
2003-03-01 20:48 ` John Levon
2003-03-02 23:05 ` Dave Jones
2003-03-01 20:55 ` Martin J. Bligh
2003-03-01 21:33 ` Dave Hansen
2003-03-03 21:57 ` Pavel Machek
2003-02-28 17:36 ` Randy.Dunlap
2003-02-28 18:11 ` Martin J. Bligh
2003-02-28 18:13 ` Dave Hansen
2003-02-28 19:30 ` Randy.Dunlap
2003-02-28 21:45 ` Martin J. Bligh
2003-02-28 21:49 ` Andries Brouwer
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=374420000.1046472228@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=akpm@zip.com.au \
--cc=anton@samba.org \
--cc=cliffw@osdl.org \
--cc=davej@codemonkey.org.uk \
--cc=haveblue@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slpratt@austin.ibm.com \
/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