All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 2/3] perf: Move exclude_kernel tracepoint check to init event
Date: Thu, 26 Nov 2015 17:44:28 -0300	[thread overview]
Message-ID: <20151126204428.GL28162@kernel.org> (raw)
In-Reply-To: <20151126194910.GA26579@krava.brq.redhat.com>

Em Thu, Nov 26, 2015 at 08:49:10PM +0100, Jiri Olsa escreveu:
> On Thu, Nov 26, 2015 at 04:41:06PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Nov 26, 2015 at 08:34:48PM +0100, Jiri Olsa escreveu:
> > > We suppress events with attr::exclude_kernel set when
> > > the event is generated, so following capture will
> > > give no warning and produce no data:
> > > 
> > >   $ sudo perf record -e sched:sched_switch:u ls
> > >   $ sudo /perf script | wc -l
> > >   0
> > > 
> > > Checking the attr::exclude_kernel at the event init
> > > time and failing right away:
> > 
> > We can as well provide a better warning in the tooling side and don't
> > even ask this nonsensical combo to the kernel, right?
> 
> yep.. I'll update my todo ;-)

Thanks!
 
> > Arguably the kernel was doing what was asked for, its just that no
> > sched:sched_switch took place while in user space... ;-)
> 
> I think it's better to fail like that.. rather than spending
> time on figuring why my test did not give me any data ;-)

Up to peterz ;-)

- Arnaldo

  reply	other threads:[~2015-11-26 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 19:34 [PATCHv2 0/3] perf ftrace: Several perf ftrace:function event fixes Jiri Olsa
2015-11-26 19:34 ` [PATCH 1/3] ftrace: Check sample types only for sampling events Jiri Olsa
2015-11-26 19:34 ` [PATCH 2/3] perf: Move exclude_kernel tracepoint check to init event Jiri Olsa
2015-11-26 19:41   ` Arnaldo Carvalho de Melo
2015-11-26 19:49     ` Jiri Olsa
2015-11-26 20:44       ` Arnaldo Carvalho de Melo [this message]
2015-11-26 19:34 ` [PATCH 3/3] perf ftrace: Use ftrace_ops::private to store event pointer Jiri Olsa

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=20151126204428.GL28162@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.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.