LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Milan Svoboda <msvoboda@ra.rockwell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: posix-timers overrun broken?
Date: Wed, 07 Feb 2007 17:14:14 +0100	[thread overview]
Message-ID: <1170864854.3657.23.camel@chaos> (raw)
In-Reply-To: <OFA77229BB.3038F286-ONC125727B.0048DC3E-C125727B.004AA20A@ra.rockwell.com>

On Wed, 2007-02-07 at 14:36 +0100, Milan Svoboda wrote:
> But if the next interrupt arrives before function collect_signal is called 
> to actually deliver the
> siginfo_t to userspace, the si.overrun is cleared in posix_timer_event and 
> we have just forgotten
> one overrun...
> 
> Am I wrong?

Yes. posix_timer_event() is only called when the timer expires the first
time. When the signal has been queued, the timer is not rearmed and the
overrun is calculated in the actual signal delivery path, which calls
do_schedule_next_timer().

	tglx



  reply	other threads:[~2007-02-07 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 13:36 Milan Svoboda
2007-02-07 16:14 ` Thomas Gleixner [this message]
2007-02-08  7:55 Milan Svoboda

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=1170864854.3657.23.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msvoboda@ra.rockwell.com \
    --subject='Re: posix-timers overrun broken?' \
    /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

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).