BoomMicrophone/nixpkgs-suyu
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
nixpkgs-suyu/pkgs/os-specific/linux/kernel/common-config.nix

597 lines
16 KiB
Nix
Raw Normal View History

kernel: add a warning/note at the top of common-config so that people would hopefully stop breaking the older kernels
2015-03-24 22:34:54 +01:00
/*
WARNING/NOTE: whenever you want to add an option here you need to
either
* mark it as an optional one with `?` suffix,
* or make sure it works for all the versions in nixpkgs,
* or check for which kernel versions it will work (using kernel
changelog, google or whatever) and mark it with `versionOlder` or
`versionAtLeast`.
Then do test your change by building all the kernels (or at least
their configs) in nixpkgs or else you will guarantee lots and lots
of pain to users trying to switch to an older kernel because of some
hardware problems with a new one.
*/
kernel: allow features to be used in common-config Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-08 00:26:33 +02:00
{ stdenv, version, kernelPlatform, extraConfig, features }:
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
with stdenv.lib;
''
linux: Compress kernel modules This reduces the kernel package from 185 to 62 MiB, for a neglible boot time cost.
2016-02-01 17:54:35 +01:00
# Compress kernel modules for a sizable disk space savings.
${optionalString (versionAtLeast version "3.18") ''
MODULE_COMPRESS y
MODULE_COMPRESS_XZ y
''}
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
# Debugging.
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
DEBUG_KERNEL y
TIMER_STATS y
BACKTRACE_SELF_TEST n
CPU_NOTIFIER_ERROR_INJECT? n
DEBUG_DEVRES n
DEBUG_NX_TEST n
DEBUG_STACK_USAGE n
linux: Disable CONFIG_DEBUG_STACKOVERFLOW This got enabled accidentally in e64e3ad88ab612379747dff15b62573bda3f8de4.
2015-03-02 23:34:44 +01:00
${optionalString (!(features.grsecurity or false)) ''
kernel: only use DEBUG_STACKOVERFLOW if !grsecurity Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 15:56:52 +02:00
DEBUG_STACKOVERFLOW n
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
RCU_TORTURE_TEST n
SCHEDSTATS n
linux: Enable detection of hung tasks
2013-08-01 00:50:48 +02:00
DETECT_HUNG_TASK y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
linux: Bump NR_CPUS The default limit (64) is too low for systems like EC2 x1.* instances or Xeon Phis, so let's increase it.
2016-07-11 12:16:19 +02:00
# Bump the maximum number of CPUs to support systems like EC2 x1.*
# instances and Xeon Phi.
${optionalString (stdenv.system == "x86_64-linux") ''
NR_CPUS 384
''}
linux: Make Unix domain sockets builtin This hopefully fixes intermittent initrd failures where udevd cannot create a Unix domain socket: machine# running udev... machine# error getting socket: Address family not supported by protocol machine# error initializing udev control socket machine# error getting socket: Address family not supported by protocol The "unix" kernel module is supposed to be loaded automatically, and clearly that works most of the time, but maybe there is a race somewhere. In any case, no sane person would run a kernel without Unix domain sockets, so we may as well make it builtin. http://hydra.nixos.org/build/30001448
2016-01-07 12:48:12 +01:00
# Unix domain sockets.
UNIX y
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
# Power management.
${optionalString (versionOlder version "3.19") ''
PM_RUNTIME y
''}
PM_ADVANCED_DEBUG y
linux: add config options needed for a Bay Trail Chromebook Close #10416. Got /dev/mmcblk0 on a live CD with these options: X86_INTEL_LPSS y PINCTRL_BAYTRAIL y
2015-10-16 12:36:18 +02:00
${optionalString (versionAtLeast version "3.11") ''
X86_INTEL_LPSS y
''}
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
${optionalString (versionAtLeast version "3.10") ''
X86_INTEL_PSTATE y
''}
linux: Enable Intel idle driver Also build the performance governor into the kernel so there is a sane default. Note that cpufreq.service will still load "ondemand" on non-pstate systems.
2015-03-04 17:04:02 +01:00
INTEL_IDLE y
CPU_FREQ_DEFAULT_GOV_PERFORMANCE y
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
${optionalString (versionOlder version "3.10") ''
USB_SUSPEND y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Support drivers that need external firmware.
STANDALONE n
Revert "linux: really provide /proc/config.gz" This reverts commit 68ce9e91e12914f34e55ef16d8f4b6fbcdd9e92a. /proc/config.gz is available after "modprobe configs" and in /run/booted-system/kernel-modules/config
2013-09-04 06:45:36 +02:00
# Make /proc/config.gz available.
kernel-config: Enable IKCONFIG so ARM gets /proc/config.gz IKCONFIG must be enabled so IKCONFIG_PROC can be set. On x86 IKCONFIG gets implicitly enabled by kernelAutoModules in platforms.nix. But ARM doesn't use kernelAutoModules, so IKCONFIG_PROC won't get enabled without this patch.
2015-06-04 10:15:31 +02:00
IKCONFIG y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
IKCONFIG_PROC y
# Optimize with -O2, not -Os.
CC_OPTIMIZE_FOR_SIZE n
# Enable the kernel's built-in memory tester.
MEMTEST y
# Include the CFQ I/O scheduler in the kernel, rather than as a
# module, so that the initrd gets a good I/O scheduler.
IOSCHED_CFQ y
BLK_CGROUP y # required by CFQ
# Enable NUMA.
NUMA? y
# Disable some expensive (?) features.
PM_TRACE_RTC n
# Enable various subsystems.
ACCESSIBILITY y # Accessibility support
AUXDISPLAY y # Auxiliary Display support
DONGLE y # Serial dongle support
HIPPI y
MTD_COMPLEX_MAPPINGS y # needed for many devices
${optionalString (versionOlder version "3.2") ''
NET_POCKET y # enable pocket and portable adapters
''}
SCSI_LOWLEVEL y # enable lots of SCSI devices
SCSI_LOWLEVEL_PCMCIA y
Added line SCSI_SAS_ATA y on line 62 This kernel change will make the nixOS live cd detect the hard drive upon boot.
2014-10-17 22:31:08 +02:00
SCSI_SAS_ATA y # added to enable detection of hard drive
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
SPI y # needed for many devices
SPI_MASTER y
WAN y
# Networking options.
IP_PNP n
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
${optionalString (versionOlder version "3.13") ''
linux: Enable BPF_JIT only on 64-bit It's not supported on i686. http://hydra.nixos.org/build/16834647
2014-11-10 20:21:28 +01:00
IPV6_PRIVACY y
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
NETFILTER_ADVANCED y
IP_VS_PROTO_TCP y
IP_VS_PROTO_UDP y
IP_VS_PROTO_ESP y
IP_VS_PROTO_AH y
IP_DCCP_CCID3 n # experimental
CLS_U32_PERF y
CLS_U32_MARK y
linux: Enable BPF_JIT only on 64-bit It's not supported on i686. http://hydra.nixos.org/build/16834647
2014-11-10 20:21:28 +01:00
${optionalString (stdenv.system == "x86_64-linux") ''
BPF_JIT y
''}
linux: kernel config for extended BPF support - Enable BPF_SYSCALL and BPF_EVENTS - Build modules for NET_CLS_BPF and NET_ACT_BPF With these config options we can leverage the full potential of BPF for tracing and instrumenting Linux systems, for example using libraries/tools like those provided by the bcc project.
2016-04-06 15:25:14 +02:00
${optionalString (versionAtLeast version "4.4") ''
NET_CLS_BPF m
NET_ACT_BPF m
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Wireless networking.
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
CFG80211_WEXT? y # Without it, ipw2200 drivers don't build
IPW2100_MONITOR? y # support promiscuous mode
IPW2200_MONITOR? y # support promiscuous mode
HOSTAP_FIRMWARE? y # Support downloading firmware images with Host AP driver
HOSTAP_FIRMWARE_NVRAM? y
ATH9K_PCI? y # Detect Atheros AR9xxx cards on PCI(e) bus
ATH9K_AHB? y # Ditto, AHB bus
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${optionalString (versionAtLeast version "3.2") ''
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
B43_PHY_HT? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
''}
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
BCMA_HOST_PCI? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Enable various FB devices.
FB y
FB_EFI y
FB_NVIDIA_I2C y # Enable DDC Support
FB_RIVA_I2C y
FB_ATY_CT y # Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
FB_ATY_GX y # Mach64 GX support
FB_SAVAGE_I2C y
FB_SAVAGE_ACCEL y
FB_SIS_300 y
FB_SIS_315 y
FB_3DFX_ACCEL y
kernel-config: Enable FB_VESA and FRAMEBUFFER_CONSOLE Commit 159fed47bc (nixos/grub: Fix video display on efi) changed BIOS systems to start in non-text mode as well. Enable FB_VESA to get a framebuffer console on BIOS systems. Change FRAMEBUFFER_CONSOLE to 'y' instead of the default 'm' to so the user doesn't need to manually load the fbcon module anymore. Other distros have similar defaults, at least on Arch: CONFIG_FB_VESA=y CONFIG_FRAMEBUFFER_CONSOLE=y and on Ubuntu (12.04): CONFIG_FB_VESA=m CONFIG_FRAMEBUFFER_CONSOLE=y Fixes #8139
2015-06-03 22:43:17 +02:00
FB_VESA y
FRAMEBUFFER_CONSOLE y
Adding framebuffer console rotation to kernels. This helps in some weird screens that otherwise show the console 90° turned.
2016-01-07 16:47:50 +01:00
FRAMEBUFFER_CONSOLE_ROTATION y
linux 3.11 works fine for me, but nvidia binary driver fails once again
2013-09-04 06:49:22 +02:00
${optionalString (versionOlder version "3.9" || stdenv.system == "i686-linux") ''
FB_GEODE y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Video configuration.
# Enable KMS for devices whose X.org driver supports it.
linux_chromiumos_3_18: init at 3.18.0 Co-authored-by: Nikolay Amiantov <ab@fmap.me>
2016-01-10 20:07:45 +01:00
${optionalString (versionOlder version "4.3" && !(features.chromiumos or false)) ''
linux-testing: Update to 4.3.0-rc2
2015-09-21 21:42:00 +02:00
DRM_I915_KMS y
''}
kernel: Enable DRM_LOAD_EDID_FIRMWARE This allows specifying drm_kms_helper.edid_firmware to work around displays that provide bad EDID data. Documentation: https://www.osadl.org/Single-View.111+M5ec938a7b3b.0.html
2015-08-04 22:38:38 +02:00
# Allow specifying custom EDID on the kernel command line
DRM_LOAD_EDID_FIRMWARE y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${optionalString (versionOlder version "3.9") ''
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
DRM_RADEON_KMS? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
''}
# Hybrid graphics support
VGA_SWITCHEROO y
# Sound.
linux: Enable SND_DYNAMIC_MINORS This is necessary if you get: kernel: Too many HDMI devices kernel: Consider building the kernel with CONFIG_SND_DYNAMIC_MINORS=y
2014-04-18 21:06:34 +02:00
SND_DYNAMIC_MINORS y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
SND_AC97_POWER_SAVE y # AC97 Power-Saving Mode
SND_HDA_INPUT_BEEP y # Support digital beep via input layer
SND_USB_CAIAQ_INPUT y
PSS_MIXER y # Enable PSS mixer (Beethoven ADSP-16 and other compatible)
# USB serial devices.
USB_SERIAL_GENERIC y # USB Generic Serial Driver
USB_SERIAL_KEYSPAN_MPR y # include firmware for various USB serial devices
USB_SERIAL_KEYSPAN_USA28 y
USB_SERIAL_KEYSPAN_USA28X y
USB_SERIAL_KEYSPAN_USA28XA y
USB_SERIAL_KEYSPAN_USA28XB y
USB_SERIAL_KEYSPAN_USA19 y
USB_SERIAL_KEYSPAN_USA18X y
USB_SERIAL_KEYSPAN_USA19W y
USB_SERIAL_KEYSPAN_USA19QW y
USB_SERIAL_KEYSPAN_USA19QI y
USB_SERIAL_KEYSPAN_USA49W y
USB_SERIAL_KEYSPAN_USA49WLC y
# Filesystem options - in particular, enable extended attributes and
# ACLs for all filesystems that support them.
kernel: common-config.nix: enable FANOTIFY
2015-02-12 19:39:44 +01:00
FANOTIFY y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
EXT2_FS_XATTR y
EXT2_FS_POSIX_ACL y
linux: Enable ACLs in ext3 http://hydra.nixos.org/build/13462892
2014-08-18 14:33:09 +02:00
EXT2_FS_SECURITY y
linux/kernel: Remove EXT2_FS_XIP for version 4.0. The option has been removed in torvalds/linux@6cd176a and thus we shouldn't try to set it for kernel version 4. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-03-04 15:38:17 +01:00
${optionalString (versionOlder version "4.0") ''
EXT2_FS_XIP y # Ext2 execute in place support
''}
linux: Enable ACLs in ext3 http://hydra.nixos.org/build/13462892
2014-08-18 14:33:09 +02:00
EXT3_FS_POSIX_ACL y
EXT3_FS_SECURITY y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
EXT4_FS_POSIX_ACL y
EXT4_FS_SECURITY y
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
REISERFS_FS_XATTR? y
REISERFS_FS_POSIX_ACL? y
REISERFS_FS_SECURITY? y
JFS_POSIX_ACL? y
JFS_SECURITY? y
XFS_QUOTA? y
XFS_POSIX_ACL? y
XFS_RT? y # XFS Realtime subvolume support
OCFS2_DEBUG_MASKLOG? n
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
BTRFS_FS_POSIX_ACL y
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
UBIFS_FS_ADVANCED_COMPR? y
kernel-config: do not use NFSD_PNFS on >=4.6
2016-03-27 04:06:58 +02:00
${optionalString (versionAtLeast version "4.0" && versionOlder version "4.6") ''
kernel-config: nfs changes
2015-05-16 01:33:45 +02:00
NFSD_PNFS y
''}
NFSD_V2_ACL y
NFSD_V3 y
NFSD_V3_ACL y
NFSD_V4 y
${optionalString (versionAtLeast version "3.11") ''
NFSD_V4_SECURITY_LABEL y
''}
NFS_FSCACHE y
linux: only enable CONFIG_NFS_SWAP for v3.6+ kernels Linux v3.6 is the earliest version with CONFIG_NFS_SWAP support. This change unbreaks NixOS tests for older kernels.
2014-07-16 12:08:48 +02:00
${optionalString (versionAtLeast version "3.6") ''
NFS_SWAP y
''}
kernel-config: nfs changes
2015-05-16 01:33:45 +02:00
NFS_V3_ACL y
linux: Enable NFSv4.1, v4.2 clients and swap on NFS I'm only enabling for kernels >= 3.11 to be conservative, because clients and servers automatically negotiate and use the highest mutually supported version by default, but only in kernel 3.11 server NFSv4.1 support actually became RFC compliant. I'm also adding support for swap on NFS, which is enabled by default on Ubuntu kernels.
2014-04-23 16:47:50 +02:00
${optionalString (versionAtLeast version "3.11") ''
NFS_V4_1 y # NFSv4.1 client support
NFS_V4_2 y
kernel-config: nfs changes
2015-05-16 01:33:45 +02:00
NFS_V4_SECURITY_LABEL y
linux: Enable NFSv4.1, v4.2 clients and swap on NFS I'm only enabling for kernels >= 3.11 to be conservative, because clients and servers automatically negotiate and use the highest mutually supported version by default, but only in kernel 3.11 server NFSv4.1 support actually became RFC compliant. I'm also adding support for swap on NFS, which is enabled by default on Ubuntu kernels.
2014-04-23 16:47:50 +02:00
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
CIFS_XATTR y
CIFS_POSIX y
CIFS_FSCACHE y
kernel: Add more supported features
2014-11-08 11:44:19 +01:00
${optionalString (versionAtLeast version "3.12") ''
CEPH_FSCACHE y
''}
${optionalString (versionAtLeast version "3.14") ''
CEPH_FS_POSIX_ACL y
''}
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.13") ''
SQUASHFS_FILE_DIRECT y
SQUASHFS_DECOMP_MULTI_PERCPU y
''}
Change kernel config: improve squashfs support of kernel
2015-02-16 19:42:10 +01:00
SQUASHFS_XATTR y
SQUASHFS_ZLIB y
SQUASHFS_LZO y
SQUASHFS_XZ y
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.19") ''
SQUASHFS_LZ4 y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
kernel: set nx bit on module ro segments Fixes #4757.
2014-11-01 01:07:06 +01:00
# Runtime security tests
DEBUG_SET_MODULE_RONX? y # Detect writes to read-only module pages
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Security related features.
STRICT_DEVMEM y # Filter access to /dev/mem
linux: Disable /dev/kmem See e.g. https://wiki.ubuntu.com/Security/Features#A.2BAC8-dev.2BAC8-kmem_disabled
2013-08-01 00:08:44 +02:00
SECURITY_SELINUX_BOOTPARAM_VALUE 0 # Disable SELinux by default
kernel: unconditionally disable /dev/kmem This was presumably set for grsecurity compatibility, but now appears redundant. Grsecurity does not expect nor require /dev/kmem to be present and so it makes little sense to continue making its inclusion in the standard kernel dependent on grsecurity. More generally, given the large number of possible grsecurity configurations, it is unclear what `features.grsecurity` even *means* and its use should be discouraged.
2016-05-17 05:20:04 +02:00
DEVKMEM n # Disable /dev/kmem
Enable CC_STACKPROTECTOR_REGULAR on linux 3.14+
2014-04-02 23:58:54 +02:00
${if versionOlder version "3.14" then ''
kernel/common-config: Another optional option Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 02:44:03 +02:00
CC_STACKPROTECTOR? y # Detect buffer overflows on the stack
Enable CC_STACKPROTECTOR_REGULAR on linux 3.14+
2014-04-02 23:58:54 +02:00
'' else ''
kernel/common-config: Another optional option Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 02:44:03 +02:00
CC_STACKPROTECTOR_REGULAR? y
Add linux 3.14
2014-04-01 02:54:47 +02:00
''}
kernel: add linux 3.12-rc2
2013-09-25 12:49:49 +02:00
${optionalString (versionAtLeast version "3.12") ''
USER_NS y # Support for user namespaces
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
kernel: enable AppArmor by default AppArmor only requires a few patches to the 3.2 and 3.4 kernels in order to work properly (with the minor catch grsecurity -stable includes the 3.2 patches.) This adds them to the kernel builds by default, removes features.apparmor (since it's always true) and makes it the default MAC system. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-08 00:59:29 +02:00
# AppArmor support
SECURITY_APPARMOR y
DEFAULT_SECURITY_APPARMOR y
kernel-config: Add microcode support + early loading on new kernels
2015-03-25 19:29:57 +01:00
# Microcode loading support
MICROCODE y
MICROCODE_INTEL y
MICROCODE_AMD y
linux-testing: Bump to 4.4-rc1
2015-11-18 02:21:25 +01:00
${optionalString (versionAtLeast version "3.11" && versionOlder version "4.4") ''
kernel-config: Add microcode support + early loading on new kernels
2015-03-25 19:29:57 +01:00
MICROCODE_EARLY y
MICROCODE_INTEL_EARLY y
MICROCODE_AMD_EARLY y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Misc. options.
8139TOO_8129 y
8139TOO_PIO n # PIO is slower
AIC79XX_DEBUG_ENABLE n
AIC7XXX_DEBUG_ENABLE n
AIC94XX_DEBUG n
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
${optionalString (versionAtLeast version "3.3" && versionOlder version "3.13") ''
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
AUDIT_LOGINUID_IMMUTABLE y
''}
linux-testing: Bump to 4.4-rc1
2015-11-18 02:21:25 +01:00
${optionalString (versionOlder version "4.4") ''
B43_PCMCIA? y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
BLK_DEV_CMD640_ENHANCED y # CMD640 enhanced support
BLK_DEV_IDEACPI y # IDE ACPI support
BLK_DEV_INTEGRITY y
BSD_PROCESS_ACCT_V3 y
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
BT_HCIUART_BCSP? y
BT_HCIUART_H4? y # UART (H4) protocol support
BT_HCIUART_LL? y
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.4") ''
BT_RFCOMM_TTY? y # RFCOMM TTY support
''}
Turning off PAE support which makes kernel unbootable on older hardware causes CRASH_DUMP option to disappear, so make it optional.
2013-08-12 04:30:10 +02:00
CRASH_DUMP? n
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${optionalString (versionOlder version "3.1") ''
DMAR? n # experimental
''}
DVB_DYNAMIC_MINORS? y # we use udev
${optionalString (versionAtLeast version "3.3") ''
EFI_STUB y # EFI bootloader in the bzImage itself
''}
FHANDLE y # used by systemd
FUSION y # Fusion MPT device support
IDE_GD_ATAPI y # ATAPI floppy support
IRDA_ULTRA y # Ultra (connectionless) protocol
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
JOYSTICK_IFORCE_232? y # I-Force Serial joysticks and wheels
JOYSTICK_IFORCE_USB? y # I-Force USB joysticks and wheels
JOYSTICK_XPAD_FF? y # X-Box gamepad rumble support
JOYSTICK_XPAD_LEDS? y # LED Support for Xbox360 controller 'BigX' LED
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
LDM_PARTITION y # Windows Logical Disk Manager (Dynamic Disk) support
LEDS_TRIGGER_IDE_DISK y # LED IDE Disk Trigger
LOGIRUMBLEPAD2_FF y # Logitech Rumblepad 2 force feedback
LOGO n # not needed
MEDIA_ATTACH y
MEGARAID_NEWGEN y
kernel-config: mlx4-en enable vxlan offloading
2015-05-16 01:36:54 +02:00
${optionalString (versionAtLeast version "3.15") ''
MLX4_EN_VXLAN y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
MODVERSIONS y
MOUSE_PS2_ELANTECH y # Elantech PS/2 protocol extension
MTRR_SANITIZER y
NET_FC y # Fibre Channel driver support
linux: add config options needed for a Bay Trail Chromebook Close #10416. Got /dev/mmcblk0 on a live CD with these options: X86_INTEL_LPSS y PINCTRL_BAYTRAIL y
2015-10-16 12:36:18 +02:00
${optionalString (versionAtLeast version "3.11") ''
PINCTRL_BAYTRAIL y # GPIO on Intel Bay Trail, for some Chromebook internal eMMC disks
''}
Increasing mmc possible partitions from 8 to 32. In kernel common config. I have a modern tablet with 18 gpt partitions on eMMC (Android+Win10 dualboot).
2016-01-11 09:27:58 +01:00
MMC_BLOCK_MINORS 32 # 8 is default. Modern gpt tables on eMMC may go far beyond 8.
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
PPP_MULTILINK y # PPP multilink support
kernel: Enable PPP_FILTER by default. pppd will try to use it to improve efficiency and complain if it's not available (but is is not mandatory).
2014-11-02 13:39:14 +01:00
PPP_FILTER y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
REGULATOR y # Voltage and Current Regulator Support
${optionalString (versionAtLeast version "3.6") ''
RC_DEVICES? y # Enable IR devices
''}
fix linux 3.2/3.4 builds
2015-03-29 21:40:57 +02:00
${optionalString (versionAtLeast version "3.10") ''
RT2800USB_RT55XX y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
SCSI_LOGGING y # SCSI logging facility
SERIAL_8250 y # 8250/16550 and compatible serial support
SLIP_COMPRESSED y # CSLIP compressed headers
SLIP_SMART y
linux-testing: Update to 4.3.0-rc2
2015-09-21 21:42:00 +02:00
HWMON y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
THERMAL_HWMON y # Hardware monitoring support
linux: disable UEVENT_HELPER by default on versions >= 3.15
2015-04-06 14:00:03 +02:00
${optionalString (versionAtLeast version "3.15") ''
UEVENT_HELPER n
''}
kernel/common-config: More fixes
2015-03-20 23:05:43 +01:00
${optionalString (versionOlder version "3.15") ''
USB_DEBUG? n
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
USB_EHCI_ROOT_HUB_TT y # Root Hub Transaction Translators
USB_EHCI_TT_NEWSCHED y # Improved transaction translator scheduling
X86_CHECK_BIOS_CORRUPTION y
X86_MCE y
linux: adding PCI Expresscard Hotplug support
2016-02-01 11:07:08 +01:00
# PCI-Expresscard hotplug support
linux-3.10: fixup config by a slightly hacky way For explanation see: https://github.com/NixOS/nixpkgs/pull/13405#issuecomment-188357637
2016-02-25 23:07:47 +01:00
${optionalString (versionAtLeast version "3.12") "HOTPLUG_PCI_PCIE y"}
linux: adding PCI Expresscard Hotplug support
2016-02-01 11:07:08 +01:00
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Linux containers.
kernel-config: Explicitly enable NAMESPACES Namespace support is required by the `unshare` tool used in `nixos-install`. It's enabled by the x86 defconfig, but not by e.g. multi_v7_defconfig. So enable it here so that `nixos-install` can work on ARM.
2015-07-01 11:36:55 +02:00
NAMESPACES? y # Required by 'unshare' used by 'nixos-install'
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
RT_GROUP_SCHED? y
CGROUP_DEVICE? y
${if versionAtLeast version "3.6" then ''
MEMCG y
MEMCG_SWAP y
'' else ''
CGROUP_MEM_RES_CTLR y
CGROUP_MEM_RES_CTLR_SWAP y
''}
linux-testing: 4.6-rc6 -> 4.7-rc6 The config option DEVPTS_MULTIPLE_INSTANCES now no longer exists since torvalds/linux@eedf265aa003b4781de24cfed40a655a664457e6. Built successfully on my Hydra instance: https://headcounter.org/hydra/log/r4n6sv0zld0aj65r7l494757s2r8w8sr-linux-4.7-rc6.drv Verified unpacked tarball with GnuPG: ABAF 11C6 5A29 70B1 30AB E3C4 79BE 3E43 0041 1886 gpg: Signature made Mon 04 Jul 2016 08:13:05 AM CEST gpg: using RSA key 79BE3E4300411886 gpg: Good signature from "Linus Torvalds <torvalds@linux-foundation.org>" Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2016-07-04 10:40:28 +02:00
${optionalString (versionOlder version "4.7") "DEVPTS_MULTIPLE_INSTANCES y"}
linux: Enable proper blkio controller support Having BLK_CGROUP is not enough, you need BLK_DEV_THROTTLING or CFQ_GROUP_IOSCHED to do anything useful.
2013-09-17 16:00:36 +02:00
BLK_DEV_THROTTLING y
CFQ_GROUP_IOSCHED y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Enable staging drivers. These are somewhat experimental, but
# they generally don't hurt.
STAGING y
# PROC_EVENTS requires that the netlink connector is not built
# as a module. This is required by libcgroup's cgrulesengd.
CONNECTOR y
PROC_EVENTS y
# Tracing.
FTRACE y
kernel: Enable kprobes and other tracing features All of these should have minimal performance impact unless enabled at runtime.
2015-03-11 17:11:41 +01:00
KPROBES y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
FUNCTION_TRACER y
FTRACE_SYSCALLS y
SCHED_TRACER y
kernel: Enable kprobes and other tracing features All of these should have minimal performance impact unless enabled at runtime.
2015-03-11 17:11:41 +01:00
STACK_TRACER y
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.10") ''
UPROBE_EVENT y
''}
linux: kernel config for extended BPF support - Enable BPF_SYSCALL and BPF_EVENTS - Build modules for NET_CLS_BPF and NET_ACT_BPF With these config options we can leverage the full potential of BPF for tracing and instrumenting Linux systems, for example using libraries/tools like those provided by the bcc project.
2016-04-06 15:25:14 +02:00
${optionalString (versionAtLeast version "4.4") ''
BPF_SYSCALL y
BPF_EVENTS y
''}
kernel: Enable kprobes and other tracing features All of these should have minimal performance impact unless enabled at runtime.
2015-03-11 17:11:41 +01:00
FUNCTION_PROFILER y
RING_BUFFER_BENCHMARK n
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Devtmpfs support.
DEVTMPFS y
# Easier debugging of NFS issues.
${optionalString (versionAtLeast version "3.4") ''
SUNRPC_DEBUG y
''}
# Virtualisation.
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
PARAVIRT? y
kernel: set virtualization options regardless of grsec Per my own testing, the NixOS grsecurity kernel works both as a KVM-based virtualisation host and guest; there appears to be no good reason to making these conditional on `features.grsecurity`. More generally, it's unclear what `features.grsecurity` *means*. If someone configures a grsecurity kernel in such a fashion that it breaks KVM support, they should know to disable KVM themselves.
2016-05-17 05:20:48 +02:00
${if versionAtLeast version "3.10" then ''
HYPERVISOR_GUEST y
'' else ''
PARAVIRT_GUEST? y
''}
kernel-config: kvm changes
2015-05-16 01:50:20 +02:00
KVM_APIC_ARCHITECTURE y
KVM_ASYNC_PF y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
${optionalString (versionOlder version "3.7") ''
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
KVM_CLOCK? y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
''}
kernel-config: kvm changes
2015-05-16 01:50:20 +02:00
${optionalString (versionAtLeast version "4.0") ''
kernel-config: Fix 4.0 build on 32-bit KVM_COMPAT apparently enables 32-bit compability syscalls for KVM, and as such can be enabled only on a 64-bit system. Resolves error http://hydra.nixos.org/build/23014132/nixlog/1/raw: GOT: # GOT: # configuration written to .config GOT: # GOT: make[1]: Leaving directory '/tmp/nix-build-linux-config-4.0.5.drv-0/build' GOT: make: Leaving directory '/tmp/nix-build-linux-config-4.0.5.drv-0/linux-4.0.5' unused option: KVM_COMPAT builder for ‘/nix/store/7kskdvmzs116f1fm55ghm0crjniw9q0a-linux-config-4.0.5.drv’ failed with exit code 255
2015-06-09 23:27:33 +02:00
KVM_COMPAT? y
kernel-config: kvm changes
2015-05-16 01:50:20 +02:00
''}
${optionalString (versionAtLeast version "3.10") ''
kernel-config: Fix for i686
2015-05-17 12:02:44 +02:00
KVM_DEVICE_ASSIGNMENT? y
kernel-config: kvm changes
2015-05-16 01:50:20 +02:00
''}
${optionalString (versionAtLeast version "4.0") ''
KVM_GENERIC_DIRTYLOG_READ_PROTECT y
''}
kernel: set virtualization options regardless of grsec Per my own testing, the NixOS grsecurity kernel works both as a KVM-based virtualisation host and guest; there appears to be no good reason to making these conditional on `features.grsecurity`. More generally, it's unclear what `features.grsecurity` *means*. If someone configures a grsecurity kernel in such a fashion that it breaks KVM support, they should know to disable KVM themselves.
2016-05-17 05:20:48 +02:00
KVM_GUEST y
kernel-config: kvm changes
2015-05-16 01:50:20 +02:00
KVM_MMIO y
${optionalString (versionAtLeast version "3.13") ''
KVM_VFIO y
''}
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
XEN? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
XEN_DOM0? y
Add kernel config for dom0 of Xen
2015-02-10 16:53:03 +01:00
${optionalString ((versionAtLeast version "3.18") && (features.xen_dom0 or false)) ''
PCI_XEN? y
HVC_XEN? y
HVC_XEN_FRONTEND? y
XEN_SYS_HYPERVISOR? y
SWIOTLB_XEN? y
XEN_BACKEND? y
XEN_BALLOON? y
XEN_BALLOON_MEMORY_HOTPLUG? y
XEN_EFI? y
XEN_HAVE_PVMMU? y
XEN_MCE_LOG? y
XEN_PVH? y
XEN_PVHVM? y
XEN_SAVE_RESTORE? y
XEN_SCRUB_PAGES? y
XEN_SELFBALLOONING? y
XEN_STUB? y
XEN_TMEM? y
''}
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
KSM y
${optionalString (!stdenv.is64bit) ''
HIGHMEM64G? y # We need 64 GB (PAE) support for Xen guest support.
''}
more kernel fixes
2014-11-11 09:21:53 +01:00
${optionalString (versionAtLeast version "3.9" && stdenv.is64bit) ''
kernel: Add more supported features
2014-11-08 11:44:19 +01:00
VFIO_PCI_VGA y
''}
VIRT_DRIVERS y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Media support.
${optionalString (versionAtLeast version "3.6") ''
MEDIA_DIGITAL_TV_SUPPORT y
MEDIA_CAMERA_SUPPORT y
MEDIA_RC_SUPPORT y
''}
${optionalString (versionAtLeast version "3.7") ''
MEDIA_USB_SUPPORT y
ChromiumOS kernel option fixup
2016-03-07 16:00:21 +01:00
${optionalString (!(features.chromiumos or false)) ''
MEDIA_PCI_SUPPORT y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
''}
# Our initrd init uses shebang scripts, so can't be modular.
${optionalString (versionAtLeast version "3.10") ''
BINFMT_SCRIPT y
''}
kernel config: Enable BINFMT_MISC This is enabled in x86 builds but lacking on ARM.
2016-04-28 19:46:34 +02:00
# For systemd-binfmt
BINFMT_MISC? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Enable the 9P cache to speed up NixOS VM tests.
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
9P_FSCACHE? y
9P_FS_POSIX_ACL? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
linux: Enable transparent hugepages
2014-04-16 22:30:58 +02:00
# Enable transparent support for huge pages.
TRANSPARENT_HUGEPAGE? y
TRANSPARENT_HUGEPAGE_ALWAYS? n
TRANSPARENT_HUGEPAGE_MADVISE? y
linux: Enable FW_LOADER_USER_HELPER_FALLBACK We don't really need this anymore, except that our docs say that you can put firmware in /root/test-firmware, which doesn't work via /sys/module/firmware_class/parameters/path.
2014-10-20 13:18:33 +02:00
# zram support (e.g for in-memory compressed swap).
linux: Add support for zram
2014-04-24 14:03:18 +02:00
${optionalString (versionAtLeast version "3.4") ''
ZSMALLOC y
''}
ZRAM m
linux: Enable FW_LOADER_USER_HELPER_FALLBACK We don't really need this anymore, except that our docs say that you can put firmware in /root/test-firmware, which doesn't work via /sys/module/firmware_class/parameters/path.
2014-10-20 13:18:33 +02:00
Linux: Enable PCIe and USB support for brcmfmac
2015-10-03 21:22:52 +02:00
# Enable PCIe and USB for the brcmfmac driver
Fix kernel config names for BRCMFMAC_*
2015-10-03 21:35:06 +02:00
BRCMFMAC_USB? y
BRCMFMAC_PCIE? y
Linux: Enable PCIe and USB support for brcmfmac
2015-10-03 21:22:52 +02:00
linux: Support x2APIC Without this, certain servers with lots of CPU cores would show only one core.
2015-10-26 16:17:22 +01:00
# Support x2APIC (which requires IRQ remapping).
linux: Fix i686 build
2015-10-28 11:09:59 +01:00
${optionalString (stdenv.system == "x86_64-linux") ''
X86_X2APIC y
IRQ_REMAP y
''}
linux: Support x2APIC Without this, certain servers with lots of CPU cores would show only one core.
2015-10-26 16:17:22 +01:00
Really disable the firmware loader user helper fallback
2015-10-30 18:31:51 +01:00
# Disable the firmware helper fallback, udev doesn't implement it any more
FW_LOADER_USER_HELPER_FALLBACK? n
linux_chromiumos_3_18: init at 3.18.0 Co-authored-by: Nikolay Amiantov <ab@fmap.me>
2016-01-10 20:07:45 +01:00
# ChromiumOS support
${optionalString (features.chromiumos or false) ''
CHROME_PLATFORMS y
VGA_SWITCHEROO n
MMC_SDHCI_PXAV2 n
NET_IPVTI n
IPV6_VTI n
REGULATOR_FIXED_VOLTAGE n
TPS6105X n
CPU_FREQ_STAT y
IPV6 y
MFD_CROS_EC y
MFD_CROS_EC_LPC y
MFD_CROS_EC_DEV y
CHARGER_CROS_USB_PD y
I2C y
MEDIA_SUBDRV_AUTOSELECT n
VIDEO_IR_I2C n
BLK_DEV_DM y
ANDROID_PARANOID_NETWORK n
DM_VERITY n
DRM_VGEM n
CPU_FREQ_GOV_INTERACTIVE n
INPUT_KEYRESET n
DM_BOOTCACHE n
UID_CPUTIME n
${optionalString (versionAtLeast version "3.18") ''
CPUFREQ_DT n
EXTCON_CROS_EC n
DRM_POWERVR_ROGUE n
CHROMEOS_OF_FIRMWARE y
TEST_RHASHTABLE n
BCMDHD n
TRUSTY n
''}
${optionalString (versionOlder version "3.18") ''
MALI_MIDGARD n
DVB_USB_DIB0700 n
DVB_USB_DW2102 n
DVB_USB_PCTV452E n
DVB_USB_TTUSB2 n
DVB_USB_AF9015 n
DVB_USB_AF9035 n
DVB_USB_ANYSEE n
DVB_USB_AZ6007 n
DVB_USB_IT913X n
DVB_USB_LME2510 n
DVB_USB_RTL28XXU n
USB_S2255 n
VIDEO_EM28XX n
VIDEO_TM6000 n
USB_DWC2 n
USB_GSPCA n
SPEAKUP n
XO15_EBOOK n
USB_GADGET n
''}
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${kernelPlatform.kernelExtraConfig or ""}
${extraConfig}
''
Reference in a new issue Copy permalink