mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Simon Derr <Simon.Derr@bull.net>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: -rt IA64 update
Date: Tue, 30 May 2006 07:20:41 -0700	[thread overview]
Message-ID: <1148998842.23411.11.camel@leatherman> (raw)
In-Reply-To: <20060530061503.GA19870@elte.hu>

On Tue, 2006-05-30 at 08:15 +0200, Ingo Molnar wrote:
> * Simon Derr <Simon.Derr@bull.net> wrote:
> > * This kernel, when booting, prints:
> > 
> > 	BUG in check_monotonic_clock at kernel/time/timeofday.c:164
> > 
> > But I think this happens because two get_monotonic_clock() are racing 
> > on two cpus. There is a lock to prevent the race, but it is a seqlock. 
> > That means that it is okay if the race happens since another try will 
> > be attempted, but the message that has been printed on the console 
> > can't be removed, and the user is unnecessarily scared.

Simon, I suspect here you actually have unsynced ITCs, as the
check_monotonic_clock values are all locked w/ spinlocks.

You should probably add a cmpxchg in clocksource_itc_read() where you
currently do the if (last_itc < now), or you'll race on setting
last_itc. Let me know if you still see the issue w/ that fix.


> that too comes from the GTOD patchset. John, should we pick up the 
> latest from -mm?

It would be nice to do so sooner or later. There will probably be a few
regressions as the bits in -mm are more stripped down then the older
code in -rt, but I'd work to fill those holes as they appeared.

Thomas, did you have any thought about the hrt code I sent you?
 
thanks
-john



  reply	other threads:[~2006-05-30 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29 12:25 Simon Derr
2006-05-30  6:15 ` Ingo Molnar
2006-05-30 14:20   ` john stultz [this message]
2006-05-30 15:09     ` Simon Derr

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=1148998842.23411.11.camel@leatherman \
    --to=johnstul@us.ibm.com \
    --cc=Simon.Derr@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

Powered by JetHome