Talk:Transactional Synchronization Extensions

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Hardware (Rated C-class, Mid-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
C-Class article C  This article has been rated as C-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.
Taskforce icon
This article is supported by Computer hardware task force (marked as Mid-importance).

The Intel TSX erratum fix is the first "unsafe" Intel microcode update[edit]

An interesting point: The Intel microcode update that disabled TSX is the first microcode update that violates the "microcode updates must be safe at all times" tradition that was in effect since 1995, and this fact is somewhat noteworthy.

Applying the microcode update really disables Intel TSX: it doesn't just clear the relevant cpuid bits, but also causes every Intel TSX instruction to trap with the illegal opcode exception. In a modern Linux distro, this will crash every multithreaded application linked to glibc's libpthread, causing data loss[1]. To be safe, this microcode update must be applied very early at boot, before any programs that might attempt to use the Intel TSX instructions are started. (talk) 14:15, 23 September 2014 (UTC)

Hello! Good remark, I've added it as an external link. — Dsimic (talk | contribs) 04:47, 26 September 2014 (UTC)