linux-kernel - Re: [uClinux-dev] [PATCH] m68k: restore lost coldfire CLOCK_TICK

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: <200906251330.10127.arnd@arndb.de>
Date:	Thu, 25 Jun 2009 13:30:09 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Greg Ungerer <gerg@...pgear.com>
Cc:	uClinux development list <uclinux-dev@...inux.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [uClinux-dev] [PATCH] m68k: restore lost coldfire CLOCK_TICK_RATE

On Thursday 25 June 2009, Greg Ungerer wrote:
> I thought it did that based on gettimeofday()?  And that ends up
> going through the underlying timer code, which for both of
> the ColdFire timer types doesn't use CLOCK_TICK_RATE. They directly
> use the MCF_CLK definition.

The problem is the definition of TICK_NSEC, which is calculated from
CLOCK_TICK_RATE. If you use the i8253 PIT tick rate, this will be
slightly different from the regular TICK_NSEC value of (1000000000 / HZ).

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