From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Rosenthal <danielrosenthal@acm.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: behavior of hrtimers scheduled to expire in the past
Date: Tue, 21 Oct 2008 10:09:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0810210953120.3301@apollo> (raw)
In-Reply-To: <4b6fba110810201724v41d26dd8lc9abcba129599fd1@mail.gmail.com>
On Mon, 20 Oct 2008, Daniel Rosenthal wrote:
> What is the intended behavior for an hrtimer that is scheduled to
> expire in the past? I assumed that it would simply be scheduled to
> expire at the nearest available time in the future, but I wrote some
> scheduler code and it looks like hrtimers don't go off at all if they
> are not scheduled to go off at a time which is after rq->clock. Is
> this the intended behavior or is this a bug?
That depends on the callback mode of the hrtimer. The standard ones
are scheduled to the softirq when they are already expired, but those
which are not allowed to run their callback in softirq context are
_not_ enqueued and the caller has to check, whether the timer is
active/enqueued after starting it.
Thanks,
tglx
prev parent reply other threads:[~2008-10-21 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 0:24 Daniel Rosenthal
2008-10-21 8:09 ` Thomas Gleixner [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=alpine.LFD.2.00.0810210953120.3301@apollo \
--to=tglx@linutronix.de \
--cc=danielrosenthal@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome