News for hackers. Stuff that matters.
Re:Windows 10 on ARM by vardump on Thursday May 11, 2017 @04:05PM (#14319044)
That's an excellent point.

I hope the answer is not "by restricting all emulated threads to one CPU core".

Re:Windows 10 on ARM by vvanders on Thursday May 11, 2017 @05:22PM (#14319646)
My off-the-cuff guess is they just force a memory/inst fence where x86 makes guarantees which is a bit better but still incurs some overhead.

Visual Studio used to(probably still does) this around volatile for x86 which leads to fun bugs when you port to ARM/etc.

Re:Windows 10 on ARM by monocasa on Thursday May 11, 2017 @06:17PM (#14319963)
That'd basically be putting a barrier on every memory access though.
Re:Windows 10 on ARM by StillBored on Friday May 12, 2017 @06:43PM (#14328533)
Nah, because ideally most applications are using library/system services to fence their data structures. For the remaining cases the apps could be marked with a new application compatibility flag (this feature already exists in windows for older apps) which adds additional checking that flags pages which are being accessed from multiple contexts as requiring additional emulator level sequencing. There are ton of strategies here, which could be as simple as basically disabling multi threading in the emulator or a page ownership ping/pong, etc.