[mirror_ubuntu-eoan-kernel.git] / arch / arm / Kconfig.debug

menu "Kernel hacking"

source "lib/Kconfig.debug"

config STRICT_DEVMEM
	bool "Filter access to /dev/mem"
	depends on MMU
	---help---
	  If this option is disabled, you allow userspace (root) access to all
	  of memory, including kernel and userspace memory. Accidental
	  access to this is obviously disastrous, but specific access can
	  be used by people debugging the kernel.

	  If this option is switched on, the /dev/mem file only allows
	  userspace access to memory mapped peripherals.

          If in doubt, say Y.

# RMK wants arm kernels compiled with frame pointers or stack unwinding.
# If you know what you are doing and are willing to live without stack
# traces, you can get a slightly smaller kernel by setting this option to
# n, but then RMK will have to kill you ;).
config FRAME_POINTER
	bool
	depends on !THUMB2_KERNEL
	default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER
	help
	  If you say N here, the resulting kernel will be slightly smaller and
	  faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
	  when a problem occurs with the kernel, the information that is
	  reported is severely limited.

config ARM_UNWIND
	bool "Enable stack unwinding support (EXPERIMENTAL)"
	depends on AEABI && EXPERIMENTAL
	default y
	help
	  This option enables stack unwinding support in the kernel
	  using the information automatically generated by the
	  compiler. The resulting kernel image is slightly bigger but
	  the performance is not affected. Currently, this feature
	  only works with EABI compilers. If unsure say Y.

config OLD_MCOUNT
	bool
	depends on FUNCTION_TRACER && FRAME_POINTER
	default y

config DEBUG_USER
	bool "Verbose user fault messages"
	help
	  When a user program crashes due to an exception, the kernel can
	  print a brief message explaining what the problem was. This is
	  sometimes helpful for debugging but serves no purpose on a
	  production system. Most people should say N here.

	  In addition, you need to pass user_debug=N on the kernel command
	  line to enable this feature.  N consists of the sum of:

	      1 - undefined instruction events
	      2 - system calls
	      4 - invalid data aborts
	      8 - SIGSEGV faults
	     16 - SIGBUS faults

# These options are only for real kernel hackers who want to get their hands dirty.
config DEBUG_LL
	bool "Kernel low-level debugging functions (read help!)"
	depends on DEBUG_KERNEL
	help
	  Say Y here to include definitions of printascii, printch, printhex
	  in the kernel.  This is helpful if you are debugging code that
	  executes before the console is initialized.

	  Note that selecting this option will limit the kernel to a single
	  UART definition, as specified below. Attempting to boot the kernel
	  image on a different platform *will not work*, so this option should
	  not be enabled for kernels that are intended to be portable.

