linux-kernel - rdtscp vgettimeofday

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: <20061211003904.GB5366@opteron.random>
Date:	Mon, 11 Dec 2006 01:39:04 +0100
From:	Andrea Arcangeli <andrea@...e.de>
To:	john stultz <johnstul@...ibm.com>
Cc:	ak@...e.de, linux-kernel@...r.kernel.org, tglx@...utronix.de,
	mingo@...e.hu, Suleiman Souhlal <ssouhlal@...eBSD.org>
Subject: rdtscp vgettimeofday

Hello,

As far as I can see, many changes happened but nobody has yet added
the rdtscp support to x86-64. rdtscp finally solves the problem and it
obsoletes hpet for timekeeping and it allows a fully userland
gettimeofday running at maximum speed in userland.

Before rdtscp we could never index the rdtsc offset in a proper index
without being in kernel with preemption disabled, so it could never
work reliably.

What's the status of the DSO API? Does it break backwards
compatibility or is the production glibc already capable of handling
that new kernel API?

I need rdtscp working on vsyscalls ASAP, but I should first understand
if I need to base my code on top of the vDSO patch or if to fork it
off in a dead branch to preserve backwards compatibility with current
glibc userland.

Thanks.
-
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/