From: benh@kernel.crashing.org
To: Anton Blanchard <anton@samba.org>,
Werner Almesberger <wa@almesberger.net>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: performance monitor exceptions
Date: Wed, 13 Feb 2002 13:48:11 +0100 [thread overview]
Message-ID: <20020213124811.28885@mailhost.mipsys.com> (raw)
In-Reply-To: <20020213111450.GF3886@krispykreme>
>Thats rather ugly :( BTW I have run kernel profiling off the performance
>monitor exception on ppc64 which has been very useful (it allowed us
>to profile inside interrupt disabled regions)
A workaround for pmac or openpic ppc32 is to use the keylargo or the
openpic timer instead of the DEC. That could be a "kernel hacking" option
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-13 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 22:37 performance monitor exceptions Werner Almesberger
2002-02-12 12:55 ` benh
2002-02-12 18:33 ` Werner Almesberger
2002-02-13 11:14 ` Anton Blanchard
2002-02-13 12:48 ` benh [this message]
2002-02-13 19:01 ` G4 boot crash problems with 2.4 "stable" David A. Gatwood
2002-02-13 19:07 ` benh
2002-02-13 21:09 ` David A. Gatwood
2002-02-13 21:06 ` Benjamin Herrenschmidt
2002-02-13 23:48 ` Ethan Benson
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=20020213124811.28885@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wa@almesberger.net \
/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).