From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Mackerras <paulus@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf_counter: allow and require one-page mmap on counting counters
Date: Tue, 31 Mar 2009 21:15:07 +0200 [thread overview]
Message-ID: <1238526907.3898.93.camel@laptop> (raw)
In-Reply-To: <18889.64659.917207.685779@cargo.ozlabs.ibm.com>
On Wed, 2009-03-25 at 20:42 +1100, Paul Mackerras wrote:
>
> And here's something else that is semi-related: the PAPI guys want a
> kind of counter that counts until it overflows, and then sends a
> signal to the process and disables itself (and the whole group it's
> in).
I tried doing this this evening, and its remarkably hard. Disabling a
counter relies on reading the time, and taking ctx->lock and such.
Things that are impossible to do in NMI context.
Furthermore, some of the software counters (those that use hrtimers)
wait for the completion of the handler (hrtimer_cancel) which would
deadlock when tried from the handler.
Some of these things could be hacked around, others less so, but all in
all it looked remarkably hard for something that sounds so simple.
next prev parent reply other threads:[~2009-03-31 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 8:15 [PATCH] perf_counter: allow and require one-page mmap on counting counters Paul Mackerras
2009-03-25 8:28 ` Ingo Molnar
2009-03-25 8:34 ` Peter Zijlstra
2009-03-25 8:56 ` Paul Mackerras
2009-03-25 9:03 ` Ingo Molnar
2009-03-25 9:14 ` Peter Zijlstra
2009-03-25 9:42 ` Paul Mackerras
2009-03-31 19:15 ` Peter Zijlstra [this message]
2009-04-01 2:32 ` Paul Mackerras
2009-04-01 8:13 ` Peter Zijlstra
2009-04-01 9:31 ` Paul Mackerras
2009-03-25 11:48 ` Peter Zijlstra
2009-03-25 11:52 ` Ingo Molnar
2009-03-25 12:07 ` [tip:perfcounters/core] " Peter Zijlstra
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=1238526907.3898.93.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/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