| ▲ | zie1ony 2 hours ago | ||||||||||||||||
At my uni, 15 years ago, one postdoc reverse engineered NVIDIA chip and wrote more performant compiler. He did that by connecting oscyloscops to all chip's outputs and started with applying random current on inputs. Using ML and his genius he rediscoverd all opcodes including a few hidden ones. Eventually he got hired by some company that was doing a lot of GPU on supercomputers. | |||||||||||||||||
| ▲ | inigyou 2 hours ago | parent | next [-] | ||||||||||||||||
You can't do that by applying random inputs to any single-chip GPU - it has far too much state. I can see that perhaps it worked on some of the early multi-chip cards - where one chip was a texture sampler, and so on. You'll have more luck reverse engineering the software driver first. They're not hidden, you can just open the driver files in Ghidra, the almost-universal tool for open-sourcing proprietary code. Hidden opcodes can be discovered first by just trying all the opcodes you couldn't discover any other way. You only need to go to the physical level if they're really hidden. | |||||||||||||||||
| |||||||||||||||||
| ▲ | tverbeure an hour ago | parent | prev | next [-] | ||||||||||||||||
There is absolutely no way that happened. 15 years ago, we're talking Fermi class GPUs and chips with hundreds of millions of bits of on-chip state and much more if you include the DRAM. You can't tease out the right information by applying random inputs. Which input would you even use? The PCIe interface? You'd first "randomly" need to get past its complex training sequences... Your postdoc probably wrote micro-benchmarks of some sort. That is a common technique. | |||||||||||||||||
| |||||||||||||||||
| ▲ | pixelatedindex 31 minutes ago | parent | prev [-] | ||||||||||||||||
“oscyloscops” is a way better spelling I gotta say. | |||||||||||||||||