public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: 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 00:29:35 -0800	[thread overview]
Message-ID: <20030228002935.256ffa98.akpm@digeo.com> (raw)
In-Reply-To: <8550000.1046419962@[10.10.2.4]>

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> ...
> +get readprofile binary fixed for 2.5 / akpm's 2.5 patch from 
> +ftp://ftp.kernel.org/pub/linux/       people/mbligh/tools/readprofile/

                                  kernel/

> +add "profile=2" to the kernel command line.
> +
> +clear		echo 2 > /proc/profile
> +		<test>
> +dump output	readprofile -m /boot/System.map > catured_profile

util-linux-2.11z (at least) has the fixed readprofile.

Of course, installing standard util-linux turns your boot process
into a complete mess because vendors have added incompatible features
to their versions.  But it seems to struggle through.

> +Oprofile
> +--------
> +get source (I use 0.5) from http://oprofile.sourceforge.net/
> +add "poll=idle" to the kernel command line 
> +Configure with CONFIG_PROFILING=y and CONFIG_OPROFILE=y & reboot on new kernel
> +./configure --with-kernel-support
> +make install
> +
> +One time setup (pick appropriate one for your CPU):
> +P3		opcontrol --setup --vmlinux=/boot/vmlinux \
> +		--ctr0-event=CPU_CLK_UNHALTED --ctr0-count=100000
> +Athalon		opcontrol --setup --vmlinux=/boot/vmlinux \

   Athlon

> +		--ctr0-event=RETIRED_INSNS --ctr0-count=100000
> +P4		opcontrol --setup --vmlinux=/boot/vmlinux \
> +		--ctr0-event=GLOBAL_POWER_EVENTS \
> +		--ctr0-unit-mask=1 --ctr0-count=100000
> +
> +start daemon	opcontrol --start-daemon
> +clear		opcontrol --reset
> +start		opcontrol --start
> +		<test>
> +stop		opcontrol --stop
> +dump output	oprofpp -dl -i /boot/vmlinux  >  output_file
> +

OK.  Might be worth adding a pointer to this in REPORTING-BUGS, but
nobody reads that anyway.


  reply	other threads:[~2003-02-28  8:18 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 [this message]
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
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=20030228002935.256ffa98.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=akpm@zip.com.au \
    --cc=cliffw@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --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