From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Srivatsa Vaddagiri <vatsa@in.ibm.com>,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>
Subject: Re: perf counter issue - WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list));
Date: Fri, 15 May 2009 11:51:44 -0300 [thread overview]
Message-ID: <20090515145144.GD13664@ghostprotocols.net> (raw)
In-Reply-To: <20090515135604.GC16389@elte.hu>
Em Fri, May 15, 2009 at 03:56:04PM +0200, Ingo Molnar escreveu:
>
> * Srivatsa Vaddagiri <vatsa@in.ibm.com> wrote:
>
> > On Wed, May 13, 2009 at 10:24:33PM +0530, Srivatsa Vaddagiri wrote:
> > > I am hitting this warning in kernel/exit.c (latest -tip code):
> > >
> > > WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list));
> > >
> > > I was using perf counters against a java benchmark.
> >
> > Basically using perf counters as:
> >
> > $ perf stat java ....
>
> hm, is there a reproducer perhaps? Is there some class file i could
> run with specific parameters to reproduce it?
I'll try this with some java benchmarks we have, AMQP related, lets see
if I can reproduce it.
- Arnaldo
next prev parent reply other threads:[~2009-05-15 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 16:54 perf counter issue - WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list)); Srivatsa Vaddagiri
2009-05-13 16:57 ` Srivatsa Vaddagiri
2009-05-15 13:56 ` Ingo Molnar
2009-05-15 14:51 ` Arnaldo Carvalho de Melo [this message]
2009-05-15 15:58 ` Srivatsa Vaddagiri
2009-05-15 16:13 ` Peter Zijlstra
2009-05-15 17:37 ` Peter Zijlstra
2009-05-15 20:27 ` Peter Zijlstra
2009-05-18 4:45 ` Paul Mackerras
2009-05-22 6:25 ` Srivatsa Vaddagiri
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=20090515145144.GD13664@ghostprotocols.net \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=vatsa@in.ibm.com \
/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