linux-kernel - Re: question about periodic clocks

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: <1173516061.24738.1148.camel@localhost.localdomain>
Date:	Sat, 10 Mar 2007 09:41:00 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: question about periodic clocks

On Fri, 2007-03-09 at 15:26 -0800, Jeremy Fitzhardinge wrote:
> How does the clock period get set on periodic timers?  In my clock
> driver, I'm seeing a call to ->set_mode(CLOCK_EVT_MODE_PERIODIC, evt),
> but then... nothing.  I was expecting a call to set_next_event to set
> the timer period.

Good point. I never thought about that and we set the period in the
clock event device itself. You are right, the clockevents layer should
hand over the period either with the set_mode call or seperately.
Probably with the set_mode call, as it is needed exactly there and we
don't want to have a "if (dev->mode == XXX)" check in set_next_event().

I look into this.

Thanks,

	tglx


-
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/