mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@engr.sgi.com>
To: tony.luck@intel.com
Cc: linux-kernel@vger.kernel.org, alex.williamson@hp.com
Subject: Re: long delays (possibly infinite) in time_interpolator_get_counter
Date: Fri, 29 Jul 2005 17:32:13 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0507291714530.19670@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200507292206.j6TM6w4k004594@agluck-lia64.sc.intel.com>

> diff --git a/include/linux/timex.h b/include/linux/timex.h

Oh. Before I forget: You need to make the same changes to the asm code in 
arch/ia64/kernel/fsys.S in order for this to work properly. The asm code 
has been optimized to the hilt to save every cycle possible. Please dont 
add any. The C code is typically bypassed for all user space gettimeofday 
/ clock_gettime calls.

Hmm.. However, if you did not see the problem in the asm code (which does 
not have the nesting issue of C and wastes some time doing other things) 
then we may solve the issue by either also calling asm from kernel space 
or making sure that some time is wasted on something else then the 
cmpxchg in the inner loop.

Or we can make "nojitter" the default? Then do a

if (nojitter)
	printk(KERN_ERR "Beware: SMP system using ITC as a time source!"
		"Time may fluctuate.\n");

at bootup and hope for the best?

      parent reply	other threads:[~2005-07-30  0:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 22:06 tony.luck
2005-07-29 23:31 ` Christoph Lameter
2005-07-30 16:47   ` Alex Williamson
2005-07-30 18:10     ` Christoph Lameter
2005-07-31 17:02       ` Alex Williamson
2005-07-31 20:00         ` Christoph Lameter
2005-08-01 16:57       ` Bjorn Helgaas
2005-08-01 17:04         ` Christoph Lameter
2005-07-30  0:32 ` Christoph Lameter [this message]

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=Pine.LNX.4.62.0507291714530.19670@schroedinger.engr.sgi.com \
    --to=clameter@engr.sgi.com \
    --cc=alex.williamson@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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®