public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <srostedt@redhat.com>
Subject: Re: perf regression: failed to stat syscalls events
Date: Thu, 24 Jun 2010 09:44:22 +0800	[thread overview]
Message-ID: <20100624014422.GA17476@localhost> (raw)
In-Reply-To: <20100624013915.GA16965@localhost>

On Thu, Jun 24, 2010 at 09:39:15AM +0800, Wu Fengguang wrote:
> Greetings,
> 
> I noticed that
> 
>         # perf stat -e syscalls:sys_enter_mmap true
> 
> refuse to work on 2.6.35-rc1. The last working kernel is 2.6.34.

Other events like lock:* or block:* or whatever continue to work.
So this is a problem specific to syscalls:*.

Thanks,
Fengguang

  reply	other threads:[~2010-06-24  1:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24  1:39 perf regression: failed to stat syscalls events Wu Fengguang
2010-06-24  1:44 ` Wu Fengguang [this message]
2010-06-24  5:58   ` Peter Zijlstra
2010-06-24  6:38     ` Wu Fengguang

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=20100624014422.GA17476@localhost \
    --to=fengguang.wu@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.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