From: Peter Zijlstra <peterz@infradead.org>
To: pawel.moll@arm.com, adrian.hunter@intel.com,
john.stultz@linaro.org, mingo@kernel.org, eranian@google.com
Cc: linux-kernel@vger.kernel.org, acme@kernel.org, dsahern@gmail.com,
fweisbec@gmail.com, jolsa@redhat.com, namhyung@gmail.com,
paulus@samba.org, tglx@linutronix.de, rostedt@goodmis.org,
sonnyrao@chromium.org, ak@linux.intel.com,
vincent.weaver@maine.edu, "Peter Zijlstra" <peterz@infradead.org>
Subject: [RFC][PATCH 1/2] time: Add ktime_get_mono_raw_fast_ns()
Date: Fri, 20 Feb 2015 15:29:31 +0100 [thread overview]
Message-ID: <20150220143754.792503379@infradead.org> (raw)
In-Reply-To: 20150220142930.013968488@infradead.org
[-- Attachment #1: peterz-timer-fast_mono_raw.patch --]
[-- Type: text/plain, Size: 3873 bytes --]
By popular demand, add a MONOTONIC_RAW variant.
The implementation is up for discussion; but given the need for the
dummy thing I thought it was easiest to just always update the
mono_raw clock state in timekeeping_update() for now, even though its
mostly wasted cycles.
I suppose the right place would be a resume callback somewhere.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
include/linux/timekeeping.h | 1 +
kernel/time/timekeeping.c | 42 +++++++++++++++++++++++++++++++++++-------
2 files changed, 36 insertions(+), 7 deletions(-)
--- a/include/linux/timekeeping.h
+++ b/include/linux/timekeeping.h
@@ -220,6 +220,7 @@ static inline u64 ktime_get_raw_ns(void)
}
extern u64 ktime_get_mono_fast_ns(void);
+extern u64 ktime_get_mono_raw_fast_ns(void);
/*
* Timespec interfaces utilizing the ktime based ones
--- a/kernel/time/timekeeping.c
+++ b/kernel/time/timekeeping.c
@@ -58,7 +58,8 @@ struct tk_fast {
struct tk_read_base base[2];
};
-static struct tk_fast tk_fast_mono ____cacheline_aligned;
+static struct tk_fast tk_fast_mono ____cacheline_aligned;
+static struct tk_fast tk_fast_mono_raw ____cacheline_aligned;
/* flag for if timekeeping is suspended */
int __read_mostly timekeeping_suspended;
@@ -267,18 +268,18 @@ static inline s64 timekeeping_get_ns_raw
* slightly wrong timestamp (a few nanoseconds). See
* @ktime_get_mono_fast_ns.
*/
-static void update_fast_timekeeper(struct tk_read_base *tkr)
+static void update_fast_timekeeper(struct tk_fast *fast, struct tk_read_base *tkr)
{
- struct tk_read_base *base = tk_fast_mono.base;
+ struct tk_read_base *base = fast->base;
/* Force readers off to base[1] */
- raw_write_seqcount_latch(&tk_fast_mono.seq);
+ raw_write_seqcount_latch(&fast->seq);
/* Update base[0] */
memcpy(base, tkr, sizeof(*base));
/* Force readers back to base[0] */
- raw_write_seqcount_latch(&tk_fast_mono.seq);
+ raw_write_seqcount_latch(&fast->seq);
/* Update base[1] */
memcpy(base + 1, base, sizeof(*base));
@@ -332,6 +333,22 @@ u64 notrace ktime_get_mono_fast_ns(void)
}
EXPORT_SYMBOL_GPL(ktime_get_mono_fast_ns);
+u64 notrace ktime_get_mono_raw_fast_ns(void)
+{
+ struct tk_read_base *tkr;
+ unsigned int seq;
+ u64 now;
+
+ do {
+ seq = raw_read_seqcount(&tk_fast_mono_raw.seq);
+ tkr = tk_fast_mono_raw.base + (seq & 0x01);
+ now = ktime_to_ns(tkr->base_mono) + timekeeping_get_ns(tkr);
+
+ } while (read_seqcount_retry(&tk_fast_mono_raw.seq, seq));
+ return now;
+}
+EXPORT_SYMBOL_GPL(ktime_get_mono_raw_fast_ns);
+
/* Suspend-time cycles value for halted fast timekeeper. */
static cycle_t cycles_at_suspend;
@@ -358,7 +375,11 @@ static void halt_fast_timekeeper(struct
memcpy(&tkr_dummy, tkr, sizeof(tkr_dummy));
cycles_at_suspend = tkr->read(tkr->clock);
tkr_dummy.read = dummy_clock_read;
- update_fast_timekeeper(&tkr_dummy);
+ update_fast_timekeeper(&tk_fast_mono, &tkr_dummy);
+
+ tkr_dummy.mult = tkr->clock->mult;
+ tkr_dummy.shift = tkr->clock->shift;
+ update_fast_timekeeper(&tk_fast_mono_raw, &tkr_dummy);
}
#ifdef CONFIG_GENERIC_TIME_VSYSCALL_OLD
@@ -475,6 +496,8 @@ static inline void tk_update_ktime_data(
/* must hold timekeeper_lock */
static void timekeeping_update(struct timekeeper *tk, unsigned int action)
{
+ static struct tk_read_base tkr;
+
if (action & TK_CLEAR_NTP) {
tk->ntp_error = 0;
ntp_clear();
@@ -489,7 +512,12 @@ static void timekeeping_update(struct ti
memcpy(&shadow_timekeeper, &tk_core.timekeeper,
sizeof(tk_core.timekeeper));
- update_fast_timekeeper(&tk->tkr);
+ update_fast_timekeeper(&tk_fast_mono, &tk->tkr);
+
+ tkr = tk->tkr;
+ tkr.mult = tk->tkr.clock->mult;
+ tkr.shift = tk->tkr.clock->shift;
+ update_fast_timekeeper(&tk_fast_mono_raw, &tkr);
}
/**
next prev parent reply other threads:[~2015-02-20 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 14:29 [RFC][PATCH 0/2] On perf and clocks Peter Zijlstra
2015-02-20 14:29 ` Peter Zijlstra [this message]
2015-02-20 19:49 ` [RFC][PATCH 1/2] time: Add ktime_get_mono_raw_fast_ns() John Stultz
2015-02-20 20:11 ` Peter Zijlstra
2015-03-17 11:24 ` Peter Zijlstra
2015-03-18 19:48 ` John Stultz
2015-02-20 14:29 ` [RFC][PATCH 2/2] perf: Add per event clockid support Peter Zijlstra
2015-02-20 15:28 ` Pawel Moll
2015-02-20 16:01 ` Peter Zijlstra
2015-02-23 8:13 ` Adrian Hunter
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=20150220143754.792503379@infradead.org \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=john.stultz@linaro.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=pawel.moll@arm.com \
--cc=rostedt@goodmis.org \
--cc=sonnyrao@chromium.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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).