diff options
author | Pekka Paalanen <pq@iki.fi> | 2009-01-03 14:23:51 -0500 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-01-10 22:01:24 -0500 |
commit | fe6f90e57fd31af8daca534ea01db2e5666c15da (patch) | |
tree | 3d1d96af9f7f59aaa884b1b7aa67d21b24929f6d /kernel/trace/Kconfig | |
parent | 5d2ad3316e29ad218f98d66b9c0ce6d4bcd05b77 (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/trace/Kconfig')
-rw-r--r-- | kernel/trace/Kconfig | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 1c0b7504cab3..944239296f13 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig | |||
@@ -323,4 +323,27 @@ config FTRACE_STARTUP_TEST | |||
323 | functioning properly. It will do tests on all the configured | 323 | functioning properly. It will do tests on all the configured |
324 | tracers of ftrace. | 324 | tracers of ftrace. |
325 | 325 | ||
326 | config MMIOTRACE | ||
327 | bool "Memory mapped IO tracing" | ||
328 | depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI | ||
329 | select TRACING | ||
330 | help | ||
331 | Mmiotrace traces Memory Mapped I/O access and is meant for | ||
332 | debugging and reverse engineering. It is called from the ioremap | ||
333 | implementation and works via page faults. Tracing is disabled by | ||
334 | default and can be enabled at run-time. | ||
335 | |||
336 | See Documentation/tracers/mmiotrace.txt. | ||
337 | If you are not helping to develop drivers, say N. | ||
338 | |||
339 | config MMIOTRACE_TEST | ||
340 | tristate "Test module for mmiotrace" | ||
341 | depends on MMIOTRACE && m | ||
342 | help | ||
343 | This is a dumb module for testing mmiotrace. It is very dangerous | ||
344 | as it will write garbage to IO memory starting at a given address. | ||
345 | However, it should be safe to use on e.g. unused portion of VRAM. | ||
346 | |||
347 | Say N, unless you absolutely know what you are doing. | ||
348 | |||
326 | endmenu | 349 | endmenu |