linux-kernel - Re: sparc generic time / clockevents

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: <20070223.015520.125893182.davem@davemloft.net>
Date:	Fri, 23 Feb 2007 01:55:20 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	tglx@...utronix.de
Cc:	linux-kernel@...r.kernel.org, johnstul@...ibm.com
Subject: Re: sparc generic time / clockevents

From: Thomas Gleixner <tglx@...utronix.de>
Date: Fri, 23 Feb 2007 10:56:18 +0100

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

Note we may not care :-)  All the interpolator does is provide
a generic tick based gettimeofday implementation, and the generic
clock code does essentially the same thing.

And the generic clock code must in fact provide the implementations
in order to deal with dyntick issues.

The only other platform using the time interpolator is IA64,
and after my dyntick implementation on sparc64 the one and
only user will be IA64 :-)
-
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/