choice
	prompt "Kernel low-level debugging port"
	depends on DEBUG_LL

	config DEBUG_LL_UART_NONE
		bool "No low-level debugging UART"
		help
		  Say Y here if your platform doesn't provide a UART option
		  below. This relies on your platform choosing the right UART
		  definition internally in order for low-level debugging to
		  work.

	config DEBUG_ICEDCC
		bool "Kernel low-level debugging via EmbeddedICE DCC channel"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the EmbeddedICE macrocell's DCC channel using
		  co-processor 14. This is known to work on the ARM9 style ICE
		  channel and on the XScale with the PEEDI.

		  Note that the system will appear to hang during boot if there
		  is nothing connected to read from the DCC.

	config DEBUG_SEMIHOSTING
		bool "Kernel low-level debug output via semihosting I"
		help
		  Semihosting enables code running on an ARM target to use
		  the I/O facilities on a host debugger/emulator through a
		  simple SVC calls. The host debugger or emulator must have
		  semihosting enabled for the special svc call to be trapped
		  otherwise the kernel will crash.

		  This is known to work with OpenOCD, as wellas
		  ARM's Fast Models, or any other controlling environment
		  that implements semihosting.

		  For more details about semihosting, please see
		  chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.

	config AT91_DEBUG_LL_DBGU0
		bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
		depends on HAVE_AT91_DBGU0

	config AT91_DEBUG_LL_DBGU1
		bool "Kernel low-level debugging on 9263, 9g45 and cap9"
		depends on HAVE_AT91_DBGU1

	config DEBUG_FOOTBRIDGE_COM1
		bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
		depends on FOOTBRIDGE
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the 8250 at PCI COM1.

	config DEBUG_DC21285_PORT
		bool "Kernel low-level debugging messages via footbridge serial port"
		depends on FOOTBRIDGE
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port in the DC21285 (Footbridge).

	config DEBUG_CLPS711X_UART1
		bool "Kernel low-level debugging messages via UART1"
		depends on ARCH_CLPS711X
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the first serial port on these devices.

	config DEBUG_CLPS711X_UART2
		bool "Kernel low-level debugging messages via UART2"
		depends on ARCH_CLPS711X
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the second serial port on these devices.

	config DEBUG_HIGHBANK_UART
		bool "Kernel low-level debugging messages via Highbank UART"
		depends on ARCH_HIGHBANK
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the UART on Highbank based devices.

	config DEBUG_IMX1_UART
		bool "i.MX1 Debug UART"
		depends on SOC_IMX1
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX1.

	config DEBUG_IMX23_UART
		bool "i.MX23 Debug UART"
		depends on SOC_IMX23
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX23.

	config DEBUG_IMX25_UART
		bool "i.MX25 Debug UART"
		depends on SOC_IMX25
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX25.

	config DEBUG_IMX21_IMX27_UART
		bool "i.MX21 and i.MX27 Debug UART"
		depends on SOC_IMX21 || SOC_IMX27
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX21 or i.MX27.

	config DEBUG_IMX28_UART
		bool "i.MX28 Debug UART"
		depends on SOC_IMX28
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX28.

	config DEBUG_IMX31_IMX35_UART
		bool "i.MX31 and i.MX35 Debug UART"
		depends on SOC_IMX31 || SOC_IMX35
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX31 or i.MX35.

	config DEBUG_IMX51_UART
		bool "i.MX51 Debug UART"
		depends on SOC_IMX51
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX51.

	config DEBUG_IMX50_IMX53_UART
		bool "i.MX50 and i.MX53 Debug UART"
		depends on SOC_IMX50 || SOC_IMX53
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX50 or i.MX53.

	config DEBUG_IMX6Q_UART
		bool "i.MX6Q Debug UART"
		depends on SOC_IMX6Q
		help
		  Say Y here if you want kernel low-level debugging support
		  on i.MX6Q.

	config DEBUG_S3C_UART0
		depends on PLAT_SAMSUNG
		bool "Use S3C UART 0 for low-level debug"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART 0. The port must have been initialised
		  by the boot-loader before use.

		  The uncompressor code port configuration is now handled
		  by CONFIG_S3C_LOWLEVEL_UART_PORT.

	config DEBUG_S3C_UART1
		depends on PLAT_SAMSUNG
		bool "Use S3C UART 1 for low-level debug"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART 1. The port must have been initialised
		  by the boot-loader before use.

		  The uncompressor code port configuration is now handled
		  by CONFIG_S3C_LOWLEVEL_UART_PORT.

	config DEBUG_S3C_UART2
		depends on PLAT_SAMSUNG
		bool "Use S3C UART 2 for low-level debug"
		help
		  Say Y here if you want the debug print routines to direct
		  their output to UART 2. The port must have been initialised
		  by the boot-loader before use.

		  The uncompressor code port configuration is now handled
		  by CONFIG_S3C_LOWLEVEL_UART_PORT.

	config DEBUG_REALVIEW_STD_PORT
		bool "RealView Default UART"
		depends on ARCH_REALVIEW
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port on RealView EB, PB11MP, PBA8
		  and PBX platforms.

	config DEBUG_REALVIEW_PB1176_PORT
		bool "RealView PB1176 UART"
		depends on MACH_REALVIEW_PB1176
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the standard serial port on the RealView
		  PB1176 platform.

	config DEBUG_MSM_UART1
		bool "Kernel low-level debugging messages via MSM UART1"
		depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the first serial port on MSM devices.

	config DEBUG_MSM_UART2
		bool "Kernel low-level debugging messages via MSM UART2"
		depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the second serial port on MSM devices.

	config DEBUG_MSM_UART3
		bool "Kernel low-level debugging messages via MSM UART3"
		depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the third serial port on MSM devices.

	config DEBUG_MSM8660_UART
		bool "Kernel low-level debugging messages via MSM 8660 UART"
		depends on ARCH_MSM8X60
		select MSM_HAS_DEBUG_UART_HS
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port on MSM 8660 devices.

	config DEBUG_MSM8960_UART
		bool "Kernel low-level debugging messages via MSM 8960 UART"
		depends on ARCH_MSM8960
		select MSM_HAS_DEBUG_UART_HS
		help
		  Say Y here if you want the debug print routines to direct
		  their output to the serial port on MSM 8960 devices.

