Messages in this thread | | | Date | Mon, 14 Feb 2011 13:46:00 -0800 (PST) | Subject | Re: [PATCH 0/2] jump label: 2.6.38 updates | From | David Miller <> |
| |
From: Steven Rostedt <rostedt@goodmis.org> Date: Mon, 14 Feb 2011 16:39:36 -0500
> Thus it is not about global, as global is updated by normal means and > will update the caches. atomic_t is updated via the ll/sc that ignores > the cache and causes all this to break down. IOW... broken hardware ;)
I don't see how cache coherency can possibly work if the hardware behaves this way.
In cache aliasing situations, yes I can understand a L1 cache visibility issue being present, but with kernel only stuff that should never happen otherwise we have a bug in the arch cache flushing support.
| |