Commit 6bc5c366 authored by Pekka Paalanen's avatar Pekka Paalanen Committed by Ingo Molnar
Browse files

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: default avatarPekka Paalanen <pq@iki.fi>
Signed-off-by: default avatarSteven Rostedt <srostedt@redhat.com>
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent 391b170f

arch/x86/Kconfig.debug

+2 −22
Original line number Diff line number Diff line
@@ -174,28 +174,8 @@ config IOMMU_LEAK 
	  Add a simple leak tracer to the IOMMU code. This is useful when you

	  are debugging a buggy device driver that leaks IOMMU mappings.



config MMIOTRACE

	bool "Memory mapped IO tracing"

	depends on DEBUG_KERNEL && PCI

	select TRACING

	help

	  Mmiotrace traces Memory Mapped I/O access and is meant for

	  debugging and reverse engineering. It is called from the ioremap

	  implementation and works via page faults. Tracing is disabled by

	  default and can be enabled at run-time.



	  See Documentation/tracers/mmiotrace.txt.

	  If you are not helping to develop drivers, say N.



config MMIOTRACE_TEST

	tristate "Test module for mmiotrace"

	depends on MMIOTRACE && m

	help

	  This is a dumb module for testing mmiotrace. It is very dangerous

	  as it will write garbage to IO memory starting at a given address.

	  However, it should be safe to use on e.g. unused portion of VRAM.



	  Say N, unless you absolutely know what you are doing.

config HAVE_MMIOTRACE_SUPPORT

	def_bool y



#

# IO delay types:

kernel/trace/Kconfig

+23 −0
Original line number Diff line number Diff line
@@ -302,4 +302,27 @@ config FTRACE_STARTUP_TEST 
	  functioning properly. It will do tests on all the configured

	  tracers of ftrace.



config MMIOTRACE

	bool "Memory mapped IO tracing"

	depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI

	select TRACING

	help

	  Mmiotrace traces Memory Mapped I/O access and is meant for

	  debugging and reverse engineering. It is called from the ioremap

	  implementation and works via page faults. Tracing is disabled by

	  default and can be enabled at run-time.



	  See Documentation/tracers/mmiotrace.txt.

	  If you are not helping to develop drivers, say N.



config MMIOTRACE_TEST

	tristate "Test module for mmiotrace"

	depends on MMIOTRACE && m

	help

	  This is a dumb module for testing mmiotrace. It is very dangerous

	  as it will write garbage to IO memory starting at a given address.

	  However, it should be safe to use on e.g. unused portion of VRAM.



	  Say N, unless you absolutely know what you are doing.



endmenu

CRA Git | Maintained and supported by SUSTech CRA and CCSE