lkml.org 
[lkml]   [2010]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCHv1 003/211] unicore32: new file arch/unicore32/Kconfig.debug
On Thu, 9 Dec 2010 17:32:42 +0800 Guan Xuetao wrote:

> From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
>
> Kconfig file for debugger
>
> Signed-off-by: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
> ---
> arch/unicore32/Kconfig.debug | 86
> ++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 86 insertions(+), 0 deletions(-)
>
> diff --git a/arch/unicore32/Kconfig.debug b/arch/unicore32/Kconfig.debug
> new file mode 100644
> index 0000000..e59ab3c
> --- /dev/null
> +++ b/arch/unicore32/Kconfig.debug
> @@ -0,0 +1,86 @@
> +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

Your mail app (or some messed-up server) is splitting long lines. This
makes the patch file invalid -- it cannot be applied cleanly.


> + 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.
> +
> +config EARLY_PRINTK
> + bool "Early printk"
> + default DEBUG_OCD
> + help
> + Write kernel log output directly into the ocd 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_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
> +
> +config DEBUG_STACK_USAGE
> + bool "Enable 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 output.
> +
> +# These options are only for real kernel hackers who want to get their
> hands dirty.

Same thing here (above).


> +config DEBUG_LL
> + bool "Kernel low-level debugging functions"
> + 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.
> +
> +config DEBUG_OCD
> + bool "Kernel low-level debugging via On-Chip-Debugger"
> + depends on DEBUG_LL
> + default y
> + help
> + Say Y here if you want the debug print routines to direct their
> + output to the UniCore On-Chip-Debugger channel using CP #1.
> +
> +config DEBUG_OCD_BREAKPOINT
> + bool "Breakpoint support via On-Chip-Debugger"
> + depends on DEBUG_OCD
> +
> +config DEBUG_UART
> + int "Kernel low-level debugging messages via serial port"
> + depends on DEBUG_LL
> + range 0 1
> + default "0"
> + help
> + Choice for UART for kernel low-level using PKUnity UARTS,
> + should be between zero and one. The port must have been
> + initialised by the boot-loader before use.
> +
> +endmenu
>
> --


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***


\
 
 \ /
  Last update: 2010-12-09 17:45    [W:0.031 / U:0.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site