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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4850460C.5030406@nortel.com>
Date:	Wed, 11 Jun 2008 15:39:24 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	markh@...pro.net
CC:	Arjan van de Ven <arjan@...radead.org>,
	"linux-os (Dick Johnson)" <linux-os@...logic.com>,
	Jan Engelhardt <jengelh@...ozas.de>,
	"Kok, Auke" <auke-jan.h.kok@...el.com>,
	"solsTiCe d'Hiver" <solstice.dhiver@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6

Mark Hounschell wrote:

> If they are not the same how do you know at what rate the tsc is counting.

You don't, at least not easily.  The timekeeping subsystem knows, but it 
might be unstable, or change with cpu frequency or cpu going idle, etc.

> But back to "how usable is rdtsc for time", is there a
> 
> clock_gettime(CLOCK_MONOTONIC, &time) equivalent that can be used in the kernel?

With current kernels it looks like ktime_get_ts() should give exactly 
the same results, since it's how that userspace function is implemented. 
  With a stable tsc it seems like it should give full accuracy.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