2 ms·
ARMs have a more relaxed memory model than x86 so that would be a complication, though I suppose you could just have the decoder put barriers everywhere. x86 i
by Symmetry 6y ago
ARMs have a more relaxed memory model than x86 so that would be a complication, though I suppose you could just have the decoder put barriers everywhere.
x86 is infamously hard to decode, though. Often you speed it up by tagging instruction boundaries in the L1$ which you wouldn't have in the Apple ARM devices by default. If you're willing to just decode one x86 instruction per cycle I suppose the overhead wouldn't be unreasonable.
- monocasa 6y agoYou could also just pin each x86 process to a single core, then you don't have to worry about the memory model. And I've seen some x86 uarchs that tag boundaries in L1, but I've seen some that don't too. I wouldn't consider it a blocker.