2 comments
> The fix is to set bit 13 of MCSR24 to 1. MCSR24 is an internal CSR whose function is not described in the manual. After setting this bit, the lost update no longer occurs. Testing showed the performance loss is very small: single-core performance is unaffected, and multi-core performance drops only slightly.<p>Presumably this is a so-called “chicken bit”.
> Presumably this is a so-called “chicken bit”.<p>For those who are out of the loop:<p>> <a href="https://lwn.net/Articles/744840/" rel="nofollow">https://lwn.net/Articles/744840/</a><p>See also<p>> <a href="https://en.wiktionary.org/wiki/chicken_bit" rel="nofollow">https://en.wiktionary.org/wiki/chicken_bit</a><p>(click on "quotations") for a list of scientific texts in which this term occurs.
Famously, the first GPS satellites had one of these, in case Einstein was wrong...<p><a href="https://www.quora.com/Why-did-the-GPS-system-initially-resist-using-General-relativity-corrections-and-what-changed-after-they-were-applied#AZtGs" rel="nofollow">https://www.quora.com/Why-did-the-GPS-system-initially-resis...</a><p>He wasn't.
more like out of the coop
Pretty much the definition of.<p>Some optimization that turned out to be buggy had a disable bit in an undocumented register.
Wang Miao? Is this the fault of sophons?