From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, johnstul@us.ibm.com, mingo@elte.hu,
zippel@linux-m68k.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
Date: Sun, 08 Oct 2006 18:52:43 +0200 [thread overview]
Message-ID: <1160326363.5686.48.camel@localhost.localdomain> (raw)
In-Reply-To: <1160324288.3693.71.camel@c-67-180-230-165.hsd1.ca.comcast.net>
On Sun, 2006-10-08 at 09:18 -0700, Daniel Walker wrote:
> > Early bootup Instrumentation is really not a good argument to make that
> > fragile time related stuff even more complex. There is no problem to
> > register reliable clocksources in early bootup, but do not make this
> > mandatory. Not every system is an ARM SoC, where you can and must rely
> > on the one source which is available usually right when the CPU comes
> > up.
>
> It's not mandatory, it's just preferred.. As I said above, to avoid
> churn. I don't like the churn at boot up, and I tried to make sure there
> was none added in the patch set.
What churn at bootup ? The clocksources _can_ be switched and it does
not matter, when this is done. We had the trouble with the early
registration a couple of month ago, and there is no reason to
reintroduce it. On systems which have exactly one clocksource, you can
register them early in bootup, but please do not touch the x86 setup for
no good reason.
tglx
next prev parent reply other threads:[~2006-10-08 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610070153.k971ren4020838@shell0.pdx.osdl.net>
2006-10-08 8:06 ` + clocksource-increase-initcall-priority.patch added to -mm tree Thomas Gleixner
2006-10-08 10:19 ` Thomas Gleixner
2006-10-08 14:50 ` Daniel Walker
2006-10-08 14:53 ` Thomas Gleixner
2006-10-08 15:45 ` Daniel Walker
2006-10-08 15:58 ` Thomas Gleixner
2006-10-08 16:18 ` Daniel Walker
2006-10-08 16:52 ` Thomas Gleixner [this message]
2006-10-08 17:17 ` Daniel Walker
2006-10-08 19:03 ` Thomas Gleixner
2006-10-08 20:39 ` Daniel Walker
2006-10-08 20:52 ` Thomas Gleixner
2006-10-08 21:15 ` Daniel Walker
2006-10-08 21:20 ` Thomas Gleixner
2006-10-08 21:31 ` Daniel Walker
2006-10-08 21:38 ` Thomas Gleixner
2006-10-08 22:13 ` Daniel Walker
2006-10-08 22:53 ` Thomas Gleixner
2006-10-08 23:35 ` Daniel Walker
2006-10-09 6:56 ` Thomas Gleixner
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=1160326363.5686.48.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zippel@linux-m68k.org \
/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