linux-kernel - Re: [PATCH 1/1] x86 TSC: set X86_FEATURE_TSC

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:	Sat, 6 Jun 2015 09:12:06 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Len Brown <lenb@...nel.org>, Andy Lutomirski <luto@...nel.org>,
	X86 ML <x86@...nel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 1/1] x86 TSC: set X86_FEATURE_TSC_RELIABLE, per CPUID

On Thu, Jun 4, 2015 at 12:17 AM, H. Peter Anvin <hpa@...or.com> wrote:
> On 06/01/2015 05:45 PM, Len Brown wrote:
>>
>> BTW, it also begs the question if Linux could actually *repair* the BIOS damage?
>>
>
> We may very well be able to by setting the TSC offset register to zero
> on all CPUs.

What TSC offset register?  IIRC before Ivy Bridge (i.e. TSC_ADJUST),
there's a writable TSC register but no visible offset register.

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