mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Ioannis Kyriakopoulos <johnkyr83@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: timer interrupt stucks using tickless kernel
Date: Mon, 7 Dec 2009 13:30:35 -0800	[thread overview]
Message-ID: <1f1b08da0912071330i35808790r554f7a3a8d712ca7@mail.gmail.com> (raw)
In-Reply-To: <SNT111-DS1957B574BA05A48FEDBFF0A7900@phx.gbl>

On Mon, Dec 7, 2009 at 7:25 AM, Ioannis Kyriakopoulos
<johnkyr83@hotmail.com> wrote:
> I have configured my kernel (2.6.31.6) so that I get periodic ticks from
> the timer interrupt (i.e. tickless is not configured) with a rate determined
> by the HZ value. I've also checked the "high resolution timer support"
> and also SMP support. The posblem is that the timer is getting incremented
> very slowly (way slower than the HZ value), just like it would be if the
> kernel was tickless. Is there an explanation for that? How can I get
> periodic
> timer ticks?
>
> AFAI understand, the HPET timer is used through the IO-APIC controller to
> trigger the processors (N.B. if the "High Resolution Timer Support" option
> wasn't checked, the timer used would  be PIT, right?) and each processor's
> LAPIC timer is used for time keeping. Please correct me if I am wrong.

Not quite, if High Resolution Timers support was disabled, you would
still use the HPET hardware instead of the pit, but you'd stay in
periodic mode. However, since you have Highres Timers on, the system
is using oneshot mode (which is necessary to trigger interrupts faster
then HZ), and likely has chosen the LAPIC timer as the interrupt
source.

In this case, the timer tick becomes an hrt event, that triggers every
HZ, instead of being caused by a periodic interrupt.

thanks
-john

  parent reply	other threads:[~2009-12-07 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Acp3UXhD1R6mbV5yTGykTs+HAU6bQg==>
2009-12-07 15:25 ` Ioannis Kyriakopoulos
2009-12-07 16:06   ` Christoph Lameter
2009-12-07 18:22     ` Ioannis Kyriakopoulos
2009-12-07 21:30   ` john stultz [this message]
2009-12-08  0:18     ` Ioannis Kyriakopoulos
2009-12-08  0:30       ` john stultz
2009-12-08  1:33         ` Ioannis Kyriakopoulos
2009-12-08  2:05           ` john stultz
2009-12-08  3:38             ` Ioannis Kyriakopoulos
2009-12-08 17:11               ` john stultz

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=1f1b08da0912071330i35808790r554f7a3a8d712ca7@mail.gmail.com \
    --to=johnstul@us.ibm.com \
    --cc=johnkyr83@hotmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®