From: "Suresh E. Warrier" <warrier@linux.vnet.ibm.com>
To: lklml <linux-kernel@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>
Subject: [PATCH 0/2] ring-buffer: More precise timestamps for nested writes
Date: Mon, 13 Apr 2015 21:29:11 -0500 [thread overview]
Message-ID: <552C7B77.1000607@linux.vnet.ibm.com> (raw)
In-Reply-To: <1428459449-10664-1-git-send-email-warrier@linux.vnet.ibm.com>
This patch set provides supports a way to record precise timestamps
for nested writes and a tunable to enable the behavior.
Nested writes occur when a trace writer is preempted, usually through
an interrupt and the interrupt handler also writes its own trace. It has
been noticed on large systems with lots of interrupts, several hundred
trace events can be recorded with the same time stamp.
Fixing this requires a small critical section in the trace write code
in which interrupts are disabled. This is an expensive operation for many
architectures. Hence, the need for a kernel tunable that allows the
feature to be enabled by admins only when needed.
Suresh Warrier (2):
ring-buffer: Introduce precise nested timestamp sysfs attribute
ring-buffer: More precise timestamps for nested writes
Documentation/trace/ftrace.txt | 8 ++++
include/linux/ring_buffer.h | 9 +++++
kernel/trace/ring_buffer.c | 85 ++++++++++++++++++++++++++++++++++++++++--
kernel/trace/trace.c | 51 +++++++++++++++++++++++++
4 files changed, 149 insertions(+), 4 deletions(-)
--
1.8.3.4
next parent reply other threads:[~2015-04-14 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1428459449-10664-1-git-send-email-warrier@linux.vnet.ibm.com>
2015-04-14 2:29 ` Suresh E. Warrier [this message]
2015-04-14 2:31 ` [PATCH 1/2] ring-buffer: Introduce precise nested timestamp sysfs attribute Suresh E. Warrier
2015-04-14 2:38 ` [PATCH 2/2] More precise timestamps for nested writes Suresh E. Warrier
2015-04-14 17:13 ` Peter Zijlstra
2015-04-15 0:33 ` Suresh E. Warrier
2015-04-15 8:45 ` Peter Zijlstra
2015-04-15 9:16 ` Peter Zijlstra
2015-04-15 16:53 ` Suresh E. Warrier
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=552C7B77.1000607@linux.vnet.ibm.com \
--to=warrier@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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