From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Christoph Lameter <cl@linux.com>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>,
Kevin Hilman <khilman@linaro.org>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@lge.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/4] nohz: Force boot CPU outside full dynticks range
Date: Thu, 28 Mar 2013 08:38:49 +0100 [thread overview]
Message-ID: <20130328073849.GA24433@gmail.com> (raw)
In-Reply-To: <1364398359-21990-2-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> The timekeeping job must be able to run early on boot
> because there may be some pre-SMP (and thus pre-initcalls )
> components that rely on it. The IO-APIC is one such users
> as it tests the timer health by watching jiffies progression.
Btw., while I agree that a conservative mode is probably wise for bootup,
that IO-APIC assumption could be fixed or even removed.
If the IO-APIC code wants to know whether an interrupt fired, it can take
a look at the kstat_irqs numbers?
Also, could we restrict the boot CPU's mode only during the early bootup
stage - i.e. until we are ready to execute user-space init?
Thaks,
Ingo
next prev parent reply other threads:[~2013-03-28 7:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:32 [PATCH 0/4] nohz: Full dynticks fixes/improvements Frederic Weisbecker
2013-03-27 15:32 ` [PATCH 1/4] nohz: Force boot CPU outside full dynticks range Frederic Weisbecker
2013-03-28 7:38 ` Ingo Molnar [this message]
2013-03-28 13:08 ` Frederic Weisbecker
2013-03-27 15:32 ` [PATCH 2/4] nohz: Print final full dynticks CPUs range on boot Frederic Weisbecker
2013-03-28 7:40 ` Ingo Molnar
2013-03-28 13:12 ` Frederic Weisbecker
2013-03-29 0:25 ` Paul Gortmaker
2013-03-29 0:39 ` Frederic Weisbecker
2013-03-29 2:00 ` Paul E. McKenney
2013-03-29 2:08 ` Paul Gortmaker
2013-03-29 3:51 ` Paul E. McKenney
2013-03-29 2:02 ` Paul Gortmaker
2013-03-27 15:32 ` [PATCH 3/4] nohz: Ensure full dynticks CPUs are RCU nocbs Frederic Weisbecker
2013-03-27 15:32 ` [PATCH 4/4] nohz: New option to force all CPUs in full dynticks range Frederic Weisbecker
2013-03-28 7:45 ` Ingo Molnar
2013-03-28 13:43 ` Frederic Weisbecker
2013-03-30 9:10 ` Ingo Molnar
2013-04-02 13:09 ` Frederic Weisbecker
2013-04-08 14:57 ` Christoph Lameter
2013-04-09 13:22 ` Paul Gortmaker
2013-04-09 14:35 ` Christoph Lameter
2013-04-11 15:19 ` Frederic Weisbecker
2013-04-11 15:37 ` Paul E. McKenney
2013-04-11 15:53 ` Frederic Weisbecker
2013-04-11 16:10 ` Paul E. McKenney
2013-04-11 16:41 ` Christoph Lameter
2013-04-11 17:04 ` Frederic Weisbecker
2013-04-11 17:11 ` Paul E. McKenney
2013-04-11 17:28 ` Frederic Weisbecker
2013-04-11 19:17 ` Paul E. McKenney
2013-04-12 15:59 ` Christoph Lameter
2013-04-15 10:27 ` Ingo Molnar
2013-04-15 16:11 ` Christoph Lameter
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=20130328073849.GA24433@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=fweisbec@gmail.com \
--cc=geoff@infradead.org \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.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