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-next>] [day] [month] [year] [list]
Message-ID: <Y33r3w6xvEeZH2XY@linutronix.de>
Date:   Wed, 23 Nov 2022 10:46:07 +0100
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     x86@...nel.org, linux-kernel@...r.kernel.org
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: RDTSCP | IA32_TSC_AUX on x86-32

Hi,

the RDTSCP opcode is translated as "Read Time-Stamp Counter and
Processor ID". It does not read the Processor ID is merely returns the
value of IA32_TSC_AUX which has been previously written by the OS. This
is documented but is misleading if you never made it past the headline.

Now. On 64bit there is __vdso_getcpu and IA32_TSC_AUX is setup (it also
contains the node number but…) for its purpose.
On 32bit there is no __vdso_getcpu and IA32_TSC_AUX is not setup.
RDTSCP is not privileged and returns the proper timestamp but the "CPU"
field is always zero.

Is the format OS specific and not for user purpose or could IA32_TSC_AUX
be setup on 32bit?

Sebastian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