News for hackers. Stuff that matters.
Re:NASM Assembly Language Tutorials by tux3 on Monday January 03, 2022 @09:11PM (#29790322)
Well, there's still plenty of systems you may interface with that sit somewhere between the kernel and the metal!

UEFI software, SMM code, various other pieces of firmware, your cloud provider's hypervisor, the Intel ME, ..

All those things send machine code to the CPU, which is really where bare metal starts. Everything that happens after is hardcoded in silicon (ignoring ucode!)

Re:NASM Assembly Language Tutorials by Koshkin on Monday January 03, 2022 @10:15PM (#29790853)
> ignoring ucode

Which you can’t anymore, because in modern CISC CPUs it is no longer microcode in the original sense but rather machine code for an internal RISC processor. Also, some hardware parts are built using FPGAs. (Basically, we might as well call the Java VM “bare metal.”)

Re:NASM Assembly Language Tutorials by tux3 on Monday January 03, 2022 @10:38PM (#29791014)
Well, it's not that simple, but I'm happy to argue that you can consider machine code the real interface to the hardware, not the undocumented microarchitectural uops.

The translation to macro and micro ops is done in silicon, hardcoded, with the exceptions of instructions that may need to read from MSROM, and the patching system that ucode updates have. That's a small percentage of instructions executed.

And because all of that is hidden from the software, it's not something you can interract with, and it changes with the CPU model. It's internal details, not the external interface (despite some people really writing the machine code specifically with some uop sequence in mind :) )

I'm not sure FPGAs are really the same concept, though. Even if they're reconfigurable, I still consider them hardware, not software code. After all you write FPGA code in HDL :)