From: Thomas Gleixner <tglx@linutronix.de>
To: george@mvista.com
Cc: Daniel Walker <dwalker@mvista.com>, linux-kernel@vger.kernel.org
Subject: Re: RT and timers
Date: Fri, 10 Jun 2005 10:30:31 +0200 [thread overview]
Message-ID: <1118392231.13312.53.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <42A8EE8C.1010406@mvista.com>
On Thu, 2005-06-09 at 18:36 -0700, George Anzinger wrote:
> > I'm mainly concerned because that loop never breaks . It seems like there
> > could be a condition when the loop never stops. For instance , a very
> > accurate timer interrupt, and timers that continually reset themselves.
>
> As I recall, it is not possible to put a timer in the list for the current time.
> It will be put in the next tick slot or, with HRT, be passed to the hrt code.
> The only case this might fail is if a kernel hrt user restarts his timer for
> "now" or prior to "now". This is bad and hard to correct. The posix-timers
> code does not restart timers until the signal is delivered and then from the
> user thread, not the softirq context.
>
> Did I miss something here?
No, you're right. Expired timers are inserted into the next slot, so the
loop is not able to starve itself.
tglx
next prev parent reply other threads:[~2005-06-10 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 7:37 [patch] Real-Time Preemption, -RT-2.6.12-rc4-V0.7.47-00 Ingo Molnar
2005-05-09 19:54 ` George Anzinger
2005-05-24 7:59 ` Ingo Molnar
2005-05-24 14:27 ` George Anzinger
2005-05-27 7:21 ` Ingo Molnar
2005-06-09 22:13 ` George Anzinger
2005-06-09 22:25 ` RT and timers Daniel Walker
2005-06-09 23:30 ` George Anzinger
2005-06-09 23:47 ` Daniel Walker
2005-06-10 1:36 ` George Anzinger
2005-06-10 8:30 ` Thomas Gleixner [this message]
[not found] ` <20050523091114.GB24956@elte.hu>
2005-05-27 0:38 ` [patch] Real-Time Preemption, -RT-2.6.12-rc4-V0.7.47-00 George Anzinger
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=1118392231.13312.53.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=george@mvista.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®