endchoice

config EARLY_PRINTK
	bool "Early printk"
	depends on DEBUG_LL
	help
	  Say Y here if you want to have an early console using the
	  kernel low-level debugging functions. Add earlyprintk to your
	  kernel parameters to enable this console.

config OC_ETM
	bool "On-chip ETM and ETB"
	depends on ARM_AMBA
	help
	  Enables the on-chip embedded trace macrocell and embedded trace
	  buffer driver that will allow you to collect traces of the
	  kernel code.

config ARM_KPROBES_TEST
	tristate "Kprobes test module"
	depends on KPROBES && MODULES
	help
	  Perform tests of kprobes API and instruction set simulation.

endmenu
Commit	Line	Data
1da177e4 LT	1	menu "Kernel hacking"
	2
	3	source "lib/Kconfig.debug"
	4
087aaffc NP	5	config STRICT_DEVMEM
	6	bool "Filter access to /dev/mem"
	7	depends on MMU
	8	---help---
	9	If this option is disabled, you allow userspace (root) access to all
	10	of memory, including kernel and userspace memory. Accidental
	11	access to this is obviously disastrous, but specific access can
	12	be used by people debugging the kernel.
	13
	14	If this option is switched on, the /dev/mem file only allows
	15	userspace access to memory mapped peripherals.
	16
	17	If in doubt, say Y.
	18
adf8b37b	19	# RMK wants arm kernels compiled with frame pointers or stack unwinding.
1da177e4 LT	20	# If you know what you are doing and are willing to live without stack
	21	# traces, you can get a slightly smaller kernel by setting this option to
	22	# n, but then RMK will have to kill you ;).
	23	config FRAME_POINTER
	24	bool
16c79651	25	depends on !THUMB2_KERNEL
0e341af8	26	default y if !ARM_UNWIND \|\| FUNCTION_GRAPH_TRACER
1da177e4 LT	27	help
1da177e4 LT	28	If you say N here, the resulting kernel will be slightly smaller and
adf8b37b CM	29	faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
	30	when a problem occurs with the kernel, the information that is
	31	reported is severely limited.
	32
	33	config ARM_UNWIND
4a50bfe3	34	bool "Enable stack unwinding support (EXPERIMENTAL)"
adf8b37b CM	35	depends on AEABI && EXPERIMENTAL
	36	default y
	37	help
	38	This option enables stack unwinding support in the kernel
	39	using the information automatically generated by the
	40	compiler. The resulting kernel image is slightly bigger but
	41	the performance is not affected. Currently, this feature
	42	only works with EABI compilers. If unsure say Y.
1da177e4	43
09bfafac RV	44	config OLD_MCOUNT
	45	bool
	46	depends on FUNCTION_TRACER && FRAME_POINTER
	47	default y
	48
