From: "Viktor Rosendahl (BMW)" <viktor.rosendahl@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joel@joelfernandes.org>,
"Viktor Rosendahl (BMW)" <viktor.rosendahl@gmail.com>
Subject: [PATCH v7 0/4] Some new features for the preempt/irqsoff tracers
Date: Fri, 20 Sep 2019 17:22:15 +0200 [thread overview]
Message-ID: <20190920152219.12920-1-viktor.rosendahl@gmail.com> (raw)
Hello all,
There are not many changes this time. I mainly changed my email address,
tweaked a commit message and removed the cluttering of a copyright message.
Changes in v7:
- [PATCH 1/4]:
* I have added some reasons to end of the commit message why I believe that
it makes sense to create a new workqueue.
- [PATCH 2/4]:
* Removed the cluttering of the copyright message.
- [PATCH 3/4]:
* No change
- [PACTH 4/4]:
* No change
This series is meant to address two issues with the latency tracing.
The first three patches provide a method to trace latencies that always
occurs very close to each other and to differentiate between them, in spite
of the fact that the latency tracers work in overwrite mode.
[PATCH 1/4] This implement fs notification for tracing_max_latency. It
makes it possible for userspace to detect when a new latency has been
detected.
[PATCH 2/4] This extends the preemptirq_delay_test module so that it can be
used to generate a burst of closely occurring latencies.
[PATCH 3/4] This adds a user space program to the tools directory that
utilizes the fs notification feature and a randomized algorithm to print out
any of the latencies in a burst with approximately equal probability.
The last patch is not directly connected but earlier it didn't apply
cleanly on its own. However, now it does, so in principle it could be
applied separately from the others.
[PATCH 4/4] This adds the option console-latency to the trace options. This
makes it possible to enable tracing of console latencies.
best regards,
Viktor
Viktor Rosendahl (BMW) (4):
ftrace: Implement fs notification for tracing_max_latency
preemptirq_delay_test: Add the burst feature and a sysfs trigger
Add the latency-collector to tools
ftrace: Add an option for tracing console latencies
include/linux/irqflags.h | 22 +
kernel/printk/printk.c | 6 +-
kernel/trace/Kconfig | 6 +-
kernel/trace/preemptirq_delay_test.c | 144 ++-
kernel/trace/trace.c | 75 +-
kernel/trace/trace.h | 19 +
kernel/trace/trace_hwlat.c | 4 +-
kernel/trace/trace_irqsoff.c | 12 +
tools/Makefile | 14 +-
tools/trace/Makefile | 20 +
tools/trace/latency-collector.c | 1212 ++++++++++++++++++++++++++
11 files changed, 1501 insertions(+), 33 deletions(-)
create mode 100644 tools/trace/Makefile
create mode 100644 tools/trace/latency-collector.c
--
2.17.1
next reply other threads:[~2019-09-20 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 15:22 Viktor Rosendahl (BMW) [this message]
2019-09-20 15:22 ` [PATCH v7 1/4] ftrace: Implement fs notification for tracing_max_latency Viktor Rosendahl (BMW)
2019-10-02 0:32 ` Joel Fernandes
2019-10-03 10:23 ` Viktor Rosendahl
2019-10-02 15:13 ` Steven Rostedt
2019-10-02 22:04 ` Viktor Rosendahl
2019-10-02 22:50 ` Steven Rostedt
2019-09-20 15:22 ` [PATCH v7 2/4] preemptirq_delay_test: Add the burst feature and a sysfs trigger Viktor Rosendahl (BMW)
2019-10-02 0:43 ` Joel Fernandes
2019-09-20 15:22 ` [PATCH v7 3/4] Add the latency-collector to tools Viktor Rosendahl (BMW)
2019-09-20 15:22 ` [PATCH v7 4/4] ftrace: Add an option for tracing console latencies Viktor Rosendahl (BMW)
2019-10-02 0:52 ` Joel Fernandes
2019-10-02 22:44 ` Viktor Rosendahl
2019-10-03 13:48 ` Joel Fernandes
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=20190920152219.12920-1-viktor.rosendahl@gmail.com \
--to=viktor.rosendahl@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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