Comment Re:How Adorable (Score 1) 47
The thing is, there is a very easy way to track the chips, just a very hard way to know the final destination especially if intermediaries just sit on them for a time.
Like the easiest tracking mechanism is to have a mask rom part of each chip have a serial number (remember when this was a big deal with the pentium III?) and production date that is also then read from the chip and printed on the chip when it's packaged. Then when the drivers (for cpu/gpu/ram parts) are first turned on a second write-once space in each chip is written with the system ID they were first installed to. So for a GPU the actual high performance mode will not activate if the system has missing or mismatched ID's, and for CPU's the clock speeds will stay locked at the lowest stable setting.
This would also prevent remarking chips.
When the system "calls home" to verify the id's and the driver matches, it writes the final rom handshake that says what it was approved to work with. If any hardware is replaced at this point, it will drop back to the lowest performance mode until checked again.
The downside here is the same one we see when flash chips are tampered with to have a capacity they do not have, people will pair them in the high performance mode, take the screenshots and whatnot and then part out the system and sell them individually and the final buyer is a victim.
Consumer hardware you do the same thing, but you have a prosumer BIOS feature that basically goes "ignore performance check requirement" which then displays a warning like " Performance check not enabled, hardware will operate at it's highest performance mode after a warm up period, and reduce performance if the system does not shut down cleanly" which basically just keeps an error/crash counter in NVRAM and any time the PC is rebooted it checks if the gpu driver version changed. If there is crash number greater than 0 between driver versions it slows down the clock speed stepping until it finds the crashing clock speeds and doesn't move past it until the driver changes or the driver is told to "reset performance counter".
Having the performance check obeyed will instead "call home" to report the crashes with each driver version and hardware id's. This allows the manufacturer to update driver compatibility matching, blacklist certain hardware configurations, and geolocate hardware that has been stolen/re-directed. It does not allow for remote disablement, as this is the hardware calling home when the driver versions change, or hardware changes, which is something that large data center installs won't be doing.
But also, who cares ultimately. I'm in favor of the minimal tracking mechanic to prevent remarking/counterfeiting of hardware that then ends up on temu/ebay but all tracking mechanics are a double-edged sword where it can be used maliciously to track journalists and celebrities doing work outside their home.