1da177e4 LT	49	config DEBUG_USER
	50	bool "Verbose user fault messages"
	51	help
	52	When a user program crashes due to an exception, the kernel can
	53	print a brief message explaining what the problem was. This is
	54	sometimes helpful for debugging but serves no purpose on a
	55	production system. Most people should say N here.
	56
	57	In addition, you need to pass user_debug=N on the kernel command
	58	line to enable this feature. N consists of the sum of:
	59
	60	1 - undefined instruction events
	61	2 - system calls
	62	4 - invalid data aborts
	63	8 - SIGSEGV faults
	64	16 - SIGBUS faults
	65
1da177e4 LT	66	# These options are only for real kernel hackers who want to get their hands dirty.
1da177e4 LT	67	config DEBUG_LL
4f5ef922	68	bool "Kernel low-level debugging functions (read help!)"
1da177e4 LT	69	depends on DEBUG_KERNEL
1da177e4 LT	70	help
35efb606	71	Say Y here to include definitions of printascii, printch, printhex
1da177e4 LT	72	in the kernel. This is helpful if you are debugging code that
	73	executes before the console is initialized.
	74
4f5ef922 WD	75	Note that selecting this option will limit the kernel to a single
	76	UART definition, as specified below. Attempting to boot the kernel
	77	image on a different platform will not work, so this option should
	78	not be enabled for kernels that are intended to be portable.
	79
17916b28 WD	80	choice
	81	prompt "Kernel low-level debugging port"
	82	depends on DEBUG_LL
	83
f73765fc WD	84	config DEBUG_LL_UART_NONE
	85	bool "No low-level debugging UART"
	86	help
	87	Say Y here if your platform doesn't provide a UART option
	88	below. This relies on your platform choosing the right UART
	89	definition internally in order for low-level debugging to
	90	work.
	91
6996f425 SB	92	config DEBUG_ICEDCC
	93	bool "Kernel low-level debugging via EmbeddedICE DCC channel"
	94	help
	95	Say Y here if you want the debug print routines to direct
	96	their output to the EmbeddedICE macrocell's DCC channel using
	97	co-processor 14. This is known to work on the ARM9 style ICE
	98	channel and on the XScale with the PEEDI.
	99
f73765fc WD	100	Note that the system will appear to hang during boot if there
f73765fc WD	101	is nothing connected to read from the DCC.
164acf96	102
9b5a146a NP	103	config DEBUG_SEMIHOSTING
	104	bool "Kernel low-level debug output via semihosting I"
	105	help
	106	Semihosting enables code running on an ARM target to use
	107	the I/O facilities on a host debugger/emulator through a
	108	simple SVC calls. The host debugger or emulator must have
	109	semihosting enabled for the special svc call to be trapped
	110	otherwise the kernel will crash.
	111
	112	This is known to work with OpenOCD, as wellas
	113	ARM's Fast Models, or any other controlling environment
	114	that implements semihosting.
	115
	116	For more details about semihosting, please see
	117	chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
	118
13079a73 JCPV	119	config AT91_DEBUG_LL_DBGU0
	120	bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
	121	depends on HAVE_AT91_DBGU0
	122
	123	config AT91_DEBUG_LL_DBGU1
	124	bool "Kernel low-level debugging on 9263, 9g45 and cap9"
	125	depends on HAVE_AT91_DBGU1
	126
164acf96 SB	127	config DEBUG_FOOTBRIDGE_COM1
	128	bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
	129	depends on FOOTBRIDGE
	130	help
	131	Say Y here if you want the debug print routines to direct
	132	their output to the 8250 at PCI COM1.
	133
17916b28 WD	134	config DEBUG_DC21285_PORT
	135	bool "Kernel low-level debugging messages via footbridge serial port"
	136	depends on FOOTBRIDGE
	137	help
	138	Say Y here if you want the debug print routines to direct
	139	their output to the serial port in the DC21285 (Footbridge).
164acf96 SB	140
	141	config DEBUG_CLPS711X_UART1
	142	bool "Kernel low-level debugging messages via UART1"
	143	depends on ARCH_CLPS711X
	144	help
	145	Say Y here if you want the debug print routines to direct
	146	their output to the first serial port on these devices.
