kernel-2.6.27で新参なパラメータ

Memtest (MEMTEST) [N/y/?] (NEW) ?

Memtest (MEMTEST) [N/y/?] (NEW) ?

This option adds a kernel parameter 'memtest', which allows memtest
to be set.
memtest=0, mean disabled; -- default
memtest=1, mean do 1 test pattern;
...
memtest=4, mean do 4 test patterns.
If you are unsure how to answer this question, answer N.

Reserve low 64K of RAM on AMI/Phoenix BIOSen

Reserve low 64K of RAM on AMI/Phoenix BIOSen (X86_RESERVE_LOW_64K) [Y/n/?] (NEW) ?

Reserve the first 64K of physical RAM on BIOSes that are known
to potentially corrupt that memory range. A numbers of BIOSes are
known to utilize this area during suspend/resume, so it must not
be used by the kernel.

Set this to N if you are absolutely sure that you trust the BIOS
to get all its memory reservations and usages right.

If you have doubts about the BIOS (e.g. suspend/resume does not
work or there's kernel crashes after certain hardware hotplug
events) and it's not AMI or Phoenix, then you might want to enable
X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
corruption patterns.

Say Y if unsure.

MTRR cleanup support (MTRR_SANITIZER) [N/y/?] (NEW) ?

MTRR cleanup support (MTRR_SANITIZER) [N/y/?] (NEW) ?

Convert MTRR layout from continuous to discrete, so X drivers can
add writeback entries.

Can be disabled with disable_mtrr_cleanup on the kernel command line.
The largest mtrr entry size for a continous block can be set with
mtrr_chunk_size.

If unsure, say N.

PCI slot detection driver (ACPI_PCI_SLOT) [N/m/y/?] (NEW) ?

This driver will attempt to discover all PCI slots in your system,
and creates entries in /sys/bus/pci/slots/. This feature can
help you correlate PCI bus addresses with the physical geography
of your slots. If you are unsure, say N.

Include in-kernel firmware blobs in kernel binary (FIRMWARE_IN_KERNEL) [Y/n/?] (NEW) ?

Include in-kernel firmware blobs in kernel binary (FIRMWARE_IN_KERNEL) [Y/n/?] (NEW) ?

The kernel source tree includes a number of firmware 'blobs'
which are used by various drivers. The recommended way to
use these is to run "make firmware_install" and to copy the
resulting binary files created in usr/lib/firmware directory
of the kernel tree to the /lib/firmware on your system so
that they can be loaded by userspace helpers on request.

Enabling this option will build each required firmware blob
into the kernel directly, where request_firmware() will find
them without having to call out to userspace. This may be
useful if your root file system requires a device which uses
such firmware, and do not wish to use an initrd.

This single option controls the inclusion of firmware for
every driver which usees request_firmare() and ships its
firmware in the kernel source tree, to avoid a proliferation
of 'Include firmware for xxx device' options.

Say 'N' and let firmware be loaded from userspace.

SDHCI support on PCI bus (MMC_SDHCI_PCI) [N/m/?] (NEW) ?

SDHCI support on PCI bus (MMC_SDHCI_PCI) [N/m/?] (NEW) ?

This selects the PCI Secure Digital Host Controller Interface.
Most controllers found today are PCI devices.

If you have a controller with this interface, say Y or M here.

If unsure, say N.

Userspace I/O platform driver (UIO_PDRV) [N/m/?] (NEW) ?

Userspace I/O platform driver (UIO_PDRV) [N/m/?] (NEW) ?

Generic platform driver for Userspace I/O devices.

If you don't know what to do here, say N.

SonicBlue Optimized MPEG File System support (OMFS_FS) [N/m/y/?] (NEW) ?

SonicBlue Optimized MPEG File System support (OMFS_FS) [N/m/y/?] (NEW) ?

This is the proprietary file system used by the Rio Karma music
player and ReplayTV DVR. Despite the name, this filesystem is not
more efficient than a standard FS for MPEG files, in fact likely
the opposite is true. Say Y if you have either of these devices
and wish to mount its disk.

To compile this file system support as a module, choose M here: the
module will be called omfs. If unsure, say N.

Interrupts-off Latency Tracer (IRQSOFF_TRACER) [N/y/?] (NEW) ?

Interrupts-off Latency Tracer (IRQSOFF_TRACER) [N/y/?] (NEW) ?

This option measures the time spent in irqs-off critical
sections, with microsecond accuracy.

The default measurement method is a maximum search, which is
disabled by default and can be runtime (re-)started
via:

echo 0 > /debugfs/tracing/tracing_max_latency

(Note that kernel size and overhead increases with this option
enabled. This option and the preempt-off timing option can be
used together or separately.)

Enable verbose x86 bootup info messages (X86_VERBOSE_BOOTUP) [Y/n/?] (NEW) ?

Enable verbose x86 bootup info messages (X86_VERBOSE_BOOTUP) [Y/n/?] (NEW) ?

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.

Allow gcc to uninline functions marked 'inline' (OPTIMIZE_INLINING) [N/y/?] (NEW) ?

Allow gcc to uninline functions marked 'inline' (OPTIMIZE_INLINING) [N/y/?] (NEW) ?

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.

If unsure, say N.