From: Albert Cahalan <albert@users.sf.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
oprofile-list@lists.sourceforge.net,
linuxppc-dev@lists.linuxppc.org,
Segher Boessenkool <segher@koffie.nl>,
o.oppitz@web.de, afleming@motorola.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch] oprofile for ppc
Date: 07 Mar 2003 13:31:01 -0500 [thread overview]
Message-ID: <1047061862.1900.67.camel@cube> (raw)
In-Reply-To: <1047032003.12206.5.camel@zion.wanadoo.fr>
On Fri, 2003-03-07 at 05:13, Benjamin Herrenschmidt wrote:
> On Fri, 2003-03-07 at 10:29, Albert D. Cahalan wrote:
>> This is basic timer profiling for ppc, tested on the
>> 2.5.62 linuxppc kernel. It's a port of the ppc64 code.
>
> I'm sure I missed something... but I fail to see the the
> interest in profiling based on sampling the instruction ptr
> on a 100 Hz basis. This is way to slow to give any useful
> results imho
This is just the first part of the code. Please merge it
into any tree you have, unless it's obviously broken.
It is useful for long-running processes that don't do
much that is tied to the clock tick. (number crunching,
maybe X, web browsers without animations, /tmp cleaner...)
The i386 port is already using 1000 Hz in the kernel,
and has 100 Hz as a non-default option. I'd really like
to have this on my Mac; lots of things would improve.
I intend to allow sampling based on the performance counter
interrupt/trap/exception and the external interrupt signal.
next prev parent reply other threads:[~2003-03-07 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 9:29 [patch] oprofile for ppc Albert D. Cahalan
2003-03-07 10:13 ` Benjamin Herrenschmidt
2003-03-07 18:31 ` Albert Cahalan [this message]
2003-03-08 15:10 ` Benjamin Herrenschmidt
2003-03-08 19:30 ` Albert Cahalan
2003-03-08 21:41 ` Benjamin Herrenschmidt
2003-03-10 4:00 ` Segher Boessenkool
2003-03-10 3:50 ` Segher Boessenkool
2003-03-10 6:31 ` Albert Cahalan
2003-03-10 8:43 ` Benjamin Herrenschmidt
2003-03-11 2:14 ` Segher Boessenkool
2003-03-11 21:54 ` Andrew Fleming
2003-03-11 23:13 ` Albert Cahalan
2003-03-12 0:25 ` Andrew Fleming
2003-03-11 23:30 ` mikpe
2003-03-12 0:10 ` Albert Cahalan
2003-03-12 10:42 ` mikpe
2003-03-10 8:38 ` Benjamin Herrenschmidt
2003-03-20 21:32 ` Andy Fleming
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=1047061862.1900.67.camel@cube \
--to=albert@users.sf.net \
--cc=acahalan@cs.uml.edu \
--cc=afleming@motorola.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=o.oppitz@web.de \
--cc=oprofile-list@lists.sourceforge.net \
--cc=segher@koffie.nl \
/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.