17916b28 WD	147
	148	config DEBUG_CLPS711X_UART2
	149	bool "Kernel low-level debugging messages via UART2"
	150	depends on ARCH_CLPS711X
	151	help
	152	Say Y here if you want the debug print routines to direct
	153	their output to the second serial port on these devices.
17916b28	154
220e6cf7 RH	155	config DEBUG_HIGHBANK_UART
	156	bool "Kernel low-level debugging messages via Highbank UART"
	157	depends on ARCH_HIGHBANK
	158	help
	159	Say Y here if you want the debug print routines to direct
	160	their output to the UART on Highbank based devices.
	161
f350b861 SG	162	config DEBUG_IMX1_UART
	163	bool "i.MX1 Debug UART"
	164	depends on SOC_IMX1
	165	help
	166	Say Y here if you want kernel low-level debugging support
	167	on i.MX1.
	168
	169	config DEBUG_IMX23_UART
	170	bool "i.MX23 Debug UART"
	171	depends on SOC_IMX23
	172	help
	173	Say Y here if you want kernel low-level debugging support
	174	on i.MX23.
	175
	176	config DEBUG_IMX25_UART
	177	bool "i.MX25 Debug UART"
	178	depends on SOC_IMX25
	179	help
	180	Say Y here if you want kernel low-level debugging support
	181	on i.MX25.
	182
	183	config DEBUG_IMX21_IMX27_UART
	184	bool "i.MX21 and i.MX27 Debug UART"
	185	depends on SOC_IMX21 \|\| SOC_IMX27
	186	help
	187	Say Y here if you want kernel low-level debugging support
	188	on i.MX21 or i.MX27.
	189
	190	config DEBUG_IMX28_UART
	191	bool "i.MX28 Debug UART"
	192	depends on SOC_IMX28
	193	help
	194	Say Y here if you want kernel low-level debugging support
	195	on i.MX28.
	196
	197	config DEBUG_IMX31_IMX35_UART
	198	bool "i.MX31 and i.MX35 Debug UART"
	199	depends on SOC_IMX31 \|\| SOC_IMX35
	200	help
	201	Say Y here if you want kernel low-level debugging support
	202	on i.MX31 or i.MX35.
	203
	204	config DEBUG_IMX51_UART
	205	bool "i.MX51 Debug UART"
	206	depends on SOC_IMX51
	207	help
	208	Say Y here if you want kernel low-level debugging support
	209	on i.MX51.
	210
	211	config DEBUG_IMX50_IMX53_UART
	212	bool "i.MX50 and i.MX53 Debug UART"
	213	depends on SOC_IMX50 \|\| SOC_IMX53
	214	help
	215	Say Y here if you want kernel low-level debugging support
	216	on i.MX50 or i.MX53.
	217
bac89d75 SG	218	config DEBUG_IMX6Q_UART
	219	bool "i.MX6Q Debug UART"
	220	depends on SOC_IMX6Q
	221	help
	222	Say Y here if you want kernel low-level debugging support
	223	on i.MX6Q.
	224
952aeeb2 WD	225	config DEBUG_S3C_UART0
	226	depends on PLAT_SAMSUNG
	227	bool "Use S3C UART 0 for low-level debug"
	228	help
	229	Say Y here if you want the debug print routines to direct
	230	their output to UART 0. The port must have been initialised
	231	by the boot-loader before use.
	232
	233	The uncompressor code port configuration is now handled
	234	by CONFIG_S3C_LOWLEVEL_UART_PORT.
	235
	236	config DEBUG_S3C_UART1
	237	depends on PLAT_SAMSUNG
	238	bool "Use S3C UART 1 for low-level debug"
	239	help
	240	Say Y here if you want the debug print routines to direct
	241	their output to UART 1. The port must have been initialised
	242	by the boot-loader before use.
	243
	244	The uncompressor code port configuration is now handled
	245	by CONFIG_S3C_LOWLEVEL_UART_PORT.
	246
	247	config DEBUG_S3C_UART2
	248	depends on PLAT_SAMSUNG
	249	bool "Use S3C UART 2 for low-level debug"
	250	help
	251	Say Y here if you want the debug print routines to direct
	252	their output to UART 2. The port must have been initialised
	253	by the boot-loader before use.
	254
	255	The uncompressor code port configuration is now handled
	256	by CONFIG_S3C_LOWLEVEL_UART_PORT.
	257
