body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2023 X Corp.

Conversation

(1/2) I remember a few weeks ago and during a conference, I asked Prof. Onur Mutlu about timing measurements in Intel. The question was why major OSs like Windows, Linux won’t forget about RDTSC & RDTSCP in User-mode (some exact timing features in user-mode will not work anymore)

1

1

23

(2/2) And you know, none of these side-channels like #meltdown and #spectre and other side-channels work anymore. He told me, there are other ways of measuring timing in User-mode other than RDTSC & RDTSCP but I still can’t find anything about ways other than RDTSC(P).😔

4

12

semi-related, but various popular packers use rdtsc for timing things to detect debuggers, so disabling it would've broke backwards compatibility

7:46 PM · Sep 9, 2019