From: Andrew Morton <akpm@osdl.org>
To: Stefan Foerster <stefan@stefan-foerster.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very bad interactivity with 2.6.0 and SCSI disks (aic7xxx)
Date: Sun, 17 Aug 2003 23:03:25 -0700 [thread overview]
Message-ID: <20030817230325.2887ca49.akpm@osdl.org> (raw)
In-Reply-To: <20030818054851.GA5252@in-ws-001.cid-net.de>
Stefan Foerster <stefan@stefan-foerster.de> wrote:
>
> * Andrew Morton <akpm@osdl.org> wrote:
> > Stefan Foerster <stefan@stefan-foerster.de> wrote:
> > A kernel profile would be needed to diagnose this. You could use
> > readprofile, but as it may be an interrupt problem, the NMI-based oprofile
> > output would be better.
>
> Is this procedure documented anywhere?
>
Documentation/basic_profiling.txt and oprofile.sourceforge.net.
oprofile is hard to get going and they seem to keep on changing things.
A quick primer would be:
- download the userspace tools, carefully read the INSTALL and README
files.
- You need to do ./configure --with-kernel-support (something like that).
- build and install.
>From my notes, for a P4:
opcontrol --setup --vmlinux=/boot/vmlinux --ctr0-count=600000 --ctr0-unit-mask=1 --ctr0-event=GLOBAL_POWER_EVENTS
For a PIII:
opcontrol --setup --vmlinux=/boot/vmlinux --ctr0-count=600000 --ctr0-event=CPU_CLK_UNHALTED
Then:
opcontrol --shutdown
rm -rf /var/lib/oprofile
opcontrol --start-daemon
opcontrol --start
<run test>
opcontrol --stop
oprofpp -l /boot/vmlinux
oprofpp -Lo /boot/vmlinux > /tmp/1
I use this script.
#!/bin/sh
sudo opcontrol --stop
sudo opcontrol --shutdown
sudo rm -rf /var/lib/oprofile
sudo opcontrol --start-daemon
sudo opcontrol --start
time $@
sudo opcontrol --stop
sudo opcontrol --shutdown
next prev parent reply other threads:[~2003-08-18 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 1:32 Very bad interactivity with 2.6.0 and SCSI disks (aic7xxx) Stefan Foerster
2003-08-18 2:21 ` Andrew Morton
2003-08-18 2:31 ` William Lee Irwin III
2003-08-18 5:48 ` Stefan Foerster
2003-08-18 6:03 ` Andrew Morton [this message]
2003-08-19 5:43 ` Stefan Foerster
2003-08-19 5:54 ` Nick Piggin
2003-08-18 19:04 ` Justin T. Gibbs
2003-08-18 19:49 ` Stefan Foerster
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=20030817230325.2887ca49.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@stefan-foerster.de \
/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;
as well as URLs for NNTP newsgroup(s).