linux-kernel - Re: [PATCH 08/57] microblaze_v7: Interrupt handling, timer support, selfmod code

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: <alpine.LFD.2.00.0903201142300.29264@localhost.localdomain>
Date:	Fri, 20 Mar 2009 11:49:52 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Michal Simek <monstr@...str.eu>
cc:	LKML <linux-kernel@...r.kernel.org>, john.williams@...alogix.com,
	John Stultz <johnstul@...ibm.com>
Subject: Re: [PATCH 08/57] microblaze_v7: Interrupt handling, timer support,
 selfmod code

On Fri, 20 Mar 2009, Michal Simek wrote:
> Why is my .resolution: 10000000 nsecs? It seems to me weird.

Well. The resulution there is the granularity which the kernel uses to
expire application timers. Once the kernel switches to high resolution
mode it sets the granularity to 1ns.

To get high resolution mode you need two things:

1) a suitable clocksource - which needs to have the
CLOCK_SOURCE_IS_CONTINUOUS flag set

2) a clock event device which has CLOCK_EVT_FEAT_PERIODIC flag set.

3) CONFIG_HIGH_RES_TIMERS=y

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/