1285b8f8 WD	258	config DEBUG_REALVIEW_STD_PORT
	259	bool "RealView Default UART"
	260	depends on ARCH_REALVIEW
	261	help
	262	Say Y here if you want the debug print routines to direct
	263	their output to the serial port on RealView EB, PB11MP, PBA8
	264	and PBX platforms.
	265
	266	config DEBUG_REALVIEW_PB1176_PORT
	267	bool "RealView PB1176 UART"
	268	depends on MACH_REALVIEW_PB1176
	269	help
	270	Say Y here if you want the debug print routines to direct
	271	their output to the standard serial port on the RealView
	272	PB1176 platform.
	273
650e3f0d SB	274	config DEBUG_MSM_UART1
	275	bool "Kernel low-level debugging messages via MSM UART1"
	276	depends on ARCH_MSM7X00A \|\| ARCH_MSM7X30 \|\| ARCH_QSD8X50
	277	help
	278	Say Y here if you want the debug print routines to direct
	279	their output to the first serial port on MSM devices.
	280
	281	config DEBUG_MSM_UART2
	282	bool "Kernel low-level debugging messages via MSM UART2"
	283	depends on ARCH_MSM7X00A \|\| ARCH_MSM7X30 \|\| ARCH_QSD8X50
	284	help
	285	Say Y here if you want the debug print routines to direct
	286	their output to the second serial port on MSM devices.
	287
	288	config DEBUG_MSM_UART3
	289	bool "Kernel low-level debugging messages via MSM UART3"
	290	depends on ARCH_MSM7X00A \|\| ARCH_MSM7X30 \|\| ARCH_QSD8X50
	291	help
	292	Say Y here if you want the debug print routines to direct
	293	their output to the third serial port on MSM devices.
	294
a3d3ef9d SB	295	config DEBUG_MSM8660_UART
	296	bool "Kernel low-level debugging messages via MSM 8660 UART"
	297	depends on ARCH_MSM8X60
	298	select MSM_HAS_DEBUG_UART_HS
	299	help
	300	Say Y here if you want the debug print routines to direct
	301	their output to the serial port on MSM 8660 devices.
	302
	303	config DEBUG_MSM8960_UART
	304	bool "Kernel low-level debugging messages via MSM 8960 UART"
	305	depends on ARCH_MSM8960
	306	select MSM_HAS_DEBUG_UART_HS
	307	help
	308	Say Y here if you want the debug print routines to direct
	309	their output to the serial port on MSM 8960 devices.
	310
17916b28 WD	311	endchoice
17916b28 WD	312
93fd03a8 CM	313	config EARLY_PRINTK
	314	bool "Early printk"
	315	depends on DEBUG_LL
	316	help
	317	Say Y here if you want to have an early console using the
	318	kernel low-level debugging functions. Add earlyprintk to your
	319	kernel parameters to enable this console.
	320
c5d6c770 AS	321	config OC_ETM
c5d6c770 AS	322	bool "On-chip ETM and ETB"
53eebb0d	323	depends on ARM_AMBA
c5d6c770 AS	324	help
	325	Enables the on-chip embedded trace macrocell and embedded trace
	326	buffer driver that will allow you to collect traces of the
	327	kernel code.
	328
4189bc71 JM	329	config ARM_KPROBES_TEST
	330	tristate "Kprobes test module"
	331	depends on KPROBES && MODULES
	332	help
	333	Perform tests of kprobes API and instruction set simulation.
	334
1da177e4	335	endmenu