| 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
| ||
|
Message-ID: <33307c790809231250y298ede7cqbee5a613ed6dbad5@mail.gmail.com> Date: Tue, 23 Sep 2008 12:50:40 -0700 From: "Martin Bligh" <mbligh@...gle.com> To: "Thomas Gleixner" <tglx@...utronix.de> Cc: "Masami Hiramatsu" <mhiramat@...hat.com>, "Linus Torvalds" <torvalds@...ux-foundation.org>, "Mathieu Desnoyers" <compudj@...stal.dyndns.org>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, "Steven Rostedt" <rostedt@...dmis.org>, darren@...art.com, "Frank Ch. Eigler" <fche@...hat.com>, systemtap-ml <systemtap@...rces.redhat.com> Subject: Re: Unified tracing buffer >> > Yup, explains your TSC observation. Nothing we can do about. Broken by >> > system design :( Welcome in the wonderful world of Inhell/BIOS/ACPI ! >> >> We have linux patches that sync the TSC on exit_idle. I'll see if I can get >> Michael to send them out. > > Are you sure that they sync it precicely enough that there is no user > space observable way of time going backwards between cores ? I think the tolerance is about 500 cycles. If that's not sufficient, I guess we'll have to either live with some slight misordering (which people have pointed out is kind of inevitable anyway) on these broken machines? It was sufficient for what we were using it for, but maybe not for everyone. -- 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/
Powered by blists - more mailing lists