STOP DOING SPECULATIVE EXECUTION
INSTRUCTIONS WERE NOT MEANT TO HAVE REVERSIBLE SIDE EFFECTS
STOP DOING SPECULATIVE EXECUTION
INSTRUCTIONS WERE NOT MEANT TO HAVE REVERSIBLE SIDE EFFECTS
@ljrk @mjg59 Sadly most of the teams doing performance oriented riscv designs are on the speculative bandwagon. 😫 🤦
@mjg59 Maybe we should follow-through with a "fully" functional CPU without side-effects, by now the perf difference can't be that big, and we could theoretically always do speculation there, safely :-p
@mjg59 @0xabad1dea THEY HAVE PLAYED US FOR ABSOLUTE FOOLS
AND THEN REALIZED THEIR MISTAKE AND WE WERE NONE THE WISER
YOUR CACHE LINES ARE PRIMED BY EVENTS THAT NEVER HAPPENED
FOR SECURITY BAIT AND SWITCH THE CPU INTO NOT MAKING A CALL WE CONTROL INSTEAD OF NOT MAKING A CALL AN ATTACKER WOULD CONTROL
STATEMENTS DREAMED UP BY THE UTTERLY DERANGED
@mjg59 All right, is there a way that we software developers can disable all speculative execution on our own machines so we can find out the new performance targets that we'll eventually have to meet?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.