News for hackers. Stuff that matters.
Re:An introduction to reverse-engineering x86 microcode and ... by jws on Thursday December 28, 2017 @11:27PM (#16027520)
I wonder about robustness. Can the microcode physically destroy the CPU? Consider driving a bus line both high and low simultaneously from two sources. That puts transistors which ordinarily spurt out a little current to overcome capacitance into a continuous maximum current situation. Compared to maximum toggle rate in normal operation, (50% duty cycle for a transistor, exponentially decaying current when on), I’ll estimate this will easily average four times the current.

The development cycle could be littered with dead processors, but worse for Intel, if a widely used microcode has a very infrequent chip stressing flaw it will manifest as “Intel chips aren’t reliable.”

Re:An introduction to reverse-engineering x86 microcode and ... by sannee on Friday December 29, 2017 @06:37AM (#16028967)
I don't think that tri-state logic is used in ICs anymore (?).

EDIT: http://vswww.kaist.ac.kr/ENGLISH/old_lecture/ee878-2002/lect...

It probably does not imply that the chip is indestructible through microcode though.

Re:An introduction to reverse-engineering x86 microcode and ... by marcosdumay on Friday December 29, 2017 @10:47AM (#16029991)
That paper is about a different concept only loosely related to what DavidBuchanan seems to be talking about.

Selecting a register through a tri-state based bus demands a circuit with a O(1) critical path. Selecting a register through a logical selector demands a circuit with O(log n) critical path, and a large constant factor.

Re:An introduction to reverse-engineering x86 microcode and ... by DavidBuchanan on Friday December 29, 2017 @06:45AM (#16028997)
How do busses work without tri-state logic?
Re:An introduction to reverse-engineering x86 microcode and ... by vanjoe on Friday December 29, 2017 @10:49AM (#16030010)
Arbitration and multiplexing