2005-04-17 05:20:36 +07:00
|
|
|
menu "Kernel hacking"
|
|
|
|
|
2006-07-03 14:24:43 +07:00
|
|
|
config TRACE_IRQFLAGS_SUPPORT
|
2007-10-25 05:50:43 +07:00
|
|
|
def_bool y
|
2006-07-03 14:24:43 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
|
2008-04-25 04:40:47 +07:00
|
|
|
config NONPROMISC_DEVMEM
|
2008-06-06 03:47:13 +07:00
|
|
|
bool "Filter access to /dev/mem"
|
2008-04-25 04:40:47 +07:00
|
|
|
help
|
2008-06-06 03:47:13 +07:00
|
|
|
If this option is left off, you allow userspace 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 PCI space and the BIOS code and data regions.
|
|
|
|
This is sufficient for dosemu and X and all common users of
|
|
|
|
/dev/mem.
|
|
|
|
|
|
|
|
If in doubt, say Y.
|
2008-04-25 04:40:47 +07:00
|
|
|
|
2008-06-19 01:04:35 +07:00
|
|
|
config X86_VERBOSE_BOOTUP
|
|
|
|
bool "Enable verbose x86 bootup info messages"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Enables the informational output from the decompression stage
|
|
|
|
(e.g. bzImage) of the boot. If you disable this you will still
|
|
|
|
see errors. Disable this if you want silent bootup.
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config EARLY_PRINTK
|
2008-01-30 19:33:06 +07:00
|
|
|
bool "Early printk" if EMBEDDED
|
2005-04-17 05:20:36 +07:00
|
|
|
default y
|
|
|
|
help
|
|
|
|
Write kernel log output directly into the VGA buffer or to a serial
|
|
|
|
port.
|
|
|
|
|
|
|
|
This is useful for kernel debugging when your machine crashes very
|
|
|
|
early before the console code is initialized. For normal operation
|
|
|
|
it is not recommended because it looks ugly and doesn't cooperate
|
|
|
|
with klogd/syslogd or the X server. You should normally N here,
|
|
|
|
unless you want to debug such a crash.
|
|
|
|
|
|
|
|
config DEBUG_STACKOVERFLOW
|
|
|
|
bool "Check for stack overflows"
|
|
|
|
depends on DEBUG_KERNEL
|
2005-07-28 01:44:23 +07:00
|
|
|
help
|
|
|
|
This option will cause messages to be printed if free stack space
|
|
|
|
drops below a certain limit.
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
config DEBUG_STACK_USAGE
|
|
|
|
bool "Stack utilization instrumentation"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Enables the display of the minimum amount of free stack which each
|
|
|
|
task has ever had available in the sysrq-T and sysrq-P debug output.
|
|
|
|
|
|
|
|
This option will slow down process creation somewhat.
|
|
|
|
|
|
|
|
config DEBUG_PAGEALLOC
|
2006-03-25 18:07:22 +07:00
|
|
|
bool "Debug page memory allocations"
|
2008-02-10 05:24:09 +07:00
|
|
|
depends on DEBUG_KERNEL
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
Unmap pages from the kernel linear mapping after free_pages().
|
|
|
|
This results in a large slowdown, but helps to find certain types
|
|
|
|
of memory corruptions.
|
|
|
|
|
2008-01-30 19:33:22 +07:00
|
|
|
config DEBUG_PER_CPU_MAPS
|
|
|
|
bool "Debug access to per_cpu maps"
|
|
|
|
depends on DEBUG_KERNEL
|
x86: cleanup early per cpu variables/accesses v4
* Introduce a new PER_CPU macro called "EARLY_PER_CPU". This is
used by some per_cpu variables that are initialized and accessed
before there are per_cpu areas allocated.
["Early" in respect to per_cpu variables is "earlier than the per_cpu
areas have been setup".]
This patchset adds these new macros:
DEFINE_EARLY_PER_CPU(_type, _name, _initvalue)
EXPORT_EARLY_PER_CPU_SYMBOL(_name)
DECLARE_EARLY_PER_CPU(_type, _name)
early_per_cpu_ptr(_name)
early_per_cpu_map(_name, _idx)
early_per_cpu(_name, _cpu)
The DEFINE macro defines the per_cpu variable as well as the early
map and pointer. It also initializes the per_cpu variable and map
elements to "_initvalue". The early_* macros provide access to
the initial map (usually setup during system init) and the early
pointer. This pointer is initialized to point to the early map
but is then NULL'ed when the actual per_cpu areas are setup. After
that the per_cpu variable is the correct access to the variable.
The early_per_cpu() macro is not very efficient but does show how to
access the variable if you have a function that can be called both
"early" and "late". It tests the early ptr to be NULL, and if not
then it's still valid. Otherwise, the per_cpu variable is used
instead:
#define early_per_cpu(_name, _cpu) \
(early_per_cpu_ptr(_name) ? \
early_per_cpu_ptr(_name)[_cpu] : \
per_cpu(_name, _cpu))
A better method is to actually check the pointer manually. In the
case below, numa_set_node can be called both "early" and "late":
void __cpuinit numa_set_node(int cpu, int node)
{
int *cpu_to_node_map = early_per_cpu_ptr(x86_cpu_to_node_map);
if (cpu_to_node_map)
cpu_to_node_map[cpu] = node;
else
per_cpu(x86_cpu_to_node_map, cpu) = node;
}
* Add a flag "arch_provides_topology_pointers" that indicates pointers
to topology cpumask_t maps are available. Otherwise, use the function
returning the cpumask_t value. This is useful if cpumask_t set size
is very large to avoid copying data on to/off of the stack.
* The coverage of CONFIG_DEBUG_PER_CPU_MAPS has been increased while
the non-debug case has been optimized a bit.
* Remove an unreferenced compiler warning in drivers/base/topology.c
* Clean up #ifdef in setup.c
For inclusion into sched-devel/latest tree.
Based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
+ sched-devel/latest .../mingo/linux-2.6-sched-devel.git
Signed-off-by: Mike Travis <travis@sgi.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-05-13 02:21:12 +07:00
|
|
|
depends on X86_SMP
|
2008-01-30 19:33:22 +07:00
|
|
|
default n
|
|
|
|
help
|
|
|
|
Say Y to verify that the per_cpu map being accessed has
|
|
|
|
been setup. Adds a fair amount of code to kernel memory
|
|
|
|
and decreases performance.
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
2008-04-17 22:40:45 +07:00
|
|
|
config X86_PTDUMP
|
|
|
|
bool "Export kernel pagetable layout to userspace via debugfs"
|
2008-04-17 22:40:45 +07:00
|
|
|
depends on DEBUG_KERNEL
|
2008-04-17 22:40:45 +07:00
|
|
|
select DEBUG_FS
|
|
|
|
help
|
|
|
|
Say Y here if you want to show the kernel pagetable layout in a
|
|
|
|
debugfs file. This information is only useful for kernel developers
|
|
|
|
who are working in architecture specific areas of the kernel.
|
|
|
|
It is probably not a good idea to enable this feature in a production
|
|
|
|
kernel.
|
|
|
|
If in doubt, say "N"
|
|
|
|
|
2006-01-06 15:12:02 +07:00
|
|
|
config DEBUG_RODATA
|
|
|
|
bool "Write protect kernel read-only data structures"
|
2008-01-30 19:33:32 +07:00
|
|
|
default y
|
2006-01-06 15:12:02 +07:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Mark the kernel read-only data as write-protected in the pagetables,
|
|
|
|
in order to catch accidental (and incorrect) writes to such const
|
2008-01-30 19:33:32 +07:00
|
|
|
data. This is recommended so that we can catch kernel bugs sooner.
|
|
|
|
If in doubt, say "Y".
|
2006-01-06 15:12:02 +07:00
|
|
|
|
2008-04-17 22:40:45 +07:00
|
|
|
config DIRECT_GBPAGES
|
|
|
|
bool "Enable gbpages-mapped kernel pagetables"
|
|
|
|
depends on DEBUG_KERNEL && EXPERIMENTAL && X86_64
|
|
|
|
help
|
|
|
|
Enable gigabyte pages support (if the CPU supports it). This can
|
|
|
|
improve the kernel's performance a tiny bit by reducing TLB
|
|
|
|
pressure.
|
|
|
|
|
|
|
|
This is experimental code.
|
|
|
|
|
|
|
|
If in doubt, say "N".
|
|
|
|
|
2008-01-30 19:34:09 +07:00
|
|
|
config DEBUG_RODATA_TEST
|
|
|
|
bool "Testcase for the DEBUG_RODATA feature"
|
|
|
|
depends on DEBUG_RODATA
|
|
|
|
help
|
|
|
|
This option enables a testcase for the DEBUG_RODATA
|
|
|
|
feature as well as for the change_page_attr() infrastructure.
|
|
|
|
If in doubt, say "N"
|
|
|
|
|
|
|
|
config DEBUG_NX_TEST
|
|
|
|
tristate "Testcase for the NX non-executable stack feature"
|
|
|
|
depends on DEBUG_KERNEL && m
|
|
|
|
help
|
|
|
|
This option enables a testcase for the CPU NX capability
|
|
|
|
and the software setup of this feature.
|
|
|
|
If in doubt, say "N"
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config 4KSTACKS
|
|
|
|
bool "Use 4Kb for kernel stacks instead of 8Kb"
|
2007-10-25 05:50:43 +07:00
|
|
|
depends on X86_32
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
If you say Y here the kernel will use a 4Kb stacksize for the
|
|
|
|
kernel stack attached to each process/thread. This facilitates
|
|
|
|
running more threads on a system and also reduces the pressure
|
|
|
|
on the VM subsystem for higher order allocations. This option
|
|
|
|
will also use IRQ stacks to compensate for the reduced stackspace.
|
|
|
|
|
2006-04-18 17:35:22 +07:00
|
|
|
config DOUBLEFAULT
|
|
|
|
default y
|
|
|
|
bool "Enable doublefault exception handler" if EMBEDDED
|
2007-10-25 05:50:43 +07:00
|
|
|
depends on X86_32
|
|
|
|
help
|
|
|
|
This option allows trapping of rare doublefault exceptions that
|
|
|
|
would otherwise cause a system to silently reboot. Disabling this
|
|
|
|
option saves about 4k and might cause you much additional grey
|
|
|
|
hair.
|
|
|
|
|
|
|
|
config IOMMU_DEBUG
|
|
|
|
bool "Enable IOMMU debugging"
|
2007-10-24 17:49:48 +07:00
|
|
|
depends on GART_IOMMU && DEBUG_KERNEL
|
2007-10-25 05:50:43 +07:00
|
|
|
depends on X86_64
|
2006-04-18 17:35:22 +07:00
|
|
|
help
|
2007-10-25 05:50:43 +07:00
|
|
|
Force the IOMMU to on even when you have less than 4GB of
|
|
|
|
memory and add debugging code. On overflow always panic. And
|
|
|
|
allow to enable IOMMU leak tracing. Can be disabled at boot
|
|
|
|
time with iommu=noforce. This will also enable scatter gather
|
|
|
|
list merging. Currently not recommended for production
|
|
|
|
code. When you use it make sure you have a big enough
|
|
|
|
IOMMU/AGP aperture. Most of the options enabled by this can
|
|
|
|
be set more finegrained using the iommu= command line
|
|
|
|
options. See Documentation/x86_64/boot-options.txt for more
|
|
|
|
details.
|
|
|
|
|
|
|
|
config IOMMU_LEAK
|
|
|
|
bool "IOMMU leak tracing"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
depends on IOMMU_DEBUG
|
|
|
|
help
|
|
|
|
Add a simple leak tracer to the IOMMU code. This is useful when you
|
|
|
|
are debugging a buggy device driver that leaks IOMMU mappings.
|
|
|
|
|
2008-05-13 02:20:57 +07:00
|
|
|
config MMIOTRACE_HOOKS
|
|
|
|
bool
|
2008-05-13 02:20:56 +07:00
|
|
|
|
2008-05-13 02:20:56 +07:00
|
|
|
config MMIOTRACE
|
2008-05-13 02:20:57 +07:00
|
|
|
bool "Memory mapped IO tracing"
|
2008-05-13 02:20:59 +07:00
|
|
|
depends on DEBUG_KERNEL && PCI
|
2008-05-13 02:20:57 +07:00
|
|
|
select TRACING
|
2008-05-13 02:20:57 +07:00
|
|
|
select MMIOTRACE_HOOKS
|
2008-05-13 02:20:56 +07:00
|
|
|
help
|
2008-05-13 02:20:57 +07:00
|
|
|
Mmiotrace traces Memory Mapped I/O access and is meant for
|
|
|
|
debugging and reverse engineering. It is called from the ioremap
|
2008-05-13 02:20:59 +07:00
|
|
|
implementation and works via page faults. Tracing is disabled by
|
2008-05-13 02:20:59 +07:00
|
|
|
default and can be enabled at run-time.
|
2008-05-13 02:20:56 +07:00
|
|
|
|
2008-05-13 02:20:59 +07:00
|
|
|
See Documentation/tracers/mmiotrace.txt.
|
2008-05-13 02:20:56 +07:00
|
|
|
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.
|
|
|
|
|
2008-01-30 19:30:05 +07:00
|
|
|
#
|
|
|
|
# IO delay types:
|
|
|
|
#
|
|
|
|
|
|
|
|
config IO_DELAY_TYPE_0X80
|
|
|
|
int
|
|
|
|
default "0"
|
|
|
|
|
|
|
|
config IO_DELAY_TYPE_0XED
|
|
|
|
int
|
|
|
|
default "1"
|
|
|
|
|
|
|
|
config IO_DELAY_TYPE_UDELAY
|
|
|
|
int
|
|
|
|
default "2"
|
|
|
|
|
|
|
|
config IO_DELAY_TYPE_NONE
|
|
|
|
int
|
|
|
|
default "3"
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "IO delay type"
|
2008-02-18 02:20:24 +07:00
|
|
|
default IO_DELAY_0X80
|
2008-01-30 19:30:05 +07:00
|
|
|
|
|
|
|
config IO_DELAY_0X80
|
|
|
|
bool "port 0x80 based port-IO delay [recommended]"
|
|
|
|
help
|
|
|
|
This is the traditional Linux IO delay used for in/out_p.
|
|
|
|
It is the most tested hence safest selection here.
|
|
|
|
|
|
|
|
config IO_DELAY_0XED
|
|
|
|
bool "port 0xed based port-IO delay"
|
|
|
|
help
|
|
|
|
Use port 0xed as the IO delay. This frees up port 0x80 which is
|
|
|
|
often used as a hardware-debug port.
|
|
|
|
|
|
|
|
config IO_DELAY_UDELAY
|
|
|
|
bool "udelay based port-IO delay"
|
|
|
|
help
|
|
|
|
Use udelay(2) as the IO delay method. This provides the delay
|
|
|
|
while not having any side-effect on the IO port space.
|
|
|
|
|
|
|
|
config IO_DELAY_NONE
|
|
|
|
bool "no port-IO delay"
|
2008-01-30 19:30:05 +07:00
|
|
|
help
|
2008-01-30 19:30:05 +07:00
|
|
|
No port-IO delay. Will break on old boxes that require port-IO
|
|
|
|
delay for certain operations. Should work on most new machines.
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
if IO_DELAY_0X80
|
|
|
|
config DEFAULT_IO_DELAY_TYPE
|
|
|
|
int
|
|
|
|
default IO_DELAY_TYPE_0X80
|
|
|
|
endif
|
|
|
|
|
|
|
|
if IO_DELAY_0XED
|
|
|
|
config DEFAULT_IO_DELAY_TYPE
|
|
|
|
int
|
|
|
|
default IO_DELAY_TYPE_0XED
|
|
|
|
endif
|
|
|
|
|
|
|
|
if IO_DELAY_UDELAY
|
|
|
|
config DEFAULT_IO_DELAY_TYPE
|
|
|
|
int
|
|
|
|
default IO_DELAY_TYPE_UDELAY
|
|
|
|
endif
|
|
|
|
|
|
|
|
if IO_DELAY_NONE
|
|
|
|
config DEFAULT_IO_DELAY_TYPE
|
|
|
|
int
|
|
|
|
default IO_DELAY_TYPE_NONE
|
|
|
|
endif
|
2008-01-30 19:30:05 +07:00
|
|
|
|
2008-01-30 19:32:51 +07:00
|
|
|
config DEBUG_BOOT_PARAMS
|
|
|
|
bool "Debug boot parameters"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
depends on DEBUG_FS
|
|
|
|
help
|
|
|
|
This option will cause struct boot_params to be exported via debugfs.
|
|
|
|
|
2008-01-30 19:33:42 +07:00
|
|
|
config CPA_DEBUG
|
2008-02-07 04:39:45 +07:00
|
|
|
bool "CPA self-test code"
|
2008-01-30 19:34:04 +07:00
|
|
|
depends on DEBUG_KERNEL
|
2008-01-30 19:33:42 +07:00
|
|
|
help
|
2008-02-07 04:39:45 +07:00
|
|
|
Do change_page_attr() self-tests every 30 seconds.
|
2008-01-30 19:33:42 +07:00
|
|
|
|
2008-03-03 18:38:52 +07:00
|
|
|
config OPTIMIZE_INLINING
|
|
|
|
bool "Allow gcc to uninline functions marked 'inline'"
|
2008-05-01 09:50:03 +07:00
|
|
|
depends on BROKEN
|
2008-03-03 18:38:52 +07:00
|
|
|
help
|
|
|
|
This option determines if the kernel forces gcc to inline the functions
|
|
|
|
developers have marked 'inline'. Doing so takes away freedom from gcc to
|
|
|
|
do what it thinks is best, which is desirable for the gcc 3.x series of
|
|
|
|
compilers. The gcc 4.x series have a rewritten inlining algorithm and
|
|
|
|
disabling this option will generate a smaller kernel there. Hopefully
|
|
|
|
this algorithm is so good that allowing gcc4 to make the decision can
|
|
|
|
become the default in the future, until then this option is there to
|
|
|
|
test gcc for this.
|
2008-04-30 13:48:45 +07:00
|
|
|
|
|
|
|
endmenu
|
|
|
|
|