5 ms·
Think that whole major, unpatchable security flaw thing could also play a part? I could see them wanting to put distance between themselves on that fast too.
by CSSer 2y ago
Think that whole major, unpatchable security flaw thing could also play a part? I could see them wanting to put distance between themselves on that fast too.
- aurareturn 2y agoI don't think so. I think M4 was planned years in advance to debut around this time. You can't change this stuff in a few months.
- saagarjha 2y agoI don’t recall any that affected silicon?
- kevlened 2y agoKey extraction from the HSM. It's unclear if this was ultimately patched in the kernel, but it appears patchable. [1] https://gofetch.fail/ https://gofetch.fail/ [2] https://social.treehouse.systems/@marcan/112238385679496096 https://social.treehouse.systems/@marcan/112238385679496096
- saagarjha 2y agoDefinitely not the HSM, this only affects the AP
- 1123581321 2y agoM3s have a flag to disable the caching vulnerable to GoFetch on p-cores. M1s and M2s are the ones that have no mitigation besides running workloads on slower e-cores.
- lwkl 2y agoThat‘s not true DMP can be disabled on M2 chips and probably also on the M1 chips. This was found by Hector Martin (@marcan) and will probably supported in Asahi Linux.
- 1123581321 2y agoThat's great news. Direct link for anyone else not up to date: https://social.treehouse.systems/@marcan/112238385679496096 https://social.treehouse.systems/@marcan/112238385679496096