public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.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>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/5] Arch-generic sched_clock NMI safety and optimizations for -tip
Date: Wed, 25 Mar 2015 10:09:26 +0100	[thread overview]
Message-ID: <20150325090926.GA696@gmail.com> (raw)
In-Reply-To: <1426613906-19718-1-git-send-email-john.stultz@linaro.org>


* John Stultz <john.stultz@linaro.org> wrote:

> Ingo, Peter, Thomas,
> 
>   The following patches from Daniel extend the arch-generic sched_clock
> implementation so that it can be safely called from NMI (or FIQ on ARM)
> context. They also optimize the sched_clock logic to improve cache
> performance. I wanted to send them along so they could be queued in
> -tip for 4.1.

Hm, the first patch does not apply to tip:timers/core, as it conflicts 
with:

  fb82fe2fe858 clocksource: Add 'max_cycles' to 'struct clocksource'
  362fde041037 clocksource: Simplify the logic around clocksource wrapping safety margins

Mind resending your latest queue as patches, on top of tip:timers/core 
or tip:master?

Thanks,

	Ingo

      parent reply	other threads:[~2015-03-25  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 17:38 [PATCH 0/5] Arch-generic sched_clock NMI safety and optimizations for -tip 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 ` [PATCH 0/5] Arch-generic sched_clock NMI safety and optimizations for -tip Peter Zijlstra
2015-03-25  9:09 ` Ingo Molnar [this message]

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=20150325090926.GA696@gmail.com \
    --to=mingo@kernel.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=peterz@infradead.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