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 16:53:54 +0200 [thread overview]
Message-ID: <1160319234.5686.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1160319033.3693.19.camel@c-67-180-230-165.hsd1.ca.comcast.net>
On Sun, 2006-10-08 at 07:50 -0700, Daniel Walker wrote:
> On Sun, 2006-10-08 at 12:19 +0200, Thomas Gleixner wrote:
> > On Sun, 2006-10-08 at 10:06 +0200, Thomas Gleixner wrote:
> > > On Fri, 2006-10-06 at 18:53 -0700, akpm@osdl.org wrote:
> > > > Since it's likely that this interface would get used during bootup I moved all
> > > > the clocksource registration into the postcore initcall. This also eliminated
> > > > some clocksource shuffling during bootup.
> > >
> > > We had the init call in postcore already. John moved it to module init
> > > to eliminate trouble with unsynced / unstable TSCs, IIRC.
> > >
> > > John, can you please comment on this.
> >
> > It also breaks pmtimer.
>
> OGAWA reported this already. It breaks the case when there is a verified
> read needed, instead of the fast read. I'll fix it.
I'd like to know, why we need to move that and you did not explain _why_
it is likely that it is used during bootup.
tglx
next prev parent reply other threads:[~2006-10-08 15:25 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 [this message]
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
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=1160319234.5686.12.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.