From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@codeaurora.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 0/5] Arch-generic sched_clock NMI safety and optimizations for -tip
Date: Tue, 17 Mar 2015 18:55:59 +0100 [thread overview]
Message-ID: <20150317175559.GJ23123@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1426613906-19718-1-git-send-email-john.stultz@linaro.org>
On Tue, Mar 17, 2015 at 10:38:21AM -0700, John Stultz wrote:
> Daniel Thompson (5):
> sched_clock: Match scope of read and write seqcounts
> sched_clock: Optimize cache line usage
> sched_clock: Remove suspend from clock_read_data
> sched_clock: Remove redundant notrace from update function
> sched_clock: Avoid deadlock during read from NMI
>
> kernel/time/sched_clock.c | 195 ++++++++++++++++++++++++++++++++--------------
> 1 file changed, 138 insertions(+), 57 deletions(-)
Looks sane; makes one wonder if there's more code to share between this
and the core timekeeping; there's some strong resemblance ;-)
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2015-03-17 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 17:38 John Stultz
2015-03-17 17:38 ` [PATCH 1/5] sched_clock: Match scope of read and write seqcounts John Stultz
2015-03-17 17:38 ` [PATCH 2/5] sched_clock: Optimize cache line usage John Stultz
2015-03-17 17:38 ` [PATCH 3/5] sched_clock: Remove suspend from clock_read_data John Stultz
2015-03-17 17:38 ` [PATCH 4/5] sched_clock: Remove redundant notrace from update function John Stultz
2015-03-17 17:38 ` [PATCH 5/5] sched_clock: Avoid deadlock during read from NMI John Stultz
2015-03-17 17:55 ` Peter Zijlstra [this message]
2015-03-25 9:09 ` [PATCH 0/5] Arch-generic sched_clock NMI safety and optimizations for -tip Ingo Molnar
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=20150317175559.GJ23123@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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