From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelaf@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Ingo Molnar <mingo@redhat.com>
Subject: [PATCH 0/2] Introduce a fast boot clock and add it as trace clock
Date: Mon, 21 Nov 2016 14:04:55 -0800 [thread overview]
Message-ID: <1479765897-29992-1-git-send-email-joelaf@google.com> (raw)
Currently no trace clock can account for suspend time, using monotonic during
tracing in the suspend path means the trace times wont be advaced. Using the
boot clock with ktime_get_with_offset is not an option due to live locking
concerns in NMI context as suggested by Thomas [1].
These patches add a fast boot clock based on fast monotonic clock and adds
a trace clock based on it which solves both these issues.
Changes since RFC:
- Moved the ktime_t offsets to the end of tk_fast
- use unlikely to optimize for the monotonic case
[1] https://lkml.org/lkml/2016/11/20/75
Joel Fernandes (2):
timekeeping: Introduce a fast boot clock derived from fast monotonic
clock
trace: Add an option for boot clock as trace clock
kernel/time/timekeeping.c | 36 ++++++++++++++++++++++++++++++------
kernel/trace/trace.c | 1 +
2 files changed, 31 insertions(+), 6 deletions(-)
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-11-21 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 22:04 Joel Fernandes [this message]
2016-11-21 22:04 ` [PATCH 1/2] timekeeping: Introduce a fast boot clock derived from fast monotonic clock Joel Fernandes
2016-11-21 22:04 ` [PATCH 2/2] trace: Add an option for boot clock as trace clock Joel Fernandes
2016-11-21 22:48 ` kbuild test robot
2016-11-21 22:59 ` Joel Fernandes
2016-11-21 22:06 ` [PATCH 0/2] Introduce a fast boot clock and add it " 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=1479765897-29992-1-git-send-email-joelaf@google.com \
--to=joelaf@google.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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
Powered by JetHome