pastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 2 years agoSome Mnemonicssh.itjust.worksexternal-linkmessage-square19linkfedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkSome Mnemonicssh.itjust.workspastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 2 years agomessage-square19linkfedilink
minus-square9point6@lemmy.worldlinkfedilinkarrow-up0·2 years agoI still don’t know why this architecture went for a Double XOR as the NOP, I guess they were just flexing that the reference chip design could do both in a single cycle
minus-squarepancake@lemmygrad.mllinkfedilinkarrow-up0·2 years agoWhen returning from kernel code, one should issue Drop Execution Ring Privileges, of course.
I still don’t know why this architecture went for a Double XOR as the NOP, I guess they were just flexing that the reference chip design could do both in a single cycle
When returning from kernel code, one should issue Drop Execution Ring Privileges, of course.