public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 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>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: [PATCHv2 0/3] perf ftrace: Several perf ftrace:function event fixes
Date: Thu, 26 Nov 2015 20:34:46 +0100	[thread overview]
Message-ID: <1448566489-25922-1-git-send-email-jolsa@kernel.org> (raw)

hi,
sending few fixes for perf ftrace:function event handling.
It's v2 for following original post:
  http://marc.info/?l=linux-kernel&m=144846634815636&w=2

v2 changes:
  - using ftrace_ops::private to store event pointer
  - moving attr::exclude_kernel check into event init processing

thanks,
jirka
---
Jiri Olsa (3):
      ftrace: Check sample types only for sampling events
      perf: Move exclude_kernel tracepoint check to init event
      perf ftrace: Use ftrace_ops::private to store event pointer

 include/linux/perf_event.h      |  3 +++
 kernel/events/core.c            | 30 +++++++++++++++++++++++++-----
 kernel/trace/trace_event_perf.c | 28 +++++++++++++++++++---------
 3 files changed, 47 insertions(+), 14 deletions(-)

             reply	other threads:[~2015-11-26 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 19:34 Jiri Olsa [this message]
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
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=1448566489-25922-1-git-send-email-jolsa@kernel.org \
    --to=jolsa@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox