All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Arun Sharma <arun@sharma-home.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: 2.6.37 kernel warning in perf_events code
Date: Thu, 10 Feb 2011 18:20:23 -0200	[thread overview]
Message-ID: <20110210202023.GG20676@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTi=WRrBnyiDqOeR7PnqVhh8wLFx5W0tgjNaPvkLg@mail.gmail.com>

Em Thu, Feb 10, 2011 at 12:02:20PM -0800, Arun Sharma escreveu:
> On Thu, Feb 10, 2011 at 11:08 AM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Em Wed, Feb 09, 2011 at 06:50:09PM -0800, Arun Sharma escreveu:
> >> [ Not sure if this is known and fixed in newer kernels. My machine
> >> becomes unusable after this warning triggers ]
> >>
> >> perf record -g -p <pid> cs -o csw.data -- sleep 3

Arun, are you shure the above line is right? I guess it should read:

perf record -g -p <pid> -e cs -o csw.data -- sleep 3

To specify the context switches soft event, right?

> > What kernel are you using? Peter, rings any bells?
> 
> Stock 2.6.37.

- Arnaldo

  reply	other threads:[~2011-02-10 20:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  2:50 2.6.37 kernel warning in perf_events code Arun Sharma
2011-02-10 19:08 ` Arnaldo Carvalho de Melo
2011-02-10 20:02   ` Arun Sharma
2011-02-10 20:20     ` Arnaldo Carvalho de Melo [this message]
2011-02-10 20:46       ` Arun Sharma
2011-02-11  0:42         ` Arnaldo Carvalho de Melo
2011-02-11  0:57           ` Arun Sharma
2011-02-11 12:16             ` 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=20110210202023.GG20676@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=arun@sharma-home.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.