linux-kernel - sparc generic time / clockevents [ was Re: NO

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: <1172224579.25076.219.camel@localhost.localdomain>
Date:	Fri, 23 Feb 2007 10:56:18 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	David Miller <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org, john stultz <johnstul@...ibm.com>
Subject: sparc generic time / clockevents [ was Re: NO_HZ: timer interrupt
	stuck ]

David,

<trimmed CC due to sparcness, added John instaed >

On Fri, 2007-02-23 at 01:25 -0800, David Miller wrote:
> > Yes, all you need is to omit the CLOCK_EVT_FEAT_PERIODIC flag when you
> > register your device.
> 
> Thanks a lot Thomas.
> 
> I noticed while doing this work that the generic clock code is
> incompatible with the time interpolator, since both provide a
> do_{get,set}timeofday() implementation.  Just FYI...

John, can you have a look at this ?

	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/