kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: trouble locating code that increments jiffies (arm)
Date: Wed, 11 May 2011 12:13:21 -0700	[thread overview]
Message-ID: <BANLkTinDWJ9qFnzcn2R2n_6aB1Ef-rATVQ@mail.gmail.com> (raw)
In-Reply-To: <d47c01f4b6db48194f07ec1f8306bb3b@basementcode.com>

Hi Chris,

On Wed, May 11, 2011 at 6:22 AM,  <chris@basementcode.com> wrote:
> ?Hi list,
>
> ?I've been looking for the code that increments the jiffies variable as
> ?well as the code that connects a timer interrupt to the function that
> ?increments the variable. I'm working with the ARM architecture in case
> ?that makes a difference. I was also wondering, how many jiffies are
> ?there? Right now I'm finding that if I disable the local timer for the
> ?boot CPU (during boot) the jiffies variable stop incrementing. I always
> ?assumed the global timer was supposed to increment a single jiffies
> ?variable. I'm working with an old, modified, version of QEMU so I'm
> ?leaning towards a QEMU bug for this problem.

It's updated here:
<http://lxr.linux.no/linux+v2.6.38/kernel/timer.c#L1304>

The machine description has a .timer entry, which points to a timer
initialization function. We use clock events, so it gets tied in
through there.

Sorry for being vague - I'm only mildly familiar with that particular code.

There is some documentation and background over here:
<http://lxr.linux.no/linux+v2.6.38/Documentation/timers/highres.txt>

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com

      reply	other threads:[~2011-05-11 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 13:22 trouble locating code that increments jiffies (arm) chris at basementcode.com
2011-05-11 19:13 ` Dave Hylands [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=BANLkTinDWJ9qFnzcn2R2n_6aB1Ef-rATVQ@mail.gmail.com \
    --to=dhylands@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).