linux-kernel - Re: getting processor numbers

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]

Date:	Wed, 04 Apr 2007 07:46:36 +0200
From:	Eric Dumazet <dada1@...mosbay.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Ulrich Drepper <drepper@...hat.com>,
	Davide Libenzi <davidel@...ilserver.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <ak@...e.de>
Subject: Re: getting processor numbers

H. Peter Anvin a écrit :
> Jeremy Fitzhardinge wrote:
>> H. Peter Anvin wrote:
>>> Mutable data should be separated from code.  I think any current CPU
>>> will do fine as long as they are in separate 128-byte chunks, but they
>>> need at least that much separation.
>> P4 manual says that if one processor modifies data within 2k of another
>> processor executing code, it will trash the entire trace cache.
> 
> Yuck.  Didn't realize the P4 was that sensitive.  OK, so at the least we 
> need a half-page of separation.

Yes but vsyscall API currently defines 4 entry points :

vsyscall0 (vgettimeofday) = ADDR
vsyscall1 (vtime)    = ADDR+1024
vsyscall2 (vgetcpu) = ADDR+2048
vsyscall3 (vxxxxx)  = ADDR+3072

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