Re: [PATCH 0/5] MR3103: server: Create and use a desktop shared mapping for GetCursorPos.

[Rémi Bernon (＠rbernon)]

On Mon Jun 19 13:25:54 2023 +0000, Jinoh Kang wrote:
> A compiler barrier is (still) required regardless of whether or not the
> underlying architecture has strong memory ordering semantics.
> #define __SHARED_READ_FENCE __asm__ __volatile__( "" ::: "memory" )

I think that it's actually not needed for the same reasons as described below: everything that is accessed in between is volatile.