All of lore.kernel.org
 help / color / mirror / Atom feed
From: tony@bakeyournoodle.com (Tony Breeds)
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Olof Johansson <olof@lixom.net>, LinuxPPC-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] Modify sched_clock() to make CONFIG_PRINTK_TIME more sane.
Date: Thu, 21 Jun 2007 14:29:10 +1000	[thread overview]
Message-ID: <20070621042910.GS9768@bakeyournoodle.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0706200936300.27011@pademelon.sonytel.be>

On Wed, Jun 20, 2007 at 09:37:51AM +0200, Geert Uytterhoeven wrote:

Hi Geert,
 
> Just wondering, does the INITIAL_JIFFIES mechanism to catch wrap bugs still
> work after this patch?
> 
> include/linux/jiffies.h:
> | /*
> |  * Have the 32 bit jiffies value wrap 5 minutes after boot
> |  * so jiffies wrap bugs show up earlier.
> |  */
> | #define INITIAL_JIFFIES ((unsigned long)(unsigned int) (-300*HZ))

I've done a quick check and I can't see how my patch would break
anything,  given that sched_clock() on powerpc returns a timebase value
generally not related to jiffies.

I hope I haven't missed anything.

Yours Tony

  linux.conf.au        http://linux.conf.au/ || http://lca2008.linux.org.au/
  Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!

      reply	other threads:[~2007-06-21  4:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19  6:35 [PATCH/RFC] Modify sched_clock() to make CONFIG_PRINTK_TIME more sane Tony Breeds
2007-06-19  6:43 ` Segher Boessenkool
2007-06-19 14:53 ` Olof Johansson
2007-06-20  2:02   ` Tony Breeds
2007-06-20  2:27     ` Olof Johansson
2007-06-20  3:13     ` [PATCH/RFC] Make certain timekeeping variables __read_mostly Tony Breeds
2007-06-20  7:41       ` Geert Uytterhoeven
2007-06-21  4:41         ` Tony Breeds
2007-06-20  7:37     ` [PATCH/RFC] Modify sched_clock() to make CONFIG_PRINTK_TIME more sane Geert Uytterhoeven
2007-06-21  4:29       ` Tony Breeds [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=20070621042910.GS9768@bakeyournoodle.com \
    --to=tony@bakeyournoodle.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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.