public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	linux-kernel@vger.kernel.org, hpa@zytor.com,
	paulmck@linux.vnet.ibm.com, akpm@linux-foundation.org,
	khilman@linaro.org, tglx@linutronix.de, axboe@fb.com,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/nohz] nohz: Move full nohz kick to its own IPI
Date: Wed, 7 May 2014 21:07:14 +0200	[thread overview]
Message-ID: <20140507190714.GA22890@gmail.com> (raw)
In-Reply-To: <20140507161350.GT30445@twins.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Wed, May 07, 2014 at 06:05:08PM +0200, Frederic Weisbecker wrote:
> > So we can as well zap these commits and replace them with the irq_work_on()
> > conversion (still preparing that).
> 
> I hear you, but I think Ingo doesn't want to rebase the tree because its
> public, but maybe he can make an exception..

Since tip:timers/nohz only contains these commits:

 fc1781cc66b1 Merge branch 'timers/nohz-ipi-for-tip-v3' of git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks into timers/nohz
 72aacf0259bb nohz: Move full nohz kick to its own IPI
 55d77c215c74 smp: Non busy-waiting IPI queue

we can zap them all, or even keep 55d77c215c74.

Frederic, which one would you prefer?

Thanks,

	Ingo

  reply	other threads:[~2014-05-07 19:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-72aacf0259bb7d53b7a3b5b2f7bf982acaa52b61@git.kernel.org>
2014-05-05 12:37 ` [tip:timers/nohz] nohz: Move full nohz kick to its own IPI Peter Zijlstra
2014-05-05 13:31   ` Peter Zijlstra
2014-05-05 15:04     ` Frederic Weisbecker
2014-05-05 15:12       ` Peter Zijlstra
2014-05-05 15:34         ` Frederic Weisbecker
2014-05-07 15:17           ` Peter Zijlstra
2014-05-07 15:29             ` Frederic Weisbecker
2014-05-07 15:37               ` Peter Zijlstra
2014-05-07 16:05                 ` Frederic Weisbecker
2014-05-07 16:13                   ` Peter Zijlstra
2014-05-07 19:07                     ` Ingo Molnar [this message]
2014-05-09 15:10                       ` Frederic Weisbecker
2014-05-11  5:34                         ` Ingo Molnar
2014-05-05 14:52   ` Frederic Weisbecker
2014-05-05 14:58     ` Peter Zijlstra
2014-05-05 15:06       ` Frederic Weisbecker

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=20140507190714.GA22890@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@fb.com \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.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