On Tue, 21 Oct 2014, Aurelien Jarno wrote: > I feel sad that the lock elision code can't really be disabled without > using additional patches that are not even upstream. I have tested your > blacklist patch, and it works fine on the few systems I have tested. > I'll therefore go that way.
Thank you. For the record, the microcode update side of this issue has been uploaded to non-free unstable two days ago (intel-microcode 3.20140913.1). Unfortunately, it cannot help users that don't enable non-free. As for the lock elision code not being easy to disable, I am actually worried the elision code in glibc 2.19 might not be mature enough. But that's the glibc team's call, not mine. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
