linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: rostedt@goodmis.org, mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, jolsa@kernel.org,
	zhouchengming1@huawei.com, peterz@infradead.org
Subject: [PATCH 0/4] perf/ftrace: Sanitize perf function-trace interaction
Date: Wed, 11 Oct 2017 09:45:28 +0200	[thread overview]
Message-ID: <20171011074528.764500836@infradead.org> (raw)

less is more..

---
 include/linux/ftrace.h          | 83 +++++++---------------------------------
 include/linux/perf_event.h      |  2 +-
 include/linux/trace_events.h    |  9 ++++-
 kernel/events/core.c            | 13 ++-----
 kernel/trace/ftrace.c           | 55 +++------------------------
 kernel/trace/trace_event_perf.c | 84 ++++++++++++++++++++++++-----------------
 kernel/trace/trace_kprobe.c     |  4 +-
 kernel/trace/trace_syscalls.c   |  4 +-
 kernel/trace/trace_uprobe.c     |  2 +-
 9 files changed, 87 insertions(+), 169 deletions(-)

             reply	other threads:[~2017-10-11  8:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  7:45 Peter Zijlstra [this message]
2017-10-11  7:45 ` [PATCH 1/4] perf/ftrace: Revert ("perf/ftrace: Fix double traces of perf on ftrace:function") Peter Zijlstra
2017-10-11 12:57   ` Steven Rostedt
2017-10-11  7:45 ` [PATCH 2/4] perf/ftrace: Fix function trace events Peter Zijlstra
2017-10-11  9:02   ` zhouchengming
2017-10-11 16:40     ` Peter Zijlstra
2017-10-11 11:59   ` Jiri Olsa
2017-10-11 13:04     ` Steven Rostedt
2017-10-11 14:23       ` Jiri Olsa
2017-10-13  7:17   ` Peter Zijlstra
2017-10-16 22:15     ` Steven Rostedt
2017-10-11  7:45 ` [PATCH 3/4] perf/ftrace: Small cleanup Peter Zijlstra
2017-10-11  7:45 ` [PATCH 4/4] ftrace: Kill FTRACE_OPS_FL_PER_CPU 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=20171011074528.764500836@infradead.org \
    --to=peterz@infradead.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=zhouchengming1@huawei.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;
as well as URLs for NNTP newsgroup(s).