This enables the 32-bit EFI entry point on 64-bit kernels, so hardware
like Baytrail devices with 32-bit firmware on a 64-bit cpu can boot the
64-bit kernel.
Signed-off-by: Peter Jones <pjones@redhat.com>
- I also like to live dangerously. (Re-enable RCU_FAST_NO_HZ which has been off
since April 2012. Also enable NO_HZ_FULL on x86_64.)
- I added zipped modules ages ago, remove it from TODO.
New kexec syscall (kexec_file_load()) can perform bzimage signature
verification.
This will re-enable kexec/kdump on secureboot systems using new syscall.
Currently kexec/kdump is disabled on secureboot systems.
User space (kexec-tools) will be modifed to automatically detect that
running system has secureboot enabled and use new syscall instead of
old one.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
The benefit of THP has been somewhat questionable overall for a while,
and it's been known to cause performance issues with some workloads.
Upstream also considers it to be overly complicated and really not worth
it on machines with memory in the amounts found on typical desktops/SMB
servers.
Switch to using it via madvise, which most applications that care about
it should likely already be doing.
Set CONFIG_BOOTPARAM_HOTPLUG_CPU0 to 'y'. Currently, to disable CPU0,
the "boot" cpu, one must specify cpu0_hotplug as a kernel parameter.
Setting this config variable to 1 enables it by default.
I've tested this on systems where it was expected to work and it seems to
function properly.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Replace x86-allow-1024-cpus.patch with the patch that contains the one hunk
not already applied upstream.
Don't install the 'trace' alias symlink for 'perf trace'. Seems much too
generic to just throw that into /usr/bin
So apparently we've been enabling CONFIG_NAMESPACES in Fedora kernels for
a very long time even though it was never explicitly set. The kconfig entry
for it looks like it should depend on CONFIG_EXPERT (which isn't set), but
either the fact that we've had CONFIG_NET_NS, etc enabled explicitly or the
fact that it defaults to !EXPERT seems to do something weird with menuconfig
and enables it in the final config. Whatever, just turn it back on. It
seems to break rtkit-daemon for some reason.
