linux-kernel - Re: [PATCH] x86: Export tsc related information in sysfs

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]

Date:	Tue, 18 May 2010 02:00:52 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dan Magenheimer <dan.magenheimer@...cle.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andi Kleen <andi@...stfloor.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Venkatesh Pallipadi <venki@...gle.com>,
	"H. Peter Anvin" <hpa@...or.com>, chris.mason@...cle.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Export tsc related information in sysfs

* Dan Magenheimer <dan.magenheimer@...cle.com> wrote:

> OK, well ignoring the metaphor, it's clear we 
> disagree on a point that neither one of us can 
> prove: You think your decision to avoid sharing 
> kernel information will stop system programmers 
> from using rdtsc, and I think some are going to use 
> rdtsc anyway and blame Linux when something 
> eventually and silently breaks.

Applications can do various unreliable things, the 
kernel cannot do anything about that.

The point is for the kernel to not be complicit in 
practices that are technically not reliable.

So the kernel wont 'signal' that something is safe to 
use if it is not safe to use.

One suggestion in this thread makes sense i think: to 
signal via sysfs that gettimeofday is slow.

Plus lets hope that we really can figure out a fast, 
TSC based gettimeofday implementation. If that is 
possible then user-space will get a fast gettimeofday 
right out of box.

Thanks,

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