From: Andi Kleen <andi@firstfloor.org>
To: soohoon_lee@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question: queuing timer interrupts
Date: Tue, 22 Jul 2008 07:50:08 +0200 [thread overview]
Message-ID: <87wsje79in.fsf@basil.nowhere.org> (raw)
In-Reply-To: <105452.56459.qm@web50711.mail.re2.yahoo.com> (soohoon lee's message of "Mon, 21 Jul 2008 11:04:03 -0700 (PDT)")
soohoon lee <soohoon_lee@yahoo.com> writes:
> There is a system and sometimes it should unavoidably block interrupts for critical jobs for couple of 10ms so will lost timer ticks.
> But keeping the wall clock is also critical.
> I thought about two solutions.
> 1. update wall clock when OS gets out of the critical section.
> 2. Add a hardware to count lost timer ticks, it's easy for this system.
> So when the OS is able to process interrupts again, the hardware generates timer interrupts back to back to compensate lost ticks.
noidlehz should handle this all correctly already. You could just
treat your critical section like the idle loop and calling all the
timer hooks around it. The only subtle issue is that the delay should
not exceed the capability of the platform timer to tick without
overflow.
-Andi
prev parent reply other threads:[~2008-07-22 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 18:04 Question: queuing timer interrupts soohoon lee
2008-07-22 5:50 ` Andi Kleen [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=87wsje79in.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soohoon_lee@yahoo.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