From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/4] tracing: Updates for 5.10
Date: Mon, 28 Sep 2020 21:11:56 -0400 [thread overview]
Message-ID: <20200929011156.807392552@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: fdb46faeab2f3fa2b43a55059b33b8f98b2e1442
Masami Hiramatsu (1):
tracing/boot: Initialize per-instance event list in early boot
Steven Rostedt (VMware) (3):
tracepoints: Add helper to test if tracepoint is enabled in a header
mm/page_ref: Convert the open coded tracepoint enabled to the new helper
x86: Use tracepoint_enabled() for msr tracepoints instead of open coding it
----
Documentation/trace/tracepoints.rst | 27 ++++++++++++++++++++++++
arch/x86/include/asm/msr.h | 20 ++++++++----------
include/linux/page_ref.h | 42 ++++++++++++++++++-------------------
include/linux/tracepoint-defs.h | 34 ++++++++++++++++++++++++++++++
kernel/trace/trace.c | 3 ++-
kernel/trace/trace.h | 1 +
kernel/trace/trace_events.c | 30 +++++++++++++-------------
7 files changed, 110 insertions(+), 47 deletions(-)
next reply other threads:[~2020-09-29 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 1:11 Steven Rostedt [this message]
2020-09-29 1:11 ` [for-next][PATCH 1/4] tracing/boot: Initialize per-instance event list in early boot Steven Rostedt
2020-09-29 1:11 ` [for-next][PATCH 2/4] tracepoints: Add helper to test if tracepoint is enabled in a header Steven Rostedt
2020-09-29 1:11 ` [for-next][PATCH 3/4] mm/page_ref: Convert the open coded tracepoint enabled to the new helper Steven Rostedt
2020-09-29 1:12 ` [for-next][PATCH 4/4] x86: Use tracepoint_enabled() for msr tracepoints instead of open coding it 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=20200929011156.807392552@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome