mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Valdis.Kletnieks@vt.edu,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@googlemail.com>
Subject: Re: 2.6.32-rc5-mmotm1101 - lockdep whinge during early boot
Date: Thu, 5 Nov 2009 16:54:37 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911051653170.12138@localhost.localdomain> (raw)
In-Reply-To: <20091105153321.GB24690@redhat.com>

On Thu, 5 Nov 2009, Oleg Nesterov wrote:

> On 11/05, Oleg Nesterov wrote:
> >
> > On 11/05, Thomas Gleixner wrote:
> > >
> > > Hmm, we fixed all this lock madness in mainline already.
> > > clocksource_done_booting() does not longer call
> > > create_workqueue(). How got this code reverted in motm ?
> >
> > I don't understand this code at all. But this is what I see
> > in Linus's tree:
> >
> > 	clocksource_done_booting
> > 	    clocksource_select
> > 	        timekeeping_notify
> > 	            stop_machine
> > 	                 stop_machine_create
> >
> >
> > OTOH, I don't see where native_cpu_up() path calls clocksource_change_rating(),
> > perhaps this was changed in -mm.
> 
> I believe Martin knows the answer:
> 
> On 11/05, Martin Schwidefsky wrote:
> >
> > That is imho caused by this patch snippet from the linux-next.patch from mmotd:
> >
> > diff -puN arch/x86/kernel/tsc.c~linux-next arch/x86/kernel/tsc.c
> > --- a/arch/x86/kernel/tsc.c~linux-next
> > +++ a/arch/x86/kernel/tsc.c
> > @@ -763,14 +763,12 @@ void mark_tsc_unstable(char *reason)
> >  {
> >         if (!tsc_unstable) {
> >                 tsc_unstable = 1;
> > -               printk(KERN_INFO "Marking TSC unstable due to %s\n", reason);
> > +               printk("Marking TSC unstable due to %s\n", reason);
> >                 /* Change only the rating, when not registered */
> >                 if (clocksource_tsc.mult)
> > -                       clocksource_mark_unstable(&clocksource_tsc);
> > -               else {
> > -                       clocksource_tsc.flags |= CLOCK_SOURCE_UNSTABLE;
> > +                       clocksource_change_rating(&clocksource_tsc, 0);
> 
>                           ^^^^^^^^^^^^^^^^^^^^^^^^^

Which basically reverts commit 7285dd7fd375763bfb8ab1ac9cf3f1206f503c16

Thanks,

	tglx


  reply	other threads:[~2009-11-05 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 16:11 Valdis.Kletnieks
2009-11-05  9:11 ` Rusty Russell
2009-11-05 14:10   ` Oleg Nesterov
2009-11-05 14:54     ` Martin Schwidefsky
2009-11-05 14:54     ` Thomas Gleixner
2009-11-05 15:22       ` Oleg Nesterov
2009-11-05 15:33         ` Oleg Nesterov
2009-11-05 15:54           ` Thomas Gleixner [this message]
2009-11-05 16:20             ` Martin Schwidefsky
2009-11-05 16:53               ` Thomas Gleixner
2009-11-09  9:43                 ` 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=alpine.LFD.2.00.0911051653170.12138@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=schwidefsky@googlemail.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

all inboxes | Powered by JetHome®