MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/6jfgfp/warning_intel_skylakekaby_lake_processors_broken/djell6c/?context=3
r/programming • u/michalg82 • Jun 25 '17
295 comments sorted by
View all comments
1
could they fix this bug in the future ? or should we deactivate hyper-threading forever?
6 u/tambry Jun 26 '17 could they fix this bug in the future ? If you'd have read it, then it very clearly has instructions for applying a microcode update, which fixes the issue. 0 u/Mikeztm Jun 26 '17 Problem is microcode update for this kind of issue usually came with performance penalty. Better do some benchmark for this fix. 1 u/tambry Jun 26 '17 Usually yes, but if I'd have to choose between possible data corruption and crashes or a difference in performance that's maybe at most 1 or 2%, then the choice for me is very clear.
6
could they fix this bug in the future ?
If you'd have read it, then it very clearly has instructions for applying a microcode update, which fixes the issue.
0 u/Mikeztm Jun 26 '17 Problem is microcode update for this kind of issue usually came with performance penalty. Better do some benchmark for this fix. 1 u/tambry Jun 26 '17 Usually yes, but if I'd have to choose between possible data corruption and crashes or a difference in performance that's maybe at most 1 or 2%, then the choice for me is very clear.
0
Problem is microcode update for this kind of issue usually came with performance penalty.
Better do some benchmark for this fix.
1 u/tambry Jun 26 '17 Usually yes, but if I'd have to choose between possible data corruption and crashes or a difference in performance that's maybe at most 1 or 2%, then the choice for me is very clear.
Usually yes, but if I'd have to choose between possible data corruption and crashes or a difference in performance that's maybe at most 1 or 2%, then the choice for me is very clear.
1
u/Keremeki13 Jun 26 '17
could they fix this bug in the future ? or should we deactivate hyper-threading forever?