I have a few issues with the post you're referring to. It seems to completely ignore the existence of constant_tsc and invariant_tsc. The problems it talks about do not exist on modern day platforms; it's just an outdated post.
http://btorpey.github.io/blog/2014/02/18/clock-sources-in-linux/ https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/7/html/reference_guide/chap-timestamping#sect-Hardware_clocks https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/tsc-resynchronization On Wed, 4 Sep 2019, 04:09 Eddie, <[email protected]> wrote: > having nothing in the kernel cmdline is when I was getting drift. > "tsc=reliable" worked (no drift), but tsc is a much less preferable clock > source in modern platforms. see https://superuser.com/a/393978/68374 > > per debian 10 advice, as seen in dmesg, I am sticking with tsc=unstable > > -- > You received this message because you are subscribed to the Google Groups > "mechanical-sympathy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/mechanical-sympathy/711aaed9-032b-4618-90f2-d8e79d700148%40googlegroups.com > <https://groups.google.com/d/msgid/mechanical-sympathy/711aaed9-032b-4618-90f2-d8e79d700148%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/mechanical-sympathy/CAHNMKAo7r7AJTdCTob574Psw4UR5vDV4hMCiPDk%3D81fKEVmaMQ%40mail.gmail.com.
