linux/arch/powerpc/Kconfig.debug
<<
>>
Prefs
   1menu "Kernel hacking"
   2
   3source "lib/Kconfig.debug"
   4
   5config PPC_DISABLE_WERROR
   6        bool "Don't build arch/powerpc code with -Werror"
   7        default n
   8        help
   9          This option tells the compiler NOT to build the code under
  10          arch/powerpc with the -Werror flag (which means warnings
  11          are treated as errors).
  12
  13          Only enable this if you are hitting a build failure in the
  14          arch/powerpc code caused by a warning, and you don't feel
  15          inclined to fix it.
  16
  17config PPC_WERROR
  18        bool
  19        depends on !PPC_DISABLE_WERROR
  20        default y
  21
  22config PRINT_STACK_DEPTH
  23        int "Stack depth to print" if DEBUG_KERNEL
  24        default 64
  25        help
  26          This option allows you to set the stack depth that the kernel
  27          prints in stack traces. This can be useful if your display is
  28          too small and stack traces cause important information to
  29          scroll off the screen.
  30
  31config HCALL_STATS
  32        bool "Hypervisor call instrumentation"
  33        depends on PPC_PSERIES && DEBUG_FS && TRACEPOINTS
  34        help
  35          Adds code to keep track of the number of hypervisor calls made and
  36          the amount of time spent in hypervisor calls.  Wall time spent in
  37          each call is always calculated, and if available CPU cycles spent
  38          are also calculated.  A directory named hcall_inst is added at the
  39          root of the debugfs filesystem.  Within the hcall_inst directory
  40          are files that contain CPU specific call statistics.
  41
  42          This option will add a small amount of overhead to all hypervisor
  43          calls.
  44
  45config PPC_EMULATED_STATS
  46        bool "Emulated instructions tracking"
  47        depends on DEBUG_FS
  48        help
  49          Adds code to keep track of the number of instructions that are
  50          emulated by the in-kernel emulator. Counters for the various classes
  51          of emulated instructions are available under
  52          powerpc/emulated_instructions/ in the root of the debugfs file
  53          system. Optionally (controlled by
  54          powerpc/emulated_instructions/do_warn in debugfs), rate-limited
  55          warnings can be printed to the console when instructions are
  56          emulated.
  57
  58config CODE_PATCHING_SELFTEST
  59        bool "Run self-tests of the code-patching code."
  60        depends on DEBUG_KERNEL
  61        default n
  62
  63config FTR_FIXUP_SELFTEST
  64        bool "Run self-tests of the feature-fixup code."
  65        depends on DEBUG_KERNEL
  66        default n
  67
  68config MSI_BITMAP_SELFTEST
  69        bool "Run self-tests of the MSI bitmap code."
  70        depends on DEBUG_KERNEL
  71        default n
  72
  73config XMON
  74        bool "Include xmon kernel debugger"
  75        depends on DEBUG_KERNEL
  76        help
  77          Include in-kernel hooks for the xmon kernel monitor/debugger.
  78          Unless you are intending to debug the kernel, say N here.
  79          Make sure to enable also CONFIG_BOOTX_TEXT on Macs. Otherwise
  80          nothing will appear on the screen (xmon writes directly to the
  81          framebuffer memory).
  82          The cmdline option 'xmon' or 'xmon=early' will drop into xmon
  83          very early during boot. 'xmon=on' will just enable the xmon
  84          debugger hooks.  'xmon=off' will disable the debugger hooks
  85          if CONFIG_XMON_DEFAULT is set.
  86          xmon will print a backtrace on the very first invocation.
  87          'xmon=nobt' will disable this autobacktrace.
  88
  89config XMON_DEFAULT
  90        bool "Enable xmon by default"
  91        depends on XMON
  92        help
  93          xmon is normally disabled unless booted with 'xmon=on'.
  94          Use 'xmon=off' to disable xmon init during runtime.
  95
  96config XMON_DISASSEMBLY
  97        bool "Include disassembly support in xmon"
  98        depends on XMON
  99        default y
 100        help
 101          Include support for disassembling in xmon. You probably want
 102          to say Y here, unless you're building for a memory-constrained
 103          system.
 104
 105config DEBUGGER
 106        bool
 107        depends on KGDB || XMON
 108        default y
 109
 110config BDI_SWITCH
 111        bool "Include BDI-2000 user context switcher"
 112        depends on DEBUG_KERNEL && PPC32
 113        help
 114          Include in-kernel support for the Abatron BDI2000 debugger.
 115          Unless you are intending to debug the kernel with one of these
 116          machines, say N here.
 117
 118config BOOTX_TEXT
 119        bool "Support for early boot text console (BootX or OpenFirmware only)"
 120        depends on PPC_OF && PPC_BOOK3S
 121        help
 122          Say Y here to see progress messages from the boot firmware in text
 123          mode. Requires either BootX or Open Firmware.
 124
 125config PPC_EARLY_DEBUG
 126        bool "Early debugging (dangerous)"
 127        help
 128          Say Y to enable some early debugging facilities that may be available
 129          for your processor/board combination. Those facilities are hacks
 130          intended to debug problems early during boot, this should not be
 131          enabled in a production kernel.
 132          Note that enabling this will also cause the kernel default log level
 133          to be pushed to max automatically very early during boot
 134
 135choice
 136        prompt "Early debugging console"
 137        depends on PPC_EARLY_DEBUG
 138        help
 139          Use the selected console for early debugging. Careful, if you
 140          enable debugging for the wrong type of machine your kernel
 141          _will not boot_.
 142
 143config PPC_EARLY_DEBUG_BOOTX
 144        bool "BootX or OpenFirmware"
 145        depends on BOOTX_TEXT
 146        help
 147          Select this to enable early debugging for a machine using BootX
 148          or OpenFirmware.
 149
 150config PPC_EARLY_DEBUG_LPAR
 151        bool "LPAR HV Console"
 152        depends on PPC_PSERIES
 153        help
 154          Select this to enable early debugging for a machine with a HVC
 155          console on vterm 0.
 156
 157config PPC_EARLY_DEBUG_LPAR_HVSI
 158        bool "LPAR HVSI Console"
 159        depends on PPC_PSERIES
 160        help
 161          Select this to enable early debugging for a machine with a HVSI
 162          console on a specified vterm.
 163
 164config PPC_EARLY_DEBUG_G5
 165        bool "Apple G5"
 166        depends on PPC_PMAC64
 167        help
 168          Select this to enable early debugging for Apple G5 machines.
 169
 170config PPC_EARLY_DEBUG_RTAS_PANEL
 171        bool "RTAS Panel"
 172        depends on PPC_RTAS
 173        help
 174          Select this to enable early debugging via the RTAS panel.
 175
 176config PPC_EARLY_DEBUG_RTAS_CONSOLE
 177        bool "RTAS Console"
 178        depends on PPC_RTAS
 179        select UDBG_RTAS_CONSOLE
 180        help
 181          Select this to enable early debugging via the RTAS console.
 182
 183config PPC_EARLY_DEBUG_MAPLE
 184        bool "Maple real mode"
 185        depends on PPC_MAPLE
 186        help
 187          Select this to enable early debugging for Maple.
 188
 189config PPC_EARLY_DEBUG_PAS_REALMODE
 190        bool "PA Semi real mode"
 191        depends on PPC_PASEMI
 192        help
 193          Select this to enable early debugging for PA Semi.
 194          Output will be on UART0.
 195
 196config PPC_EARLY_DEBUG_BEAT
 197        bool "Beat HV Console"
 198        depends on PPC_CELLEB
 199        select PPC_UDBG_BEAT
 200        help
 201          Select this to enable early debugging for Celleb with Beat.
 202
 203config PPC_EARLY_DEBUG_44x
 204        bool "Early serial debugging for IBM/AMCC 44x CPUs"
 205        # PPC_EARLY_DEBUG on 440 leaves AS=1 mappings above the TLB high water
 206        # mark, which doesn't work with current 440 KVM.
 207        depends on 44x && !KVM
 208        help
 209          Select this to enable early debugging for IBM 44x chips via the
 210          inbuilt serial port.  If you enable this, ensure you set
 211          PPC_EARLY_DEBUG_44x_PHYSLOW below to suit your target board.
 212
 213config PPC_EARLY_DEBUG_40x
 214        bool "Early serial debugging for IBM/AMCC 40x CPUs"
 215        depends on 40x
 216        help
 217          Select this to enable early debugging for IBM 40x chips via the
 218          inbuilt serial port. This works on chips with a 16550 compatible
 219          UART. Xilinx chips with uartlite cannot use this option.
 220
 221config PPC_EARLY_DEBUG_CPM
 222        bool "Early serial debugging for Freescale CPM-based serial ports"
 223        depends on SERIAL_CPM
 224        select PIN_TLB if PPC_8xx
 225        help
 226          Select this to enable early debugging for Freescale chips
 227          using a CPM-based serial port.  This assumes that the bootwrapper
 228          has run, and set up the CPM in a particular way.
 229
 230config PPC_EARLY_DEBUG_USBGECKO
 231        bool "Early debugging through the USB Gecko adapter"
 232        depends on GAMECUBE_COMMON
 233        select USBGECKO_UDBG
 234        help
 235          Select this to enable early debugging for Nintendo GameCube/Wii
 236          consoles via an external USB Gecko adapter.
 237
 238config PPC_EARLY_DEBUG_WSP
 239        bool "Early debugging via WSP's internal UART"
 240        depends on PPC_WSP
 241        select PPC_UDBG_16550
 242
 243config PPC_EARLY_DEBUG_PS3GELIC
 244        bool "Early debugging through the PS3 Ethernet port"
 245        depends on PPC_PS3
 246        select PS3GELIC_UDBG
 247        help
 248          Select this to enable early debugging for the PlayStation3 via
 249          UDP broadcasts sent out through the Ethernet port.
 250
 251config PPC_EARLY_DEBUG_OPAL_RAW
 252        bool "OPAL raw console"
 253        depends on HVC_OPAL
 254        help
 255          Select this to enable early debugging for the PowerNV platform
 256          using a "raw" console
 257
 258config PPC_EARLY_DEBUG_OPAL_HVSI
 259        bool "OPAL hvsi console"
 260        depends on HVC_OPAL
 261        help
 262          Select this to enable early debugging for the PowerNV platform
 263          using an "hvsi" console
 264
 265config PPC_EARLY_DEBUG_MEMCONS
 266        bool "In memory console"
 267        help
 268          Select this to enable early debugging using an in memory console.
 269          This console provides input and output buffers stored within the
 270          kernel BSS and should be safe to select on any system. A debugger
 271          can then be used to read kernel output or send input to the console.
 272endchoice
 273
 274config PPC_MEMCONS_OUTPUT_SIZE
 275        int "In memory console output buffer size"
 276        depends on PPC_EARLY_DEBUG_MEMCONS
 277        default 4096
 278        help
 279          Selects the size of the output buffer (in bytes) of the in memory
 280          console.
 281
 282config PPC_MEMCONS_INPUT_SIZE
 283        int "In memory console input buffer size"
 284        depends on PPC_EARLY_DEBUG_MEMCONS
 285        default 128
 286        help
 287          Selects the size of the input buffer (in bytes) of the in memory
 288          console.
 289
 290config PPC_EARLY_DEBUG_OPAL
 291        def_bool y
 292        depends on PPC_EARLY_DEBUG_OPAL_RAW || PPC_EARLY_DEBUG_OPAL_HVSI
 293
 294
 295config PPC_EARLY_DEBUG_HVSI_VTERMNO
 296        hex "vterm number to use with early debug HVSI"
 297        depends on PPC_EARLY_DEBUG_LPAR_HVSI
 298        default "0x30000000"
 299        help
 300          You probably want 0x30000000 for your first serial port and
 301          0x30000001 for your second one
 302
 303config PPC_EARLY_DEBUG_OPAL_VTERMNO
 304        hex "vterm number to use with OPAL early debug"
 305        depends on PPC_EARLY_DEBUG_OPAL
 306        default "0"
 307        help
 308          This correspond to which /dev/hvcN you want to use for early
 309          debug.
 310
 311          On OPAL v1 (takeover) this should always be 0
 312          On OPAL v2, this will be 0 for network console and 1 or 2 for
 313          the machine built-in serial ports.
 314
 315config PPC_EARLY_DEBUG_44x_PHYSLOW
 316        hex "Low 32 bits of early debug UART physical address"
 317        depends on PPC_EARLY_DEBUG_44x
 318        default "0x40000200"
 319        help
 320          You probably want 0x40000200 for ebony boards and
 321          0x40000300 for taishan
 322
 323config PPC_EARLY_DEBUG_44x_PHYSHIGH
 324        hex "EPRN of early debug UART physical address"
 325        depends on PPC_EARLY_DEBUG_44x
 326        default "0x1"
 327
 328config PPC_EARLY_DEBUG_40x_PHYSADDR
 329        hex "Early debug UART physical address"
 330        depends on PPC_EARLY_DEBUG_40x
 331        default "0xef600300"
 332
 333config PPC_EARLY_DEBUG_CPM_ADDR
 334        hex "CPM UART early debug transmit descriptor address"
 335        depends on PPC_EARLY_DEBUG_CPM
 336        default "0xfa202008" if PPC_EP88XC
 337        default "0xf0001ff8" if CPM2
 338        default "0xff002008" if CPM1
 339        help
 340          This specifies the address of the transmit descriptor
 341          used for early debug output.  Because it is needed before
 342          platform probing is done, all platforms selected must
 343          share the same address.
 344
 345config STRICT_DEVMEM
 346        def_bool y
 347        prompt "Filter access to /dev/mem"
 348        help
 349          This option restricts access to /dev/mem.  If this option is
 350          disabled, you allow userspace access to all memory, including
 351          kernel and userspace memory. Accidental memory access is likely
 352          to be disastrous.
 353          Memory access is required for experts who want to debug the kernel.
 354
 355          If you are unsure, say Y.
 356
 357config FAIL_IOMMU
 358        bool "Fault-injection capability for IOMMU"
 359        depends on FAULT_INJECTION
 360        help
 361          Provide fault-injection capability for IOMMU. Each device can
 362          be selectively enabled via the fail_iommu property.
 363
 364          If you are unsure, say N.
 365
 366endmenu
 367