[lkml]   [2009]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Q: smp.c && barriers (Was: [PATCH 1/4] generic-smp: remove single ipi fallback for smp_call_function_many())

an off-list comment pointed out this piece of information as

A WRMSR to one of the x2APIC MSRs (0000_0800h...0000_0BFFh) is
not guaranteed to be serializing.

So i suspect we should just enclose it in smp_mb() pairs to make
sure it's a full barrier in both directions?

Although since it's an explicitly async mechanism with no
ordering expectations whatsoever, just doing an smp_mb() before
it should be enough, to make sure the IPI can never arrive to
another CPU/core faster than the event-horizon/visibility of
preceding operations.


 \ /
  Last update: 2009-02-18 18:09    [W:0.132 / U:9.116 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site