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]

Message-ID: <CALCETrUvkBLQZXQYKs2nNTgUeBQvP1jntFPEkh0m6r_-CQt3-w@mail.gmail.com>
Date:	Mon, 8 Jun 2015 16:24:21 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Len Brown <lenb@...nel.org>
Cc:	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 Wed, Jun 3, 2015 at 12:03 PM, Len Brown <lenb@...nel.org> wrote:
> On Mon, Jun 1, 2015 at 9:12 PM, Andy Lutomirski <luto@...capital.net> wrote:
>> On Mon, Jun 1, 2015 at 5:45 PM, Len Brown <lenb@...nel.org> wrote:
>>> On Mon, Jun 1, 2015 at 2:40 PM, Andy Lutomirski <luto@...nel.org> wrote:
>>>> On 05/30/2015 10:44 PM, Len Brown wrote:
>>>>>
>>>>> From: Len Brown <len.brown@...el.com>
>>>>>
>>>>> Speed cpu_up() by believing CPUID's "invariant TSC" flag,
>>>>> and skipping the TSC warp test on single socket systems.
>>>>
>>>>
>>>> I'm typing this email on a "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz" with a
>>>> "X79A-GD65 (8D) (MS-7760)" motherboard.  (DO NOT BUY THAT MOTHERBOARD!)
>>>>
>>>> The brilliant stock firmware breaks TSC sync on bootup.  Even with the
>>>> updated firmware I'm using, it's broken on resume from S3.
>>>
>>> So the stock firmware broke the TSC on boot _and_ S3.
>>> The updated firmware does not break the TSC on boot, but still breaks it on S3?
>>
>> Exactly.
>>
>>>
>>> For this board, please send the output from
>>> $ dmesg | grep -i tsc
>>
>> [    0.000000] tsc: Fast TSC calibration using PIT
>> [    0.000000] tsc: Detected 3199.952 MHz processor
>> [    0.192253] TSC deadline timer enabled
>> [    1.712495] tsc: Refined TSC clocksource calibration: 3199.960 MHz
>> [    2.712791] Switched to clocksource tsc
>>
>> ... suspend and resume ...
>>
>> [   61.414518] TSC synchronization [CPU#0 -> CPU#1]:
>> [   61.414518] Measured 6137255520 cycles TSC warp between CPUs,
>> turning off TS clock.
>> [   61.414522] tsc: Marking TSC unstable due to check_tsc_sync_source failed
>
>
> If you boot this machine with "tsc=reliable", to disable the cpu_up
> check_tsc_sync,
> what happens?  Does the run-time clocksource code detect the bogus TSC values?
> If yes, how long does that take?

They didn't detect it in the time I watched it.

[    0.000000] Command line: rd.md=0 rd.dm=0
rd.lvm.lv=vg_amaluto_2014/root  KEYTABLE=us
rd.luks.uuid=luks-1dd64d38-40c0-4e20-ad67-aa2590991023 SYSFONT=True ro
root=/dev/mapper/vg_amaluto_2014-root LANG=en_US.UTF-8 rhgb quiet
modprobe.blacklist=nvidia tsc=reliable
[    0.000000] Kernel command line: rd.md=0 rd.dm=0
rd.lvm.lv=vg_amaluto_2014/root  KEYTABLE=us
rd.luks.uuid=luks-1dd64d38-40c0-4e20-ad67-aa2590991023 SYSFONT=True ro
root=/dev/mapper/vg_amaluto_2014-root LANG=en_US.UTF-8 rhgb quiet
modprobe.blacklist=nvidia tsc=reliable
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 3200.188 MHz processor
[    0.186542] TSC deadline timer enabled
[    0.312543] Skipped synchronization checks as TSC is reliable.
[    1.683795] tsc: Refined TSC clocksource calibration: 3199.967 MHz
[    1.685339] Switched to clocksource tsc
[  147.158279] Skipped synchronization checks as TSC is reliable.
[  149.086532] Skipped synchronization checks as TSC is reliable.
[  149.098287] Skipped synchronization checks as TSC is reliable.
[  149.110045] Skipped synchronization checks as TSC is reliable.
[  149.121809] Skipped synchronization checks as TSC is reliable.
[  149.133186] Skipped synchronization checks as TSC is reliable.
[  149.144560] Skipped synchronization checks as TSC is reliable.
[  149.155948] Skipped synchronization checks as TSC is reliable.
[  149.167349] Skipped synchronization checks as TSC is reliable.
[  149.178758] Skipped synchronization checks as TSC is reliable.
[  149.190186] Skipped synchronization checks as TSC is reliable.

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