From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Vince Weaver <vweaver1@eecs.utk.edu>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, mingo@elte.hu
Subject: Re: [tip:perf/urgent] perf: Fix SIGIO handling
Date: Tue, 07 Jun 2011 12:15:57 +0200 [thread overview]
Message-ID: <1307441757.2322.244.camel@twins> (raw)
In-Reply-To: <alpine.DEB.2.00.1106011516480.5384@cl320.eecs.utk.edu>
On Wed, 2011-06-01 at 15:41 -0400, Vince Weaver wrote:
> On Sat, 28 May 2011, tip-bot for Peter Zijlstra wrote:
>
> > Commit-ID: f506b3dc0ec454a16d40cab9ee5d75435b39dc50
> > Gitweb: http://git.kernel.org/tip/f506b3dc0ec454a16d40cab9ee5d75435b39dc50
> > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > AuthorDate: Thu, 26 May 2011 17:02:53 +0200
> > Committer: Ingo Molnar <mingo@elte.hu>
> > CommitDate: Sat, 28 May 2011 17:04:59 +0200
> >
> > perf: Fix SIGIO handling
> >
> > Vince noticed that unless we mmap() a buffer, SIGIO gets lost. So
> > explicitly push the wakeup (including signals) when requested.
> >
> > Reported-by: Vince Weaver <vweaver1@eecs.utk.edu>
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: <stable@kernel.org>
> > Link: http://lkml.kernel.org/n/tip-2euus3f3x3dyvdk52cjxw8zu@git.kernel.org
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> > ---
> > kernel/events/core.c | 8 ++++++++
> > 1 files changed, 8 insertions(+), 0 deletions(-)
> >
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index c09767f..d863b3c 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -5028,6 +5028,14 @@ static int __perf_event_overflow(struct perf_event *event, int nmi,
> > else
> > perf_event_output(event, nmi, data, regs);
> >
> > + if (event->fasync && event->pending_kill) {
> > + if (nmi) {
> > + event->pending_wakeup = 1;
> > + irq_work_queue(&event->pending);
> > + } else
> > + perf_event_wakeup(event);
> > + }
> > +
> > return ret;
> > }
>
> there is something strange about this commit.
>
> With it I get many more overflows than expected (on the order of 40x more)
> when I am using PERF_IOC_REFRESH,1 to restart the sampled counter
> from the end of the signal handler.
>
> Also if you use PERF_IOC_REFRESH with a value other than 1, the value
> seems to be ignored and all of the counts are POLL_IN rather than
> POLL_HUP as I'd expect.
OK, so what semantics do we expect?
Currently (with this patch) when a SIGIO is registered, every event
overflow (sample) generates a POLL_IN SIGIO, except when event_limit
disables the counter, in which case its a POLL_HUP.
Without the patch, we used to send POLL_IN on every wakeup that would
wake poll() and POLL_HUP every time event_limit was reached.
event_limit is incremented using IOC_REFRESH, when its non-zero its
decremented on every overflow, and when it reaches 0 again it fires
SIGIO-POLL_HUP and disables the event.
next prev parent reply other threads:[~2011-06-07 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 15:42 [tip:perf/urgent] perf: Fix SIGIO handling tip-bot for Peter Zijlstra
2011-06-01 19:41 ` Vince Weaver
2011-06-07 10:15 ` Peter Zijlstra [this message]
2011-06-27 13:09 ` 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=1307441757.2322.244.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vweaver1@eecs.utk.edu \
/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).