From: Bryan Rittmeyer <bryanr@bryanr.org>
To: oprofile-list@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Albert Cahalan <albert@users.sourceforge.net>,
Segher Boessenkool <segher@koffie.nl>,
Andrew Fleming <afleming@motorola.com>,
mikpe@csd.uu.se, o.oppitz@web.de
Subject: [patch] oprofile + ppc750cx perfmon
Date: Mon, 24 Mar 2003 21:09:00 -0800 [thread overview]
Message-ID: <20030325050900.GA30294@bryanr.org> (raw)
Hi all,
I've created very preliminary patches to add PPC Performance Monitor
support to oprofile cvs and linux 2.4.20-ben8:
http://bryanr.org/linux/oprofile/
Sadly, this approach seems very unstable on a 750CX imac (PVR 0008 2214).
The box freezes hard and requires a cold reboot after just a few minutes of
profiling. As benh hinted in a previous thread, I suspect there's an
undocumented erratum for this CPU related to decrementer + pm use.
If anyone has contacts in IBM, further info would be helpful to rule out
software error and possibly to obtain a workaround...
Assuming lots of PPC perfmon hardware is effectively useless with the
decrementer, some solutions are:
1. use the pm irq for all timer-related stuff in Linux, and turn off the
decrementer completely. May mean we need to disable idle loop HLTs, hurting
thermal dissipation / power consumption--I believe the PMC cycle counters
stop incrementing inside power_save_6xx().
2. use the decrementer for profiling. we'd forfeits the perfmon's ability to
sample when MSR[EE]=0 (irqs disabled), taking a big chunk out of
oprofile's appeal imo.
3. hybrid approach. when not using oprofile, the kernel runs as it does
now via the decrementer. when profiling, we switch everything over to the
pm system, disabling the power_save stuff. I suspect this is the best
approach on broken silicon, though there may be some minor nastiness with
swapping between different exception mechanisms for timer_interrupt()
I'm going to try the hybrid approach and will post new patches soon.
My work is commercially sponsored by Ixia and therefore focuses on 2.4
and the IBM PPC750FX/CXe. However, I'm happy to discuss a 2.5 port,
support for other chips, an eventual upstream merge, and any other issues
related to bringing up oprofile on the PPC.
-Bryan
next reply other threads:[~2003-03-25 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 5:09 Bryan Rittmeyer [this message]
2003-03-25 8:57 ` [patch] oprofile + ppc750cx perfmon Bryan Rittmeyer
2003-03-25 9:45 ` Benjamin Herrenschmidt
2003-03-26 5:04 ` Bryan Rittmeyer
[not found] ` <20030325174309.GB57374@compsoc.man.ac.uk>
2003-03-26 3:50 ` Bryan Rittmeyer
[not found] ` <20030327010121.GA94874@compsoc.man.ac.uk>
2003-03-28 8:50 ` Bryan Rittmeyer
[not found] <20030327130535.GA1132@bryanr.org>
[not found] ` <F0BBB858-6093-11D7-BD8D-000393C30512@motorola.com>
2003-03-28 8:31 ` Bryan Rittmeyer
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=20030325050900.GA30294@bryanr.org \
--to=bryanr@bryanr.org \
--cc=afleming@motorola.com \
--cc=albert@users.sourceforge.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mikpe@csd.uu.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox