aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorPekka Paalanen <pq@iki.fi>2009-01-03 14:23:51 -0500
committerIngo Molnar <mingo@elte.hu>2009-02-15 14:03:28 -0500
commit6bc5c366b1a45ca18fba6851f62db5743b3f6db5 (patch)
treec3e2a092760b2eca5ff052cbea77cc84502b8016 /kernel
parent391b170f10e669dd429aa47bce998c2fa839404c (diff)
trace: mmiotrace to the tracer menu in Kconfig
Impact: cosmetic change in Kconfig menu layout This patch was originally suggested by Peter Zijlstra, but seems it was forgotten. CONFIG_MMIOTRACE and CONFIG_MMIOTRACE_TEST were selectable directly under the Kernel hacking / debugging menu in the kernel configuration system. They were present only for x86 and x86_64. Other tracers that use the ftrace tracing framework are in their own sub-menu. This patch moves the mmiotrace configuration options there. Since the Kconfig file, where the tracer menu is, is not architecture specific, HAVE_MMIOTRACE_SUPPORT is introduced and provided only by x86/x86_64. CONFIG_MMIOTRACE now depends on it. Signed-off-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel')
-rw-r--r--kernel/trace/Kconfig23
1 files changed, 23 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index e2a4ff6fc3a..58a93fbd68a 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -302,4 +302,27 @@ config FTRACE_STARTUP_TEST
302 functioning properly. It will do tests on all the configured 302 functioning properly. It will do tests on all the configured
303 tracers of ftrace. 303 tracers of ftrace.
304 304
305config MMIOTRACE
306 bool "Memory mapped IO tracing"
307 depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI
308 select TRACING
309 help
310 Mmiotrace traces Memory Mapped I/O access and is meant for
311 debugging and reverse engineering. It is called from the ioremap
312 implementation and works via page faults. Tracing is disabled by
313 default and can be enabled at run-time.
314
315 See Documentation/tracers/mmiotrace.txt.
316 If you are not helping to develop drivers, say N.
317
318config MMIOTRACE_TEST
319 tristate "Test module for mmiotrace"
320 depends on MMIOTRACE && m
321 help
322 This is a dumb module for testing mmiotrace. It is very dangerous
323 as it will write garbage to IO memory starting at a given address.
324 However, it should be safe to use on e.g. unused portion of VRAM.
325
326 Say N, unless you absolutely know what you are doing.
327
305endmenu 328endmenu