From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Segher Boessenkool" <segher@koffie.nl>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: RFC: Performance Monitor Counters device
Date: Thu, 12 Sep 2002 11:52:17 +0200 [thread overview]
Message-ID: <20020912095217.449@192.168.4.1> (raw)
In-Reply-To: <3D80F2F7.3FB3AE4B@koffie.nl>
>For 2), you need the same as for 1), plus have the kernel
>generate a signal on every Nth occurence of some event. The
>PowerPC generates an exception for that, so this is not all
>that hard either. Maybe the kernel can communicate which PMC
>set off the signal; if not, it's trivial for the userland to
>figure that out from the current counters.
Hrm... you should check the various CPU erratas, I think
the perf. counter exception suffers from the same bugs
the thermal exceptions has regarding clashing with DEC
and thus losing exception context information on some
G4s. If this is the case, that would basically prevent
using it.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-12 9:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 20:03 RFC: Performance Monitor Counters device Segher Boessenkool
2002-09-12 9:52 ` Benjamin Herrenschmidt [this message]
2002-09-12 21:45 ` Segher Boessenkool
2002-09-12 10:25 ` Benjamin Herrenschmidt
2002-09-14 11:28 ` Segher Boessenkool
2002-09-15 12:50 ` samuel
2002-09-16 12:38 ` Benjamin Herrenschmidt
2002-09-16 23:50 ` Segher Boessenkool
2002-09-13 3:32 ` Paul Mackerras
2002-09-14 11:36 ` Segher Boessenkool
2002-09-13 10:04 ` Anton Blanchard
2002-09-14 11:39 ` Segher Boessenkool
2002-09-13 22:21 ` David Engebretsen
2002-09-14 11:22 ` Segher Boessenkool
2002-09-16 15:14 ` Dave Engebretsen
2002-09-17 4:59 ` Segher Boessenkool
2002-09-14 4:41 ` Ethan Benson
2002-09-15 1:37 ` Rob Latham
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=20020912095217.449@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--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;
as well as URLs for NNTP newsgroup(s).