aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/util/scripting-engines/trace-event-perl.c
diff options
context:
space:
mode:
authorToshi Kani <[email protected]>2015-07-16 23:23:14 +0000
committerThomas Gleixner <[email protected]>2015-07-22 15:20:33 +0000
commit1c9cf9b211030a454a84cbc1cb15b82d9aa49011 (patch)
tree0f37223b092bf69c6a89d13eb2fc18dacb54115d /tools/perf/util/scripting-engines/trace-event-perl.c
parentMerge tag 'efi-urgent' of git://git.kernel.org/pub/scm/linux/kernel/git/mflem... (diff)
downloadkernel-1c9cf9b211030a454a84cbc1cb15b82d9aa49011.tar.gz
kernel-1c9cf9b211030a454a84cbc1cb15b82d9aa49011.zip
x86/mm: Move warning from __ioremap_check_ram() to the call site
__ioremap_check_ram() has a WARN_ONCE() which is emitted when the given pfn range is not RAM. The warning is bogus in two aspects: - it never triggers since walk_system_ram_range() only calls __ioremap_check_ram() for RAM ranges. - the warning message is wrong as it says: "ioremap on RAM' after it established that the pfn range is not RAM. Move the WARN_ONCE() to __ioremap_caller(), and update the message to include the address range so we get an actual warning when something tries to ioremap system RAM. [ tglx: Massaged changelog ] Signed-off-by: Toshi Kani <[email protected]> Reviewed-by: Dan Williams <[email protected]> Cc: Roland Dreier <[email protected]> Cc: Luis R. Rodriguez <[email protected]> Cc: H. Peter Anvin <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: Borislav Petkov <[email protected]> Cc: [email protected] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-perl.c')
0 files changed, 0 insertions, 0 deletions