Revision f54ae69bafa16434ce46bc2f1fe556bce4d23650 authored by Andres Salomon on 09 February 2008, 22:24:08 UTC, committed by Thomas Gleixner on 09 February 2008, 22:24:08 UTC
We *really* don't want to be reading MFGPTx_SETUP and writing back those values. What we want to be doing is clearing CMP1 and CMP2 unconditionally; otherwise, we have races where CMP1 and/or CMP2 fire after we've read MFGPTx_SETUP. They can also fire between when we've written ~CNTEN to the register, and when the new register values get copied to the timer's version of the register. By clearing both fields, we're okay. Signed-off-by: Andres Salomon <dilinger@debian.org> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
1 parent f087515
| File | Mode | Size |
|---|---|---|
| keys | ||
| selinux | ||
| smack | ||
| Kconfig | -rw-r--r-- | 4.3 KB |
| Makefile | -rw-r--r-- | 660 bytes |
| capability.c | -rw-r--r-- | 2.3 KB |
| commoncap.c | -rw-r--r-- | 15.6 KB |
| dummy.c | -rw-r--r-- | 26.6 KB |
| inode.c | -rw-r--r-- | 9.0 KB |
| root_plug.c | -rw-r--r-- | 3.0 KB |
| security.c | -rw-r--r-- | 27.4 KB |
Computing file changes ...
