aboutsummaryrefslogtreecommitdiff
path: root/arch/x86/kvm/lapic.h
diff options
context:
space:
mode:
authorH. Peter Anvin2012-01-09 19:33:24 -0800
committerH. Peter Anvin2012-01-09 19:33:24 -0800
commit8030c36d13f030103356709e63638678fdc66fdc (patch)
treef50b2e91261697914ab8ff4745b3a862f3a275e0 /arch/x86/kvm/lapic.h
parentda517a08ac5913cd80ce3507cddd00f2a091b13c (diff)
x86, atomic: atomic64_read() take a const pointer
atomic64_read() doesn't actually write anything (as far as the C environment is concerned... the CPU does actually write but that's an implementation quirk), so it should take a const pointer. This does NOT mean that it is safe to use atomic64_read() on an object in readonly storage (it will trap!) Reported-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: H. Peter Anvin <hpa@zytor.com> Link: http://lkml.kernel.org/r/20120109165859.1879abda.akpm@linux-foundation.org
Diffstat (limited to 'arch/x86/kvm/lapic.h')
0 files changed, 0 insertions, 0 deletions