From: Kurt Kanzenbach <kurt@linutronix.de>
To: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>
Cc: Richard Cochran <richardcochran@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kurt Kanzenbach <kurt@linutronix.de>
Subject: [PATCH 0/3] tracing: Introduce trace clock tai
Date: Sat, 9 Apr 2022 10:12:57 +0200 [thread overview]
Message-ID: <20220409081300.4762-1-kurt@linutronix.de> (raw)
Hi,
the Linux kernel tracing infrastructure has support for using different clocks
to generate timestamps for trace events. Especially in TSN networks it's useful
to have TAI as trace clock, because the application scheduling is done in
accordance to the network time, which is based on TAI. With a tai trace_clock in
place, it becomes very convenient to correlate network activity with Linux
kernel application traces.
However, there's no fast accessor for CLOCK_TAI yet. Therefore, patch #1 is
adding one. Patch #2 introduces the clock and the last one adds documentation
for it.
Thanks,
Kurt
Kurt Kanzenbach (3):
timekeeping: Introduce fast accessor to clock tai
tracing: Introduce trace clock tai
tracing: Add documentation for trace clock tai
Documentation/trace/ftrace.rst | 12 ++++++++++++
include/linux/timekeeping.h | 1 +
kernel/time/timekeeping.c | 17 +++++++++++++++++
kernel/trace/trace.c | 1 +
4 files changed, 31 insertions(+)
--
2.30.2
next reply other threads:[~2022-04-09 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 8:12 Kurt Kanzenbach [this message]
2022-04-09 8:12 ` [PATCH 1/3] timekeeping: Introduce fast accessor to clock tai Kurt Kanzenbach
2022-04-09 13:37 ` Steven Rostedt
2022-04-09 20:33 ` Thomas Gleixner
2022-04-11 20:58 ` Thomas Gleixner
2022-04-12 7:03 ` Kurt Kanzenbach
2022-04-09 20:32 ` Thomas Gleixner
2022-04-09 8:12 ` [PATCH 2/3] tracing: Introduce trace " Kurt Kanzenbach
2022-04-09 8:13 ` [PATCH 3/3] tracing: Add documentation for " Kurt Kanzenbach
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=20220409081300.4762-1-kurt@linutronix.de \
--to=kurt@linutronix.de \
--cc=corbet@lwn.net \
--cc=john.stultz@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sboyd@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 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).