linux-kernel - Re: clockevent questions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <38b2ab8a0705122252kc067722s3298db20cfd5552a@mail.gmail.com>
Date:	Sun, 13 May 2007 07:52:54 +0200
From:	"Francis Moreau" <francis.moro@...il.com>
To:	tglx@...utronix.de
Cc:	linux-kernel@...r.kernel.org
Subject: Re: clockevent questions

On 5/12/07, Thomas Gleixner <tglx@...utronix.de> wrote:
> On Sat, 2007-05-12 at 22:13 +0200, Francis Moreau wrote:
> > > Yes, it is correct. The generic timer code requests an event in the
> > > future. It does not care, whether the hardware device can handle that or
> > > not. So the clock event code limits the delta to the maximum delta the
> > > device can handle. The interrupt fires and the generic timer code
> > > reschedules the event with the remaining delta time.
> > >
> >
> > Thanks again for explanations. Could you give me a pointer of this reschedules ?
>
> Well, it ends up in hrtimer_interrupt() and the code there finds out,
> that the next timer is not due right now, so it simply requests the same
> (absolute) time event again, which is processed by the clock events code
> and eventually limited to the max delta of the device again.
>

OK, I'll give it a deeper look soon.

Thanks for your great work !
-- 
Francis
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/