From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <john.stultz@linaro.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Paweł Moll" <pawel.moll@arm.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Stephane Eranian" <eranian@google.com>,
lkml <linux-kernel@vger.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"David Ahern" <dsahern@gmail.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Jiri Olsa" <jolsa@redhat.com>,
"Namhyung Kim" <namhyung@gmail.com>,
"Paul Mackerras" <paulus@samba.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Sonny Rao" <sonnyrao@chromium.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
vincent.weaver@maine.edu
Subject: Re: [RFC][PATCH 0/4] Another go at ktime_get_raw_fast_ns()
Date: Tue, 24 Mar 2015 16:48:55 +0100 [thread overview]
Message-ID: <20150324154855.GQ21418@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CALAqxLU3M5BU_nS6wbnw4CRSY3g-59N3Wj6xxwsjHm095WjVCA@mail.gmail.com>
On Tue, Mar 24, 2015 at 08:20:07AM -0700, John Stultz wrote:
> On Thu, Mar 19, 2015 at 2:31 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > Hi John,
> >
> > So yeah, I just didn't try hard enough it seems; how about this?
>
> Yea, this looks much better! I'll queue it up for testing and if that
> goes well include it for 4.1.
I have a few patches that depend on it, so if you're ok with it I'd like
to carry the lot. But yes please test ;-)
> > Also, I think we should double check that everything passed to
> > tk_setup_internals(.clock) is either static storage or RCU-sched freed,
> > because with the whole latch thing one CPUs (fast) access might still be
> > in progress while the other is freeing the clock struct.
> >
> > Not sure what the lifetime rules of struct clocksource are here.
>
> At one point it was install and never remove, but I think Thomas
> changed that awhile back, so I think your concern here is a good one.
OK, I'll try and dig around a bit on this.
next prev parent reply other threads:[~2015-03-24 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 9:31 Peter Zijlstra
2015-03-19 9:31 ` [RFC][PATCH 1/4] time: Rename timekeeper::tkr to timekeeper::tkr_mono Peter Zijlstra
2015-03-27 11:44 ` [tip:perf/timer] time: Rename timekeeper::tkr to timekeeper:: tkr_mono tip-bot for Peter Zijlstra
2015-03-19 9:31 ` [RFC][PATCH 2/4] time: Add timerkeeper::tkr_raw Peter Zijlstra
2015-03-27 11:44 ` [tip:perf/timer] " tip-bot for Peter Zijlstra
2015-03-19 9:31 ` [RFC][PATCH 3/4] time: Parametrize all tk_fast_mono users Peter Zijlstra
2015-03-27 11:45 ` [tip:perf/timer] " tip-bot for Peter Zijlstra
2015-03-19 9:31 ` [RFC][PATCH 4/4] time: Introduce tk_fast_raw Peter Zijlstra
2015-03-27 11:45 ` [tip:perf/timer] " tip-bot for Peter Zijlstra
2015-03-24 15:20 ` [RFC][PATCH 0/4] Another go at ktime_get_raw_fast_ns() John Stultz
2015-03-24 15:48 ` Peter Zijlstra [this message]
2015-03-24 16:00 ` John Stultz
2015-03-24 21:02 ` John Stultz
2015-03-25 14:58 ` Peter Zijlstra
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=20150324154855.GQ21418@twins.programming.kicks-ass.net \
--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
Powered by JetHome