public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Rogier Wolff <R.E.Wolff@bitwizard.nl>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: early printk timings way off
Date: Fri, 16 Sep 2005 15:55:55 +0200	[thread overview]
Message-ID: <9a874849050916065511a6f973@mail.gmail.com> (raw)
In-Reply-To: <20050916103002.GA19839@bitwizard.nl>

On 9/16/05, Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote:
> On Fri, Sep 16, 2005 at 01:00:45AM +0200, Jesper Juhl wrote:
> >
> > I'll just dig into it myself for now, but thank you, if I get really
> > stuck I may ask him.
> 
> The explanation: "jiffies starts at rollover minus a bit" seems to be
> spot-on: If jiffies are 32bit, and counting at 1000 per second, the
> 2^32 / 1000 works out.
> 
> I expect the kernel to run without turning on (timer) interrupts for a
> while during boot: It is still initializing things like memory and the
> processor. Without those, interrupts won't work. This means that the
> timer interrupt will not count in real-time.
> 
> A "jump" of 27 seconds seems unlikely, except if somehow the
> interrupts are somehow accounted. It could very well be that the
> kernel nowadays has a mechanism of measuring the fact that it missed a
> timer interrupt and corrects for that. This would mean that around the
> "jump", the kernel suddenly realized it missed around 27000 interrupts
> and added 27000 to "jiffies"....
> 
> I'd say: Would be nice to get the timings right, but not worth the
> trouble: There are good technical reasons for the observed facts.
> 
Thank you for that explanation Rogier.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-09-16 13:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 21:42 early printk timings way off Jesper Juhl
2005-09-15 21:59 ` Randy.Dunlap
2005-09-15 22:07   ` Jesper Juhl
2005-09-15 22:37     ` Randy.Dunlap
2005-09-15 22:49       ` Jesper Juhl
2005-09-15 22:55         ` Randy.Dunlap
2005-09-15 23:00           ` Jesper Juhl
2005-09-16 10:30             ` Rogier Wolff
2005-09-16 13:55               ` Jesper Juhl [this message]
2005-09-16 17:04         ` Tim Bird
2005-09-16 17:15           ` Tim Schmielau
2005-09-16 17:25             ` Tim Schmielau
2005-09-16 17:42               ` Tim Bird
2005-09-16 18:24                 ` Tony Luck
2005-09-16 17:37             ` Tim Bird
2005-09-16 10:09     ` Tim Schmielau
2005-09-16 10:33       ` Tim Schmielau
2005-09-16 13:56         ` Jesper Juhl

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=9a874849050916065511a6f973@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=R.E.Wolff@bitwizard.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox