All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [for-next][PATCH 0/8] tracing/ftrace: Updates for 4.12-rc1
Date: Thu, 18 May 2017 20:43:13 -0400	[thread overview]
Message-ID: <20170519004313.407366856@goodmis.org> (raw)

I'll let these sit in linux-next for a day or two before pushing to Linus.

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 545a028190dae4437aac4f86da7c8ab20857647c


Naveen N. Rao (4):
      ftrace: Simplify glob handling in unregister_ftrace_function_probe_func()
      ftrace/instances: Clear function triggers when removing instances
      selftests/ftrace: Fix bashisms
      selftests/ftrace: Add test to remove instance with active event triggers

Steven Rostedt (1):
      tracing: Move postpone selftests to core from early_initcall

Steven Rostedt (VMware) (2):
      ftrace: Remove #ifdef from code and add clear_ftrace_function_probes() stub
      kprobes: Document how optimized kprobes are removed from module unload

Thomas Gleixner (1):
      tracing/kprobes: Enforce kprobes teardown after testing

----
 include/linux/kprobes.h                                      |  3 +++
 kernel/kprobes.c                                             |  8 +++++++-
 kernel/trace/ftrace.c                                        | 12 ++++++++++--
 kernel/trace/trace.c                                         |  3 ++-
 kernel/trace/trace.h                                         |  5 +++++
 kernel/trace/trace_kprobe.c                                  |  5 +++++
 tools/testing/selftests/ftrace/ftracetest                    |  2 +-
 .../selftests/ftrace/test.d/ftrace/func_event_triggers.tc    |  2 +-
 tools/testing/selftests/ftrace/test.d/functions              |  4 ++--
 .../selftests/ftrace/test.d/instances/instance-event.tc      |  8 ++++++--
 10 files changed, 42 insertions(+), 10 deletions(-)

             reply	other threads:[~2017-05-19  0:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  0:43 Steven Rostedt [this message]
2017-05-19  0:43 ` [for-next][PATCH 1/8] tracing: Move postpone selftests to core from early_initcall Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 2/8] tracing/kprobes: Enforce kprobes teardown after testing Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 3/8] ftrace: Simplify glob handling in unregister_ftrace_function_probe_func() Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 4/8] ftrace/instances: Clear function triggers when removing instances Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 5/8] ftrace: Remove #ifdef from code and add clear_ftrace_function_probes() stub Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 6/8] selftests/ftrace: Fix bashisms Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 7/8] selftests/ftrace: Add test to remove instance with active event triggers Steven Rostedt
2017-05-19  0:43 ` [for-next][PATCH 8/8] kprobes: Document how optimized kprobes are removed from module unload Steven Rostedt

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=20170519004313.407366856@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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.