News for hackers. Stuff that matters.
Re:63 Cores Blocked by Seven Instructions by KenanSulayman on Monday October 21, 2019 @04:54AM (#21310367)
Technically this wasn't caused by those instructions but by the spinlocks waiting for the lock to be released. Also "blocked by seven instructions" sounds a bit click-baity.. you can lock the CPU or power off the computer with less than that amount of instructions :-)
Re:63 Cores Blocked by Seven Instructions by saagarjha on Monday October 21, 2019 @05:10AM (#21310432)
Or break it, depending on how old it is:

  f0 0f c7 c8: lock cmpxchg8b eax
Re:63 Cores Blocked by Seven Instructions by Piskvorrr on Monday October 21, 2019 @06:40AM (#21310754)
Does this still bug still bite anywhere? Embedded computing with Pentiums?
Re:63 Cores Blocked by Seven Instructions by lmm on Monday October 21, 2019 @10:26AM (#21312604)
I used a Pentium with that bug as a router up until 2009.
Re:63 Cores Blocked by Seven Instructions by Piskvorrr on Wednesday October 23, 2019 @08:36AM (#21333904)
Yeah, I used to have a similar setup then. That was 10 years ago, though.
Re:63 Cores Blocked by Seven Instructions by ahbyb on Monday October 21, 2019 @06:41AM (#21310761)
It's an invalid instruction, so a compiler wouldn't (shouldn't) ever generate it.
Re:63 Cores Blocked by Seven Instructions by souprock on Monday October 21, 2019 @09:10AM (#21311827)
You can make gcc generate it, and versions of Linux without no-execute support will actually run it. Like so:

int main = 0xc8c70ff0;

Re:63 Cores Blocked by Seven Instructions by ahbyb on Monday October 21, 2019 @09:27AM (#21311985)
Ah, but that's something you do on purpose. What I meant is that it's not a Meltdown-like problem.
Re:63 Cores Blocked by Seven Instructions by brucedawson on Monday October 21, 2019 @11:35PM (#21320174)
Did you read the post? There were no spin locks waiting for the lock to be released. The ~100 threads waiting for the lock were all waiting in an idle state, quite efficiently.

The problem was that the thread that owned the lock was spinning in a seven-instruction loop.

Re:63 Cores Blocked by Seven Instructions by djmips on Monday October 21, 2019 @06:42PM (#21318363)
I think the point is that you have this beast of a computer and the lions share if its power is going to these 7 instructions. It's a bit theatrical way of putting it, but in the article he doesn't actually blame the 7 instructions for the root problem.
Re:63 Cores Blocked by Seven Instructions by slowhand09 on Monday October 21, 2019 @10:09AM (#21312418)
In this case I'm OK with it. It pulled me in long enough to be entertained.