2006-06-09 12:12:45 +07:00
|
|
|
config DEFCONFIG_LIST
|
|
|
|
|
string
|
[PATCH] uml: use DEFCONFIG_LIST to avoid reading host's config
This should make sure that, for UML, host's configuration files are not
considered, which avoids various pains to the user. Our dependency are such
that the obtained Kconfig will be valid and will lead to successful
compilation - however they cannot prevent an user from disabling any boot
device, and if an option is not set in the read .config (say
/boot/config-XXX), with make menuconfig ARCH=um, it is not set. This always
disables UBD and all console I/O channels, which leads to non-working UML
kernels, so this bothers users - especially now, since it will happen on
almost every machine (/boot/config-`uname -r` exists almost on every machine).
It can be workarounded with make defconfig ARCH=um, but it is non-obvious and
can be avoided, so please _do_ merge this patch.
Given the existence of options, it could be interesting to implement
(additionally) "option required" - with it, Kconfig will refuse reading a
.config file (from wherever it comes) if the given option is not set. With
this, one could mark with it the option characteristic of the given
architecture (it was an old proposal of Roman Zippel, when I pointed out our
problem):
config UML
option required
default y
However this should be further discussed:
*) for x86, it must support constructs like:
==arch/i386/Kconfig==
config 64BIT
option required
default n
where Kconfig must require that CONFIG_64BIT is disabled or not present in the
read .config.
*) do we want to do such checks only for the starting defconfig or also for
.config? Which leads to:
*) I may want to port a x86_64 .config to x86 and viceversa, or even among more
different archs. Should that be allowed, and in which measure (the user may
force skipping the check for a .config or it is only given a warning by
default)?
Cc: Roman Zippel <zippel@linux-m68k.org>
Cc: <kbuild-devel@lists.sourceforge.net>
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-10-20 13:28:23 +07:00
|
|
|
depends on !UML
|
2006-06-09 12:12:45 +07:00
|
|
|
option defconfig_list
|
|
|
|
|
default "/lib/modules/$UNAME_RELEASE/.config"
|
|
|
|
|
default "/etc/kernel-config"
|
|
|
|
|
default "/boot/config-$UNAME_RELEASE"
|
|
|
|
|
default "arch/$ARCH/defconfig"
|
|
|
|
|
|
2007-07-31 14:39:23 +07:00
|
|
|
menu "General setup"
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
config EXPERIMENTAL
|
|
|
|
|
bool "Prompt for development and/or incomplete code/drivers"
|
|
|
|
|
---help---
|
|
|
|
|
Some of the various things that Linux supports (such as network
|
|
|
|
|
drivers, file systems, network protocols, etc.) can be in a state
|
|
|
|
|
of development where the functionality, stability, or the level of
|
|
|
|
|
testing is not yet high enough for general use. This is usually
|
|
|
|
|
known as the "alpha-test" phase among developers. If a feature is
|
|
|
|
|
currently in alpha-test, then the developers usually discourage
|
|
|
|
|
uninformed widespread use of this feature by the general public to
|
|
|
|
|
avoid "Why doesn't this work?" type mail messages. However, active
|
|
|
|
|
testing and use of these systems is welcomed. Just be aware that it
|
|
|
|
|
may not meet the normal level of reliability or it may fail to work
|
|
|
|
|
in some special cases. Detailed bug reports from people familiar
|
|
|
|
|
with the kernel internals are usually welcomed by the developers
|
|
|
|
|
(before submitting bug reports, please read the documents
|
|
|
|
|
<file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
|
|
|
|
|
<file:Documentation/BUG-HUNTING>, and
|
|
|
|
|
<file:Documentation/oops-tracing.txt> in the kernel source).
|
|
|
|
|
|
|
|
|
|
This option will also make obsoleted drivers available. These are
|
|
|
|
|
drivers that have been replaced by something else, and/or are
|
|
|
|
|
scheduled to be removed in a future kernel release.
|
|
|
|
|
|
|
|
|
|
Unless you intend to help test and develop a feature or driver that
|
|
|
|
|
falls into this category, or you have a situation that requires
|
|
|
|
|
using these features, you should probably say N here, which will
|
|
|
|
|
cause the configurator to present you with fewer choices. If
|
|
|
|
|
you say Y here, you will be offered the choice of using features or
|
|
|
|
|
drivers that are currently considered to be in the alpha-test phase.
|
|
|
|
|
|
|
|
|
|
config BROKEN
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config BROKEN_ON_SMP
|
|
|
|
|
bool
|
|
|
|
|
depends on BROKEN || !SMP
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config LOCK_KERNEL
|
|
|
|
|
bool
|
|
|
|
|
depends on SMP || PREEMPT
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config INIT_ENV_ARG_LIMIT
|
|
|
|
|
int
|
2006-06-30 15:55:51 +07:00
|
|
|
default 32 if !UML
|
|
|
|
|
default 128 if UML
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
2005-10-31 06:01:46 +07:00
|
|
|
Maximum of each of the number of arguments and environment
|
|
|
|
|
variables passed to init from the kernel command line.
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
config LOCALVERSION
|
|
|
|
|
string "Local version - append to kernel release"
|
|
|
|
|
help
|
|
|
|
|
Append an extra string to the end of your kernel version.
|
|
|
|
|
This will show up when you type uname, for example.
|
|
|
|
|
The string you set here will be appended after the contents of
|
|
|
|
|
any files with a filename matching localversion* in your
|
|
|
|
|
object and source tree, in that order. Your total string can
|
|
|
|
|
be a maximum of 64 characters.
|
|
|
|
|
|
2005-07-31 15:57:49 +07:00
|
|
|
config LOCALVERSION_AUTO
|
|
|
|
|
bool "Automatically append version information to the version string"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This will try to automatically determine if the current tree is a
|
2007-05-02 04:08:11 +07:00
|
|
|
release tree by looking for git tags that belong to the current
|
|
|
|
|
top of tree revision.
|
2005-07-31 15:57:49 +07:00
|
|
|
|
|
|
|
|
A string of the format -gxxxxxxxx will be added to the localversion
|
2007-05-02 04:08:11 +07:00
|
|
|
if a git-based tree is found. The string generated by this will be
|
2005-07-31 15:57:49 +07:00
|
|
|
appended after any matching localversion* files, and after the value
|
2007-05-02 04:08:11 +07:00
|
|
|
set in CONFIG_LOCALVERSION.
|
2005-07-31 15:57:49 +07:00
|
|
|
|
2007-05-02 04:08:11 +07:00
|
|
|
(The actual string used here is the first eight characters produced
|
|
|
|
|
by running the command:
|
|
|
|
|
|
|
|
|
|
$ git rev-parse --verify HEAD
|
|
|
|
|
|
|
|
|
|
which is done within the script "scripts/setlocalversion".)
|
2005-07-31 15:57:49 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config SWAP
|
|
|
|
|
bool "Support for paging of anonymous memory (swap)"
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-10-01 01:45:40 +07:00
|
|
|
depends on MMU && BLOCK
|
2005-04-17 05:20:36 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option allows you to choose whether you want to have support
|
2006-01-15 08:40:08 +07:00
|
|
|
for so called swap devices or swap files in your kernel that are
|
2005-04-17 05:20:36 +07:00
|
|
|
used to provide more virtual memory than the actual RAM present
|
|
|
|
|
in your computer. If unsure say Y.
|
|
|
|
|
|
|
|
|
|
config SYSVIPC
|
|
|
|
|
bool "System V IPC"
|
|
|
|
|
---help---
|
|
|
|
|
Inter Process Communication is a suite of library functions and
|
|
|
|
|
system calls which let processes (running programs) synchronize and
|
|
|
|
|
exchange information. It is generally considered to be a good thing,
|
|
|
|
|
and some programs won't run unless you say Y here. In particular, if
|
|
|
|
|
you want to run the DOS emulator dosemu under Linux (read the
|
|
|
|
|
DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
|
|
|
|
|
you'll need to say Y here.
|
|
|
|
|
|
|
|
|
|
You can find documentation about IPC with "info ipc" and also in
|
|
|
|
|
section 6.4 of the Linux Programmer's Guide, available from
|
|
|
|
|
<http://www.tldp.org/guides.html>.
|
|
|
|
|
|
2007-02-14 15:34:06 +07:00
|
|
|
config SYSVIPC_SYSCTL
|
|
|
|
|
bool
|
|
|
|
|
depends on SYSVIPC
|
|
|
|
|
depends on SYSCTL
|
|
|
|
|
default y
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config POSIX_MQUEUE
|
|
|
|
|
bool "POSIX Message Queues"
|
|
|
|
|
depends on NET && EXPERIMENTAL
|
|
|
|
|
---help---
|
|
|
|
|
POSIX variant of message queues is a part of IPC. In POSIX message
|
|
|
|
|
queues every message has a priority which decides about succession
|
|
|
|
|
of receiving it by a process. If you want to compile and run
|
|
|
|
|
programs written e.g. for Solaris with use of its POSIX message
|
2007-05-09 12:25:13 +07:00
|
|
|
queues (functions mq_*) say Y here.
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
POSIX message queues are visible as a filesystem called 'mqueue'
|
|
|
|
|
and can be mounted somewhere if you want to do filesystem
|
|
|
|
|
operations on message queues.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config BSD_PROCESS_ACCT
|
|
|
|
|
bool "BSD Process Accounting"
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, a user level program will be able to instruct the
|
|
|
|
|
kernel (via a special system call) to write process accounting
|
|
|
|
|
information to a file: whenever a process exits, information about
|
|
|
|
|
that process will be appended to the file by the kernel. The
|
|
|
|
|
information includes things such as creation time, owning user,
|
|
|
|
|
command name, memory usage, controlling terminal etc. (the complete
|
|
|
|
|
list is in the struct acct in <file:include/linux/acct.h>). It is
|
|
|
|
|
up to the user level program to do useful things with this
|
|
|
|
|
information. This is generally a good idea, so say Y.
|
|
|
|
|
|
|
|
|
|
config BSD_PROCESS_ACCT_V3
|
|
|
|
|
bool "BSD Process Accounting version 3 file format"
|
|
|
|
|
depends on BSD_PROCESS_ACCT
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, the process accounting information is written
|
|
|
|
|
in a new file format that also logs the process IDs of each
|
|
|
|
|
process and it's parent. Note that this file format is incompatible
|
|
|
|
|
with previous v0/v1/v2 file formats, so you will need updated tools
|
|
|
|
|
for processing it. A preliminary version of these tools is available
|
|
|
|
|
at <http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/>.
|
|
|
|
|
|
2006-07-14 14:24:40 +07:00
|
|
|
config TASKSTATS
|
|
|
|
|
bool "Export task/process statistics through netlink (EXPERIMENTAL)"
|
|
|
|
|
depends on NET
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Export selected statistics for tasks/processes through the
|
|
|
|
|
generic netlink interface. Unlike BSD process accounting, the
|
|
|
|
|
statistics are available during the lifetime of tasks/processes as
|
|
|
|
|
responses to commands. Like BSD accounting, they are sent to user
|
|
|
|
|
space on task exit.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2006-07-14 14:24:36 +07:00
|
|
|
config TASK_DELAY_ACCT
|
|
|
|
|
bool "Enable per-task delay accounting (EXPERIMENTAL)"
|
2006-07-14 14:24:41 +07:00
|
|
|
depends on TASKSTATS
|
2006-07-14 14:24:36 +07:00
|
|
|
help
|
|
|
|
|
Collect information on time spent by a task waiting for system
|
|
|
|
|
resources like cpu, synchronous block I/O completion and swapping
|
|
|
|
|
in pages. Such statistics can help in setting a task's priorities
|
|
|
|
|
relative to other tasks for cpu, io, rss limits etc.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2007-02-10 16:46:44 +07:00
|
|
|
config TASK_XACCT
|
|
|
|
|
bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
|
|
|
|
|
depends on TASKSTATS
|
|
|
|
|
help
|
|
|
|
|
Collect extended task accounting data and send the data
|
|
|
|
|
to userland for processing over the taskstats interface.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
|
|
|
|
config TASK_IO_ACCOUNTING
|
|
|
|
|
bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
|
|
|
|
|
depends on TASK_XACCT
|
|
|
|
|
help
|
|
|
|
|
Collect information on the number of bytes of storage I/O which this
|
|
|
|
|
task has caused.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2007-07-16 13:40:59 +07:00
|
|
|
config USER_NS
|
|
|
|
|
bool "User Namespaces (EXPERIMENTAL)"
|
|
|
|
|
default n
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Support user namespaces. This allows containers, i.e.
|
|
|
|
|
vservers, to use user namespaces to provide different
|
|
|
|
|
user info for different servers. If unsure, say N.
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config AUDIT
|
|
|
|
|
bool "Auditing support"
|
2005-05-11 16:52:45 +07:00
|
|
|
depends on NET
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Enable auditing infrastructure that can be used with another
|
|
|
|
|
kernel subsystem, such as SELinux (which requires this for
|
|
|
|
|
logging of avc messages output). Does not do system-call
|
|
|
|
|
auditing without CONFIG_AUDITSYSCALL.
|
|
|
|
|
|
|
|
|
|
config AUDITSYSCALL
|
|
|
|
|
bool "Enable system-call auditing support"
|
2006-01-06 15:19:28 +07:00
|
|
|
depends on AUDIT && (X86 || PPC || PPC64 || S390 || IA64 || UML || SPARC64)
|
2005-04-17 05:20:36 +07:00
|
|
|
default y if SECURITY_SELINUX
|
|
|
|
|
help
|
|
|
|
|
Enable low-overhead system-call auditing infrastructure that
|
|
|
|
|
can be used independently or with another kernel subsystem,
|
[PATCH] audit: path-based rules
In this implementation, audit registers inotify watches on the parent
directories of paths specified in audit rules. When audit's inotify
event handler is called, it updates any affected rules based on the
filesystem event. If the parent directory is renamed, removed, or its
filesystem is unmounted, audit removes all rules referencing that
inotify watch.
To keep things simple, this implementation limits location-based
auditing to the directory entries in an existing directory. Given
a path-based rule for /foo/bar/passwd, the following table applies:
passwd modified -- audit event logged
passwd replaced -- audit event logged, rules list updated
bar renamed -- rule removed
foo renamed -- untracked, meaning that the rule now applies to
the new location
Audit users typically want to have many rules referencing filesystem
objects, which can significantly impact filtering performance. This
patch also adds an inode-number-based rule hash to mitigate this
situation.
The patch is relative to the audit git tree:
http://kernel.org/git/?p=linux/kernel/git/viro/audit-current.git;a=summary
and uses the inotify kernel API:
http://lkml.org/lkml/2006/6/1/145
Signed-off-by: Amy Griffis <amy.griffis@hp.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2006-04-08 03:55:56 +07:00
|
|
|
such as SELinux. To use audit's filesystem watch feature, please
|
|
|
|
|
ensure that INOTIFY is configured.
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
config IKCONFIG
|
2006-10-01 13:27:25 +07:00
|
|
|
tristate "Kernel .config support"
|
2005-04-17 05:20:36 +07:00
|
|
|
---help---
|
|
|
|
|
This option enables the complete Linux kernel ".config" file
|
|
|
|
|
contents to be saved in the kernel. It provides documentation
|
|
|
|
|
of which kernel options are used in a running kernel or in an
|
|
|
|
|
on-disk kernel. This information can be extracted from the kernel
|
|
|
|
|
image file with the script scripts/extract-ikconfig and used as
|
|
|
|
|
input to rebuild the current kernel or to build another kernel.
|
|
|
|
|
It can also be extracted from a running kernel by reading
|
|
|
|
|
/proc/config.gz if enabled (below).
|
|
|
|
|
|
|
|
|
|
config IKCONFIG_PROC
|
|
|
|
|
bool "Enable access to .config through /proc/config.gz"
|
|
|
|
|
depends on IKCONFIG && PROC_FS
|
|
|
|
|
---help---
|
|
|
|
|
This option enables access to the kernel configuration file
|
|
|
|
|
through /proc/config.gz.
|
|
|
|
|
|
2007-05-08 14:31:15 +07:00
|
|
|
config LOG_BUF_SHIFT
|
|
|
|
|
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
|
|
|
|
|
range 12 21
|
|
|
|
|
default 17 if S390 || LOCKDEP
|
|
|
|
|
default 16 if X86_NUMAQ || IA64
|
|
|
|
|
default 15 if SMP
|
|
|
|
|
default 14
|
|
|
|
|
help
|
|
|
|
|
Select kernel log buffer size as a power of 2.
|
|
|
|
|
Defaults and Examples:
|
|
|
|
|
17 => 128 KB for S/390
|
|
|
|
|
16 => 64 KB for x86 NUMAQ or IA-64
|
|
|
|
|
15 => 32 KB for SMP
|
|
|
|
|
14 => 16 KB for uniprocessor
|
|
|
|
|
13 => 8 KB
|
|
|
|
|
12 => 4 KB
|
|
|
|
|
|
Task Control Groups: basic task cgroup framework
Generic Process Control Groups
--------------------------
There have recently been various proposals floating around for
resource management/accounting and other task grouping subsystems in
the kernel, including ResGroups, User BeanCounters, NSProxy
cgroups, and others. These all need the basic abstraction of being
able to group together multiple processes in an aggregate, in order to
track/limit the resources permitted to those processes, or control
other behaviour of the processes, and all implement this grouping in
different ways.
This patchset provides a framework for tracking and grouping processes
into arbitrary "cgroups" and assigning arbitrary state to those
groupings, in order to control the behaviour of the cgroup as an
aggregate.
The intention is that the various resource management and
virtualization/cgroup efforts can also become task cgroup
clients, with the result that:
- the userspace APIs are (somewhat) normalised
- it's easier to test e.g. the ResGroups CPU controller in
conjunction with the BeanCounters memory controller, or use either of
them as the resource-control portion of a virtual server system.
- the additional kernel footprint of any of the competing resource
management systems is substantially reduced, since it doesn't need
to provide process grouping/containment, hence improving their
chances of getting into the kernel
This patch:
Add the main task cgroups framework - the cgroup filesystem, and the
basic structures for tracking membership and associating subsystem state
objects to tasks.
Signed-off-by: Paul Menage <menage@google.com>
Cc: Serge E. Hallyn <serue@us.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Dave Hansen <haveblue@us.ibm.com>
Cc: Balbir Singh <balbir@in.ibm.com>
Cc: Paul Jackson <pj@sgi.com>
Cc: Kirill Korotaev <dev@openvz.org>
Cc: Herbert Poetzl <herbert@13thfloor.at>
Cc: Srivatsa Vaddagiri <vatsa@in.ibm.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-10-19 13:39:30 +07:00
|
|
|
config CGROUPS
|
|
|
|
|
bool "Control Group support"
|
|
|
|
|
help
|
|
|
|
|
This option will let you use process cgroup subsystems
|
|
|
|
|
such as Cpusets
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config CPUSETS
|
|
|
|
|
bool "Cpuset support"
|
|
|
|
|
depends on SMP
|
|
|
|
|
help
|
2005-07-28 01:45:11 +07:00
|
|
|
This option will let you create and manage CPUSETs which
|
2005-04-17 05:20:36 +07:00
|
|
|
allow dynamically partitioning a system into sets of CPUs and
|
|
|
|
|
Memory Nodes and assigning tasks to run only within those sets.
|
|
|
|
|
This is primarily useful on large SMP or NUMA systems.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2007-10-15 22:00:07 +07:00
|
|
|
config FAIR_GROUP_SCHED
|
2007-10-15 22:00:12 +07:00
|
|
|
bool "Fair group CPU scheduler"
|
2007-10-15 22:00:09 +07:00
|
|
|
default y
|
2007-10-15 22:00:09 +07:00
|
|
|
depends on EXPERIMENTAL
|
2007-10-15 22:00:07 +07:00
|
|
|
help
|
2007-10-15 22:00:12 +07:00
|
|
|
This feature lets CPU scheduler recognize task groups and control CPU
|
2007-10-15 22:00:09 +07:00
|
|
|
bandwidth allocation to such task groups.
|
2007-10-15 22:00:07 +07:00
|
|
|
|
2007-10-15 22:00:09 +07:00
|
|
|
choice
|
|
|
|
|
depends on FAIR_GROUP_SCHED
|
|
|
|
|
prompt "Basis for grouping tasks"
|
|
|
|
|
default FAIR_USER_SCHED
|
|
|
|
|
|
2007-10-15 22:00:12 +07:00
|
|
|
config FAIR_USER_SCHED
|
|
|
|
|
bool "user id"
|
|
|
|
|
help
|
|
|
|
|
This option will choose userid as the basis for grouping
|
|
|
|
|
tasks, thus providing equal CPU bandwidth to each user.
|
2007-10-15 22:00:09 +07:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2006-09-14 16:23:28 +07:00
|
|
|
config SYSFS_DEPRECATED
|
|
|
|
|
bool "Create deprecated sysfs files"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option creates deprecated symlinks such as the
|
|
|
|
|
"device"-link, the <subsystem>:<name>-link, and the
|
|
|
|
|
"bus"-link. It may also add deprecated key in the
|
|
|
|
|
uevent environment.
|
|
|
|
|
None of these features or values should be used today, as
|
|
|
|
|
they export driver core implementation details to userspace
|
|
|
|
|
or export properties which can't be kept stable across kernel
|
|
|
|
|
releases.
|
|
|
|
|
|
|
|
|
|
If enabled, this option will also move any device structures
|
2007-05-09 12:12:20 +07:00
|
|
|
that belong to a class, back into the /sys/class hierarchy, in
|
2006-09-14 16:23:28 +07:00
|
|
|
order to support older versions of udev.
|
|
|
|
|
|
|
|
|
|
If you are using a distro that was released in 2006 or later,
|
|
|
|
|
it should be safe to say N here.
|
|
|
|
|
|
2006-03-24 01:56:55 +07:00
|
|
|
config RELAY
|
|
|
|
|
bool "Kernel->user space relay support (formerly relayfs)"
|
|
|
|
|
help
|
|
|
|
|
This option enables support for relay interface support in
|
|
|
|
|
certain file systems (such as debugfs).
|
|
|
|
|
It is designed to provide an efficient mechanism for tools and
|
|
|
|
|
facilities to relay large amounts of data from kernel space to
|
|
|
|
|
user space.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-03-06 16:42:17 +07:00
|
|
|
config BLK_DEV_INITRD
|
|
|
|
|
bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
|
|
|
|
|
depends on BROKEN || !FRV
|
|
|
|
|
help
|
|
|
|
|
The initial RAM filesystem is a ramfs which is loaded by the
|
|
|
|
|
boot loader (loadlin or lilo) and that is mounted as root
|
|
|
|
|
before the normal boot procedure. It is typically used to
|
|
|
|
|
load modules needed to mount the "real" root file system,
|
|
|
|
|
etc. See <file:Documentation/initrd.txt> for details.
|
|
|
|
|
|
|
|
|
|
If RAM disk support (BLK_DEV_RAM) is also included, this
|
|
|
|
|
also enables initial RAM disk (initrd) support and adds
|
|
|
|
|
15 Kbytes (more on some other architectures) to the kernel size.
|
|
|
|
|
|
|
|
|
|
If unsure say Y.
|
|
|
|
|
|
2007-02-10 16:44:43 +07:00
|
|
|
if BLK_DEV_INITRD
|
|
|
|
|
|
2005-08-11 01:44:50 +07:00
|
|
|
source "usr/Kconfig"
|
|
|
|
|
|
2007-02-10 16:44:43 +07:00
|
|
|
endif
|
|
|
|
|
|
Move size optimization option outside of EMBEDDED menu, mark it EXPERIMENTAL
Also, disable on sparc64 - a number of people report breakage. Probably
a compiler bug, but it's quite possible that it tickles some latent
kernel problem too.
It still defaults to 'y' everywhere else (when enabled through
EXPERIMENTAL), and Dave Jones points out that Fedora (and RHEL4) has
been building with size optimizations for a long time on x86, x86-64,
ia64, s390, s390x, ppc32 and ppc64. So it is really only moderately
experimental, but the sparc64 breakage certainly shows that it can
trigger "issues".
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-12-15 09:52:21 +07:00
|
|
|
config CC_OPTIMIZE_FOR_SIZE
|
|
|
|
|
bool "Optimize for size (Look out for broken compilers!)"
|
|
|
|
|
default y
|
2007-07-25 09:27:05 +07:00
|
|
|
depends on ARM || H8300 || SUPERH || EXPERIMENTAL
|
Move size optimization option outside of EMBEDDED menu, mark it EXPERIMENTAL
Also, disable on sparc64 - a number of people report breakage. Probably
a compiler bug, but it's quite possible that it tickles some latent
kernel problem too.
It still defaults to 'y' everywhere else (when enabled through
EXPERIMENTAL), and Dave Jones points out that Fedora (and RHEL4) has
been building with size optimizations for a long time on x86, x86-64,
ia64, s390, s390x, ppc32 and ppc64. So it is really only moderately
experimental, but the sparc64 breakage certainly shows that it can
trigger "issues".
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-12-15 09:52:21 +07:00
|
|
|
help
|
|
|
|
|
Enabling this option will pass "-Os" instead of "-O2" to gcc
|
|
|
|
|
resulting in a smaller kernel.
|
|
|
|
|
|
|
|
|
|
WARNING: some versions of gcc may generate incorrect code with this
|
|
|
|
|
option. If problems are observed, a gcc upgrade may be needed.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2006-10-01 13:28:13 +07:00
|
|
|
config SYSCTL
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
menuconfig EMBEDDED
|
|
|
|
|
bool "Configure standard kernel features (for small systems)"
|
|
|
|
|
help
|
|
|
|
|
This option allows certain base kernel options and settings
|
|
|
|
|
to be disabled or tweaked. This is for specialized
|
|
|
|
|
environments which can tolerate a "non-standard" kernel.
|
|
|
|
|
Only use this if you really know what you are doing.
|
|
|
|
|
|
2006-09-17 02:15:53 +07:00
|
|
|
config UID16
|
|
|
|
|
bool "Enable 16-bit UID system calls" if EMBEDDED
|
blackfin architecture
This adds support for the Analog Devices Blackfin processor architecture, and
currently supports the BF533, BF532, BF531, BF537, BF536, BF534, and BF561
(Dual Core) devices, with a variety of development platforms including those
avaliable from Analog Devices (BF533-EZKit, BF533-STAMP, BF537-STAMP,
BF561-EZKIT), and Bluetechnix! Tinyboards.
The Blackfin architecture was jointly developed by Intel and Analog Devices
Inc. (ADI) as the Micro Signal Architecture (MSA) core and introduced it in
December of 2000. Since then ADI has put this core into its Blackfin
processor family of devices. The Blackfin core has the advantages of a clean,
orthogonal,RISC-like microprocessor instruction set. It combines a dual-MAC
(Multiply/Accumulate), state-of-the-art signal processing engine and
single-instruction, multiple-data (SIMD) multimedia capabilities into a single
instruction-set architecture.
The Blackfin architecture, including the instruction set, is described by the
ADSP-BF53x/BF56x Blackfin Processor Programming Reference
http://blackfin.uclinux.org/gf/download/frsrelease/29/2549/Blackfin_PRM.pdf
The Blackfin processor is already supported by major releases of gcc, and
there are binary and source rpms/tarballs for many architectures at:
http://blackfin.uclinux.org/gf/project/toolchain/frs There is complete
documentation, including "getting started" guides available at:
http://docs.blackfin.uclinux.org/ which provides links to the sources and
patches you will need in order to set up a cross-compiling environment for
bfin-linux-uclibc
This patch, as well as the other patches (toolchain, distribution,
uClibc) are actively supported by Analog Devices Inc, at:
http://blackfin.uclinux.org/
We have tested this on LTP, and our test plan (including pass/fails) can
be found at:
http://docs.blackfin.uclinux.org/doku.php?id=testing_the_linux_kernel
[m.kozlowski@tuxland.pl: balance parenthesis in blackfin header files]
Signed-off-by: Bryan Wu <bryan.wu@analog.com>
Signed-off-by: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Signed-off-by: Aubrey Li <aubrey.li@analog.com>
Signed-off-by: Jie Zhang <jie.zhang@analog.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-07 04:50:22 +07:00
|
|
|
depends on ARM || BFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && SPARC32_COMPAT) || UML || (X86_64 && IA32_EMULATION)
|
2006-09-17 02:15:53 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This enables the legacy 16-bit UID syscall wrappers.
|
|
|
|
|
|
2006-09-27 15:51:04 +07:00
|
|
|
config SYSCTL_SYSCALL
|
2006-10-01 13:28:13 +07:00
|
|
|
bool "Sysctl syscall support" if EMBEDDED
|
2006-11-09 08:44:51 +07:00
|
|
|
default y
|
2006-09-27 15:51:04 +07:00
|
|
|
select SYSCTL
|
2006-09-17 02:15:53 +07:00
|
|
|
---help---
|
2006-11-09 08:44:51 +07:00
|
|
|
sys_sysctl uses binary paths that have been found challenging
|
|
|
|
|
to properly maintain and use. The interface in /proc/sys
|
|
|
|
|
using paths with ascii names is now the primary path to this
|
|
|
|
|
information.
|
2006-09-27 15:51:04 +07:00
|
|
|
|
2006-11-09 08:44:51 +07:00
|
|
|
Almost nothing using the binary sysctl interface so if you are
|
|
|
|
|
trying to save some space it is probably safe to disable this,
|
|
|
|
|
making your kernel marginally smaller.
|
2006-09-27 15:51:04 +07:00
|
|
|
|
2006-11-09 08:44:51 +07:00
|
|
|
If unsure say Y here.
|
2006-09-17 02:15:53 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config KALLSYMS
|
2006-12-13 01:25:11 +07:00
|
|
|
bool "Load all symbols for debugging/ksymoops" if EMBEDDED
|
2005-04-17 05:20:36 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y here to let the kernel print out symbolic crash information and
|
|
|
|
|
symbolic stack backtraces. This increases the size of the kernel
|
|
|
|
|
somewhat, as all symbols have to be loaded into the kernel image.
|
|
|
|
|
|
|
|
|
|
config KALLSYMS_ALL
|
|
|
|
|
bool "Include all symbols in kallsyms"
|
|
|
|
|
depends on DEBUG_KERNEL && KALLSYMS
|
|
|
|
|
help
|
|
|
|
|
Normally kallsyms only contains the symbols of functions, for nicer
|
|
|
|
|
OOPS messages. Some debuggers can use kallsyms for other
|
2005-07-20 10:43:05 +07:00
|
|
|
symbols too: say Y here to include all symbols, if you need them
|
|
|
|
|
and you don't care about adding 300k to the size of your kernel.
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
Say N.
|
|
|
|
|
|
|
|
|
|
config KALLSYMS_EXTRA_PASS
|
|
|
|
|
bool "Do an extra kallsyms pass"
|
|
|
|
|
depends on KALLSYMS
|
|
|
|
|
help
|
|
|
|
|
If kallsyms is not working correctly, the build will fail with
|
|
|
|
|
inconsistent kallsyms data. If that occurs, log a bug report and
|
|
|
|
|
turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
|
|
|
|
|
Always say N here unless you find a bug in kallsyms, which must be
|
|
|
|
|
reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
|
|
|
|
|
you wait for kallsyms to be fixed.
|
|
|
|
|
|
2005-05-01 22:59:02 +07:00
|
|
|
|
2005-11-17 02:27:07 +07:00
|
|
|
config HOTPLUG
|
|
|
|
|
bool "Support for hot-pluggable devices" if EMBEDDED
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option is provided for the case where no hotplug or uevent
|
|
|
|
|
capabilities is wanted by the kernel. You should only consider
|
|
|
|
|
disabling this option for embedded systems that do not use modules, a
|
|
|
|
|
dynamic /dev tree, or dynamic device discovery. Just say Y.
|
|
|
|
|
|
2005-05-01 22:59:02 +07:00
|
|
|
config PRINTK
|
|
|
|
|
default y
|
|
|
|
|
bool "Enable support for printk" if EMBEDDED
|
|
|
|
|
help
|
|
|
|
|
This option enables normal printk support. Removing it
|
|
|
|
|
eliminates most of the message strings from the kernel image
|
|
|
|
|
and makes the kernel more or less silent. As this makes it
|
|
|
|
|
very difficult to diagnose system problems, saying N here is
|
|
|
|
|
strongly discouraged.
|
|
|
|
|
|
2005-05-01 22:59:01 +07:00
|
|
|
config BUG
|
|
|
|
|
bool "BUG() support" if EMBEDDED
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Disabling this option eliminates support for BUG and WARN, reducing
|
|
|
|
|
the size of your kernel image and potentially quietly ignoring
|
|
|
|
|
numerous fatal conditions. You should only consider disabling this
|
|
|
|
|
option for embedded systems with no facilities for reporting errors.
|
|
|
|
|
Just say Y.
|
|
|
|
|
|
2006-01-08 16:05:25 +07:00
|
|
|
config ELF_CORE
|
|
|
|
|
default y
|
|
|
|
|
bool "Enable ELF core dumps" if EMBEDDED
|
|
|
|
|
help
|
|
|
|
|
Enable support for generating core dumps. Disabling saves about 4k.
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config BASE_FULL
|
|
|
|
|
default y
|
|
|
|
|
bool "Enable full-sized data structures for core" if EMBEDDED
|
|
|
|
|
help
|
|
|
|
|
Disabling this option reduces the size of miscellaneous core
|
|
|
|
|
kernel data structures. This saves memory on small machines,
|
|
|
|
|
but may reduce performance.
|
|
|
|
|
|
|
|
|
|
config FUTEX
|
|
|
|
|
bool "Enable futex support" if EMBEDDED
|
|
|
|
|
default y
|
2006-06-27 16:54:53 +07:00
|
|
|
select RT_MUTEXES
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Disabling this option will cause the kernel to be built without
|
|
|
|
|
support for "fast userspace mutexes". The resulting kernel may not
|
|
|
|
|
run glibc-based applications correctly.
|
|
|
|
|
|
2007-05-11 12:23:11 +07:00
|
|
|
config ANON_INODES
|
2007-07-31 14:39:10 +07:00
|
|
|
bool
|
2007-05-11 12:23:11 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config EPOLL
|
|
|
|
|
bool "Enable eventpoll support" if EMBEDDED
|
|
|
|
|
default y
|
2007-07-31 14:39:10 +07:00
|
|
|
select ANON_INODES
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Disabling this option will cause the kernel to be built without
|
|
|
|
|
support for epoll family of system calls.
|
|
|
|
|
|
signal/timer/event: signalfd core
This patch series implements the new signalfd() system call.
I took part of the original Linus code (and you know how badly it can be
broken :), and I added even more breakage ;) Signals are fetched from the same
signal queue used by the process, so signalfd will compete with standard
kernel delivery in dequeue_signal(). If you want to reliably fetch signals on
the signalfd file, you need to block them with sigprocmask(SIG_BLOCK). This
seems to be working fine on my Dual Opteron machine. I made a quick test
program for it:
http://www.xmailserver.org/signafd-test.c
The signalfd() system call implements signal delivery into a file descriptor
receiver. The signalfd file descriptor if created with the following API:
int signalfd(int ufd, const sigset_t *mask, size_t masksize);
The "ufd" parameter allows to change an existing signalfd sigmask, w/out going
to close/create cycle (Linus idea). Use "ufd" == -1 if you want a brand new
signalfd file.
The "mask" allows to specify the signal mask of signals that we are interested
in. The "masksize" parameter is the size of "mask".
The signalfd fd supports the poll(2) and read(2) system calls. The poll(2)
will return POLLIN when signals are available to be dequeued. As a direct
consequence of supporting the Linux poll subsystem, the signalfd fd can use
used together with epoll(2) too.
The read(2) system call will return a "struct signalfd_siginfo" structure in
the userspace supplied buffer. The return value is the number of bytes copied
in the supplied buffer, or -1 in case of error. The read(2) call can also
return 0, in case the sighand structure to which the signalfd was attached,
has been orphaned. The O_NONBLOCK flag is also supported, and read(2) will
return -EAGAIN in case no signal is available.
If the size of the buffer passed to read(2) is lower than sizeof(struct
signalfd_siginfo), -EINVAL is returned. A read from the signalfd can also
return -ERESTARTSYS in case a signal hits the process. The format of the
struct signalfd_siginfo is, and the valid fields depends of the (->code &
__SI_MASK) value, in the same way a struct siginfo would:
struct signalfd_siginfo {
__u32 signo; /* si_signo */
__s32 err; /* si_errno */
__s32 code; /* si_code */
__u32 pid; /* si_pid */
__u32 uid; /* si_uid */
__s32 fd; /* si_fd */
__u32 tid; /* si_fd */
__u32 band; /* si_band */
__u32 overrun; /* si_overrun */
__u32 trapno; /* si_trapno */
__s32 status; /* si_status */
__s32 svint; /* si_int */
__u64 svptr; /* si_ptr */
__u64 utime; /* si_utime */
__u64 stime; /* si_stime */
__u64 addr; /* si_addr */
};
[akpm@linux-foundation.org: fix signalfd_copyinfo() on i386]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 12:23:13 +07:00
|
|
|
config SIGNALFD
|
|
|
|
|
bool "Enable signalfd() system call" if EMBEDDED
|
2007-07-31 14:39:10 +07:00
|
|
|
select ANON_INODES
|
signal/timer/event: signalfd core
This patch series implements the new signalfd() system call.
I took part of the original Linus code (and you know how badly it can be
broken :), and I added even more breakage ;) Signals are fetched from the same
signal queue used by the process, so signalfd will compete with standard
kernel delivery in dequeue_signal(). If you want to reliably fetch signals on
the signalfd file, you need to block them with sigprocmask(SIG_BLOCK). This
seems to be working fine on my Dual Opteron machine. I made a quick test
program for it:
http://www.xmailserver.org/signafd-test.c
The signalfd() system call implements signal delivery into a file descriptor
receiver. The signalfd file descriptor if created with the following API:
int signalfd(int ufd, const sigset_t *mask, size_t masksize);
The "ufd" parameter allows to change an existing signalfd sigmask, w/out going
to close/create cycle (Linus idea). Use "ufd" == -1 if you want a brand new
signalfd file.
The "mask" allows to specify the signal mask of signals that we are interested
in. The "masksize" parameter is the size of "mask".
The signalfd fd supports the poll(2) and read(2) system calls. The poll(2)
will return POLLIN when signals are available to be dequeued. As a direct
consequence of supporting the Linux poll subsystem, the signalfd fd can use
used together with epoll(2) too.
The read(2) system call will return a "struct signalfd_siginfo" structure in
the userspace supplied buffer. The return value is the number of bytes copied
in the supplied buffer, or -1 in case of error. The read(2) call can also
return 0, in case the sighand structure to which the signalfd was attached,
has been orphaned. The O_NONBLOCK flag is also supported, and read(2) will
return -EAGAIN in case no signal is available.
If the size of the buffer passed to read(2) is lower than sizeof(struct
signalfd_siginfo), -EINVAL is returned. A read from the signalfd can also
return -ERESTARTSYS in case a signal hits the process. The format of the
struct signalfd_siginfo is, and the valid fields depends of the (->code &
__SI_MASK) value, in the same way a struct siginfo would:
struct signalfd_siginfo {
__u32 signo; /* si_signo */
__s32 err; /* si_errno */
__s32 code; /* si_code */
__u32 pid; /* si_pid */
__u32 uid; /* si_uid */
__s32 fd; /* si_fd */
__u32 tid; /* si_fd */
__u32 band; /* si_band */
__u32 overrun; /* si_overrun */
__u32 trapno; /* si_trapno */
__s32 status; /* si_status */
__s32 svint; /* si_int */
__u64 svptr; /* si_ptr */
__u64 utime; /* si_utime */
__u64 stime; /* si_stime */
__u64 addr; /* si_addr */
};
[akpm@linux-foundation.org: fix signalfd_copyinfo() on i386]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 12:23:13 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable the signalfd() system call that allows to receive signals
|
|
|
|
|
on a file descriptor.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
signal/timer/event: timerfd core
This patch introduces a new system call for timers events delivered though
file descriptors. This allows timer event to be used with standard POSIX
poll(2), select(2) and read(2). As a consequence of supporting the Linux
f_op->poll subsystem, they can be used with epoll(2) too.
The system call is defined as:
int timerfd(int ufd, int clockid, int flags, const struct itimerspec *utmr);
The "ufd" parameter allows for re-use (re-programming) of an existing timerfd
w/out going through the close/open cycle (same as signalfd). If "ufd" is -1,
s new file descriptor will be created, otherwise the existing "ufd" will be
re-programmed.
The "clockid" parameter is either CLOCK_MONOTONIC or CLOCK_REALTIME. The time
specified in the "utmr->it_value" parameter is the expiry time for the timer.
If the TFD_TIMER_ABSTIME flag is set in "flags", this is an absolute time,
otherwise it's a relative time.
If the time specified in the "utmr->it_interval" is not zero (.tv_sec == 0,
tv_nsec == 0), this is the period at which the following ticks should be
generated.
The "utmr->it_interval" should be set to zero if only one tick is requested.
Setting the "utmr->it_value" to zero will disable the timer, or will create a
timerfd without the timer enabled.
The function returns the new (or same, in case "ufd" is a valid timerfd
descriptor) file, or -1 in case of error.
As stated before, the timerfd file descriptor supports poll(2), select(2) and
epoll(2). When a timer event happened on the timerfd, a POLLIN mask will be
returned.
The read(2) call can be used, and it will return a u32 variable holding the
number of "ticks" that happened on the interface since the last call to
read(2). The read(2) call supportes the O_NONBLOCK flag too, and EAGAIN will
be returned if no ticks happened.
A quick test program, shows timerfd working correctly on my amd64 box:
http://www.xmailserver.org/timerfd-test.c
[akpm@linux-foundation.org: add sys_timerfd to sys_ni.c]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 12:23:16 +07:00
|
|
|
config TIMERFD
|
|
|
|
|
bool "Enable timerfd() system call" if EMBEDDED
|
2007-07-31 14:39:10 +07:00
|
|
|
select ANON_INODES
|
2007-09-19 12:46:41 +07:00
|
|
|
depends on BROKEN
|
signal/timer/event: timerfd core
This patch introduces a new system call for timers events delivered though
file descriptors. This allows timer event to be used with standard POSIX
poll(2), select(2) and read(2). As a consequence of supporting the Linux
f_op->poll subsystem, they can be used with epoll(2) too.
The system call is defined as:
int timerfd(int ufd, int clockid, int flags, const struct itimerspec *utmr);
The "ufd" parameter allows for re-use (re-programming) of an existing timerfd
w/out going through the close/open cycle (same as signalfd). If "ufd" is -1,
s new file descriptor will be created, otherwise the existing "ufd" will be
re-programmed.
The "clockid" parameter is either CLOCK_MONOTONIC or CLOCK_REALTIME. The time
specified in the "utmr->it_value" parameter is the expiry time for the timer.
If the TFD_TIMER_ABSTIME flag is set in "flags", this is an absolute time,
otherwise it's a relative time.
If the time specified in the "utmr->it_interval" is not zero (.tv_sec == 0,
tv_nsec == 0), this is the period at which the following ticks should be
generated.
The "utmr->it_interval" should be set to zero if only one tick is requested.
Setting the "utmr->it_value" to zero will disable the timer, or will create a
timerfd without the timer enabled.
The function returns the new (or same, in case "ufd" is a valid timerfd
descriptor) file, or -1 in case of error.
As stated before, the timerfd file descriptor supports poll(2), select(2) and
epoll(2). When a timer event happened on the timerfd, a POLLIN mask will be
returned.
The read(2) call can be used, and it will return a u32 variable holding the
number of "ticks" that happened on the interface since the last call to
read(2). The read(2) call supportes the O_NONBLOCK flag too, and EAGAIN will
be returned if no ticks happened.
A quick test program, shows timerfd working correctly on my amd64 box:
http://www.xmailserver.org/timerfd-test.c
[akpm@linux-foundation.org: add sys_timerfd to sys_ni.c]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 12:23:16 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable the timerfd() system call that allows to receive timer
|
|
|
|
|
events on a file descriptor.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
signal/timer/event: eventfd core
This is a very simple and light file descriptor, that can be used as event
wait/dispatch by userspace (both wait and dispatch) and by the kernel
(dispatch only). It can be used instead of pipe(2) in all cases where those
would simply be used to signal events. Their kernel overhead is much lower
than pipes, and they do not consume two fds. When used in the kernel, it can
offer an fd-bridge to enable, for example, functionalities like KAIO or
syslets/threadlets to signal to an fd the completion of certain operations.
But more in general, an eventfd can be used by the kernel to signal readiness,
in a POSIX poll/select way, of interfaces that would otherwise be incompatible
with it. The API is:
int eventfd(unsigned int count);
The eventfd API accepts an initial "count" parameter, and returns an eventfd
fd. It supports poll(2) (POLLIN, POLLOUT, POLLERR), read(2) and write(2).
The POLLIN flag is raised when the internal counter is greater than zero.
The POLLOUT flag is raised when at least a value of "1" can be written to the
internal counter.
The POLLERR flag is raised when an overflow in the counter value is detected.
The write(2) operation can never overflow the counter, since it blocks (unless
O_NONBLOCK is set, in which case -EAGAIN is returned).
But the eventfd_signal() function can do it, since it's supposed to not sleep
during its operation.
The read(2) function reads the __u64 counter value, and reset the internal
value to zero. If the value read is equal to (__u64) -1, an overflow happened
on the internal counter (due to 2^64 eventfd_signal() posts that has never
been retired - unlickely, but possible).
The write(2) call writes an __u64 count value, and adds it to the current
counter. The eventfd fd supports O_NONBLOCK also.
On the kernel side, we have:
struct file *eventfd_fget(int fd);
int eventfd_signal(struct file *file, unsigned int n);
The eventfd_fget() should be called to get a struct file* from an eventfd fd
(this is an fget() + check of f_op being an eventfd fops pointer).
The kernel can then call eventfd_signal() every time it wants to post an event
to userspace. The eventfd_signal() function can be called from any context.
An eventfd() simple test and bench is available here:
http://www.xmailserver.org/eventfd-bench.c
This is the eventfd-based version of pipetest-4 (pipe(2) based):
http://www.xmailserver.org/pipetest-4.c
Not that performance matters much in the eventfd case, but eventfd-bench
shows almost as double as performance than pipetest-4.
[akpm@linux-foundation.org: fix i386 build]
[akpm@linux-foundation.org: add sys_eventfd to sys_ni.c]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 12:23:19 +07:00
|
|
|
config EVENTFD
|
|
|
|
|
bool "Enable eventfd() system call" if EMBEDDED
|
2007-07-31 14:39:10 +07:00
|
|
|
select ANON_INODES
|
signal/timer/event: eventfd core
This is a very simple and light file descriptor, that can be used as event
wait/dispatch by userspace (both wait and dispatch) and by the kernel
(dispatch only). It can be used instead of pipe(2) in all cases where those
would simply be used to signal events. Their kernel overhead is much lower
than pipes, and they do not consume two fds. When used in the kernel, it can
offer an fd-bridge to enable, for example, functionalities like KAIO or
syslets/threadlets to signal to an fd the completion of certain operations.
But more in general, an eventfd can be used by the kernel to signal readiness,
in a POSIX poll/select way, of interfaces that would otherwise be incompatible
with it. The API is:
int eventfd(unsigned int count);
The eventfd API accepts an initial "count" parameter, and returns an eventfd
fd. It supports poll(2) (POLLIN, POLLOUT, POLLERR), read(2) and write(2).
The POLLIN flag is raised when the internal counter is greater than zero.
The POLLOUT flag is raised when at least a value of "1" can be written to the
internal counter.
The POLLERR flag is raised when an overflow in the counter value is detected.
The write(2) operation can never overflow the counter, since it blocks (unless
O_NONBLOCK is set, in which case -EAGAIN is returned).
But the eventfd_signal() function can do it, since it's supposed to not sleep
during its operation.
The read(2) function reads the __u64 counter value, and reset the internal
value to zero. If the value read is equal to (__u64) -1, an overflow happened
on the internal counter (due to 2^64 eventfd_signal() posts that has never
been retired - unlickely, but possible).
The write(2) call writes an __u64 count value, and adds it to the current
counter. The eventfd fd supports O_NONBLOCK also.
On the kernel side, we have:
struct file *eventfd_fget(int fd);
int eventfd_signal(struct file *file, unsigned int n);
The eventfd_fget() should be called to get a struct file* from an eventfd fd
(this is an fget() + check of f_op being an eventfd fops pointer).
The kernel can then call eventfd_signal() every time it wants to post an event
to userspace. The eventfd_signal() function can be called from any context.
An eventfd() simple test and bench is available here:
http://www.xmailserver.org/eventfd-bench.c
This is the eventfd-based version of pipetest-4 (pipe(2) based):
http://www.xmailserver.org/pipetest-4.c
Not that performance matters much in the eventfd case, but eventfd-bench
shows almost as double as performance than pipetest-4.
[akpm@linux-foundation.org: fix i386 build]
[akpm@linux-foundation.org: add sys_eventfd to sys_ni.c]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 12:23:19 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable the eventfd() system call that allows to receive both
|
|
|
|
|
kernel notification (ie. KAIO) or userspace notifications.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config SHMEM
|
|
|
|
|
bool "Use full shmem filesystem" if EMBEDDED
|
|
|
|
|
default y
|
|
|
|
|
depends on MMU
|
|
|
|
|
help
|
|
|
|
|
The shmem is an internal filesystem used to manage shared memory.
|
|
|
|
|
It is backed by swap and manages resource limits. It is also exported
|
|
|
|
|
to userspace as tmpfs if TMPFS is enabled. Disabling this
|
|
|
|
|
option replaces shmem and tmpfs with the much simpler ramfs code,
|
|
|
|
|
which may be appropriate on small systems without swap.
|
|
|
|
|
|
2006-06-30 15:55:45 +07:00
|
|
|
config VM_EVENT_COUNTERS
|
|
|
|
|
default y
|
|
|
|
|
bool "Enable VM event counters for /proc/vmstat" if EMBEDDED
|
|
|
|
|
help
|
2006-12-22 16:06:10 +07:00
|
|
|
VM event counters are needed for event counts to be shown.
|
|
|
|
|
This option allows the disabling of the VM event counters
|
|
|
|
|
on EMBEDDED systems. /proc/vmstat will only show page counts
|
|
|
|
|
if VM event counters are disabled.
|
2006-06-30 15:55:45 +07:00
|
|
|
|
2007-05-09 16:32:44 +07:00
|
|
|
config SLUB_DEBUG
|
|
|
|
|
default y
|
|
|
|
|
bool "Enable SLUB debugging support" if EMBEDDED
|
2007-05-10 17:15:40 +07:00
|
|
|
depends on SLUB
|
2007-05-09 16:32:44 +07:00
|
|
|
help
|
|
|
|
|
SLUB has extensive debug support features. Disabling these can
|
|
|
|
|
result in significant savings in code size. This also disables
|
|
|
|
|
SLUB sysfs support. /sys/slab will not exist and there will be
|
|
|
|
|
no support for cache validation etc.
|
|
|
|
|
|
2007-05-07 04:49:36 +07:00
|
|
|
choice
|
|
|
|
|
prompt "Choose SLAB allocator"
|
2007-07-17 18:03:32 +07:00
|
|
|
default SLUB
|
2007-05-07 04:49:36 +07:00
|
|
|
help
|
|
|
|
|
This option allows to select a slab allocator.
|
|
|
|
|
|
|
|
|
|
config SLAB
|
|
|
|
|
bool "SLAB"
|
|
|
|
|
help
|
|
|
|
|
The regular slab allocator that is established and known to work
|
2007-05-09 16:32:47 +07:00
|
|
|
well in all environments. It organizes cache hot objects in
|
2007-05-07 04:49:36 +07:00
|
|
|
per cpu and per node queues. SLAB is the default choice for
|
2007-05-09 16:32:47 +07:00
|
|
|
a slab allocator.
|
2007-05-07 04:49:36 +07:00
|
|
|
|
|
|
|
|
config SLUB
|
|
|
|
|
bool "SLUB (Unqueued Allocator)"
|
|
|
|
|
help
|
|
|
|
|
SLUB is a slab allocator that minimizes cache line usage
|
|
|
|
|
instead of managing queues of cached objects (SLAB approach).
|
|
|
|
|
Per cpu caching is realized using slabs of objects instead
|
|
|
|
|
of queues of objects. SLUB can use memory efficiently
|
2007-05-09 16:32:47 +07:00
|
|
|
and has enhanced diagnostics.
|
2007-05-07 04:49:36 +07:00
|
|
|
|
|
|
|
|
config SLOB
|
2007-07-16 13:38:24 +07:00
|
|
|
depends on EMBEDDED
|
2007-05-07 04:49:36 +07:00
|
|
|
bool "SLOB (Simple Allocator)"
|
|
|
|
|
help
|
|
|
|
|
SLOB replaces the SLAB allocator with a drastically simpler
|
2007-05-17 12:10:49 +07:00
|
|
|
allocator. SLOB is more space efficient than SLAB but does not
|
2007-05-09 16:32:47 +07:00
|
|
|
scale well (single lock for all operations) and is also highly
|
|
|
|
|
susceptible to fragmentation. SLUB can accomplish a higher object
|
|
|
|
|
density. It is usually better to use SLUB instead of SLOB.
|
2007-05-07 04:49:36 +07:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
endmenu # General setup
|
|
|
|
|
|
2006-09-17 02:15:53 +07:00
|
|
|
config RT_MUTEXES
|
|
|
|
|
boolean
|
|
|
|
|
select PLIST
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config TINY_SHMEM
|
|
|
|
|
default !SHMEM
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config BASE_SMALL
|
|
|
|
|
int
|
|
|
|
|
default 0 if BASE_FULL
|
|
|
|
|
default 1 if !BASE_FULL
|
|
|
|
|
|
2007-07-16 13:39:29 +07:00
|
|
|
menuconfig MODULES
|
2005-04-17 05:20:36 +07:00
|
|
|
bool "Enable loadable module support"
|
|
|
|
|
help
|
|
|
|
|
Kernel modules are small pieces of compiled code which can
|
|
|
|
|
be inserted in the running kernel, rather than being
|
|
|
|
|
permanently built into the kernel. You use the "modprobe"
|
|
|
|
|
tool to add (and sometimes remove) them. If you say Y here,
|
|
|
|
|
many parts of the kernel can be built as modules (by
|
|
|
|
|
answering M instead of Y where indicated): this is most
|
|
|
|
|
useful for infrequently used options which are not required
|
|
|
|
|
for booting. For more information, see the man pages for
|
|
|
|
|
modprobe, lsmod, modinfo, insmod and rmmod.
|
|
|
|
|
|
|
|
|
|
If you say Y here, you will need to run "make
|
|
|
|
|
modules_install" to put the modules under /lib/modules/
|
|
|
|
|
where modprobe can find them (you may need to be root to do
|
|
|
|
|
this).
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config MODULE_UNLOAD
|
|
|
|
|
bool "Module unloading"
|
|
|
|
|
depends on MODULES
|
|
|
|
|
help
|
|
|
|
|
Without this option you will not be able to unload any
|
|
|
|
|
modules (note that some modules may not be unloadable
|
|
|
|
|
anyway), which makes your kernel slightly smaller and
|
|
|
|
|
simpler. If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config MODULE_FORCE_UNLOAD
|
|
|
|
|
bool "Forced module unloading"
|
|
|
|
|
depends on MODULE_UNLOAD && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
This option allows you to force a module to unload, even if the
|
|
|
|
|
kernel believes it is unsafe: the kernel will remove the module
|
|
|
|
|
without waiting for anyone to stop using it (using the -f option to
|
|
|
|
|
rmmod). This is mainly for kernel developers and desperate users.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MODVERSIONS
|
2005-12-27 05:04:02 +07:00
|
|
|
bool "Module versioning support"
|
|
|
|
|
depends on MODULES
|
2005-04-17 05:20:36 +07:00
|
|
|
help
|
|
|
|
|
Usually, you have to use modules compiled with your kernel.
|
|
|
|
|
Saying Y here makes it sometimes possible to use modules
|
|
|
|
|
compiled for different kernels, by adding enough information
|
|
|
|
|
to the modules to (hopefully) spot any changes which would
|
|
|
|
|
make them incompatible with the kernel you are running. If
|
|
|
|
|
unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MODULE_SRCVERSION_ALL
|
|
|
|
|
bool "Source checksum for all modules"
|
|
|
|
|
depends on MODULES
|
|
|
|
|
help
|
|
|
|
|
Modules which contain a MODULE_VERSION get an extra "srcversion"
|
|
|
|
|
field inserted into their modinfo section, which contains a
|
|
|
|
|
sum of the source files which made it. This helps maintainers
|
|
|
|
|
see exactly which source was used to build a module (since
|
|
|
|
|
others sometimes change the module source without updating
|
|
|
|
|
the version). With this option, such a "srcversion" field
|
|
|
|
|
will be created for all modules. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config KMOD
|
|
|
|
|
bool "Automatic kernel module loading"
|
|
|
|
|
depends on MODULES
|
|
|
|
|
help
|
|
|
|
|
Normally when you have selected some parts of the kernel to
|
|
|
|
|
be created as kernel modules, you must load them (using the
|
|
|
|
|
"modprobe" command) before you can use them. If you say Y
|
|
|
|
|
here, some parts of the kernel will be able to load modules
|
|
|
|
|
automatically: when a part of the kernel needs a module, it
|
|
|
|
|
runs modprobe with the appropriate arguments, thereby
|
|
|
|
|
loading the module if it is available. If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config STOP_MACHINE
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
|
|
|
|
|
help
|
|
|
|
|
Need stop_machine() primitive.
|
2005-11-04 14:43:35 +07:00
|
|
|
|
|
|
|
|
source "block/Kconfig"
|
2007-10-17 13:27:31 +07:00
|
|
|
|
|
|
|
|
config PREEMPT_NOTIFIERS
|
|
|
|
|
bool
|