Skip to content

Repository files navigation

 ██╗ ██╗██╗ ██╗██████╗ ███████╗██████╗ ██╗ ██████╗ ███╗ ██╗
██║ ██║╚██╗ ██╔╝██╔══██╗██╔════╝██╔══██╗██║██╔═══██╗████╗ ██║
███████║ ╚████╔╝ ██████╔╝█████╗ ██████╔╝██║██║ ██║██╔██╗ ██║
██╔══██║ ╚██╔╝ ██╔═══╝ ██╔══╝ ██╔══██╗██║██║ ██║██║╚██╗██║
██║ ██║ ██║ ██║ ███████╗██║ ██║██║╚██████╔╝██║ ╚████║
╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚══════╝╚═╝ ╚═╝╚═╝ ╚═════╝ ╚═╝ ╚═══╝
H Y P E R I O N · v2.2.4
Linux 6.19.6 · Universal · Stable · God-Tier Daily Driver
Hyperion Kernel Icon

Author: Soumalya Das | License: MIT | Base: Linux 6.19.6 | Year: 2026

Build StatusKernel VersionArchitectureLicense: MITDKMS CompatibleUniversal Distro SupportRust Enabled


Table of Contents


Overview

Hyperion Kernel is a custom Linux 6.19.6 kernel build engineered to be the definitive daily-driver kernel for every kind of Linux user — gamers, developers, security engineers, audio producers, and tinkerers. It combines the best configuration practices from CachyOS, XanMod, Nobara, Liquorix, and upstream Linux into a single, fully integrated, zero-compromise bzImage.

v2.2.4 is the "Ultimate Performance" release — the most comprehensive Hyperion build to date. It adds Rust language infrastructure, the BORE interactive scheduler, the ADIOS I/O scheduler, a full developer tracing and debugging suite, GPU virtual memory management, precision network schedulers, and dual-stream ZRAM compression. Every improvement is expressed as a kernel configuration choice backed by upstream in-tree code or documented companion patches. No staging code. No unmaintained drivers. Just the right config, fully documented, for every workload.

uname -r → 6.19.6-Hyperion-2.2.4
uname -v → #1 SMP PREEMPT Linux 6.19.6-Hyperion-2.2.4 (Soumalya Das) 2026

What's New in v2.2.4

"Everything you need. Nothing you don't. Documented to the last bit."

Rust Language Support

CONFIG_RUST=y — Rust is now a first-class citizen in the Hyperion build.

The Linux kernel's Rust infrastructure (merged Linux 6.1, actively expanding in 6.19) provides memory-safety guarantees at compile time for new kernel subsystems. Enabling Rust in the kernel does not change any existing C code or drivers — it simply makes the Rust toolchain available for drivers that choose to use it.

Why it matters for 2026:

  • New NVMe, network, and GPU driver implementations are being written in Rust upstream
  • Apple Silicon GPU driver (Asahi Linux) requires Rust infrastructure
  • Several new security modules and filesystem drivers are Rust-first
  • Zero overhead when no Rust drivers are loaded — Rust support is purely additive

Build requirement:rustc >= 1.78 + bindgen >= 0.65. Install with:

# Arch
sudo pacman -S rust rust-bindgen
# Fedora
sudo dnf install rust rust-bindgen-cli
# Check version
rustc --version && bindgen --version
ConfigValuePurpose
CONFIG_RUST_IS_AVAILABLEyRust toolchain detected and usable
CONFIG_HAVE_RUSTyArchitecture declares Rust support
CONFIG_RUSTyEnable Rust in the kernel build
CONFIG_RUST_BUILD_ASSERT_ALLOWnKeep build-time assertions (safety)

BORE: Burst-Oriented Response Enhancer

CONFIG_SCHED_BORE=y — the best interactive scheduler for Linux desktop and gaming, now enabled in Hyperion.

BORE extends the upstream EEVDF (Earliest Eligible Virtual Deadline First) scheduler with per-task burst accounting. Every task is tracked for how aggressively it historically consumes CPU time in short bursts. Interactive tasks — games, audio daemons, terminals, compositors — naturally have a low burst score because they consume CPU in brief spikes and then yield. Batch tasks — compilers, video encoders, ML training — have a high burst score because they run continuously.

BORE uses this burst history to give deadline priority to interactive tasks over batch tasks, even when both are technically "runnable" at the same time. The result is that your game, your audio, and your Wayland compositor feel perfectly smooth even when cargo build --release is pinning all your cores.

Why BORE over vanilla EEVDF / CFS:

ScenarioCFS/EEVDFBORE
Game under 100% compile loadInput latency spikes 2–5 msInput latency stays < 1 ms
PipeWire at 64-frame quantumOccasional xrunsNo xruns
Terminal under heavy I/OSluggishInstant response
Background ffmpeg + desktopCompositor jankSmooth 144 Hz

BORE is the default scheduler in CachyOS and Nobara — two of the most gaming-optimised Linux distributions. It ships as a patchset against the upstream kernel. The BURST_SMOOTHNESS=2 setting is the CachyOS-recommended balance between reactivity and throughput.

Source: github.com/firelzrd/bore-scheduler

ConfigValuePurpose
CONFIG_SCHED_BOREyEnable BORE burst-aware scheduling
CONFIG_SCHED_BORE_BURST_SMOOTHNESS2Burst score decay rate (2 = balanced)

Tuning burst smoothness at runtime:

# More reactive (better for gaming)echo 1 > /sys/kernel/debug/sched/bore_burst_smoothness
# More throughput-friendly (better for compiles)echo 3 > /sys/kernel/debug/sched/bore_burst_smoothness

ADIOS: Adaptive Deadline I/O Scheduler

CONFIG_IOSCHED_ADIOS=y — the CachyOS 2025 I/O scheduler, now the Hyperion default.

ADIOS (Adaptive Deadline I/O Scheduler) is a new I/O scheduler developed for CachyOS that combines the best properties of the Deadline and BFQ schedulers:

  • From Deadline: simplicity and determinism — every request has a hard deadline, preventing starvation
  • From BFQ: per-queue fairness and latency awareness — interactive processes (games, audio) never wait behind bulk I/O (package manager, backup)
  • New in ADIOS: adaptive deadline calculation — the scheduler learns the per-queue historical I/O latency and dynamically adjusts its deadlines to match real hardware behaviour

On NVMe drives in particular, ADIOS consistently outperforms both Kyber and BFQ in mixed desktop workloads (gaming + background compilation), because it does not over-parameterise its queuing model the way BFQ does.

Set as CONFIG_DEFAULT_IOSCHED="adios" — active by default on all block devices at boot.

Source: CachyOS linux-cachyos kernel, 2025

ConfigValuePurpose
CONFIG_IOSCHED_ADIOSyEnable ADIOS scheduler
CONFIG_DEFAULT_IOSCHED"adios"Set ADIOS as system default

Switch scheduler per-device at runtime:

# Check available schedulers
cat /sys/block/nvme0n1/queue/scheduler
# Switch to BFQ for a spinning diskecho bfq > /sys/block/sda/queue/scheduler
# Switch back to ADIOS for NVMeecho adios > /sys/block/nvme0n1/queue/scheduler

GPU: DRM_GPUVM & Display Stack

Three additions strengthen the Hyperion GPU stack for modern Vulkan workloads and laptop displays.

DRM_GPUVM — GPU Virtual Memory Manager

CONFIG_DRM_GPUVM=y — required by Mesa 24.1+ Vulkan drivers.

The GPU VM manager is a unified framework for managing GPU virtual address spaces, introduced in Linux 6.7. Modern Mesa Vulkan drivers (radv for AMD RDNA2/3, anv for Intel Arc) use it to manage GPU address spaces without driver-specific hacks. Without it, Mesa falls back to slower legacy address space management and some GPU compute features (ROCm, OpenCL) are unavailable.

It is also required for Intel Arc SR-IOV vGPU support — running multiple virtual GPU instances on a single Arc card.

DRM_EXEC — GPU Execution Context Manager

CONFIG_DRM_EXEC=y — correct multi-object GPU command submission.

Provides lock-based GPU object reservation for correct multi-object command submission without deadlocks. Required for hardware-accelerated video decode on RDNA3+ via Mesa VCN and for multi-queue Vulkan on Intel Xe.

DRM_PANEL + DRM_BRIDGE — Laptop Display Support

CONFIG_DRM_PANEL=y, CONFIG_DRM_PANEL_SIMPLE=y, CONFIG_DRM_BRIDGE=y — explicit inclusion for complete laptop display coverage.

Bridge chips connect GPU output to the physical connector (LVDS encoder, DP bridge, HDMI encoder). Many AMD and Intel laptops post-2020 use bridge chips for their internal eDP display. Without explicit inclusion of the panel and bridge subsystems, some laptop displays show as unconfigured in KMS even when the GPU driver probes correctly.

ConfigValuePurpose
CONFIG_DRM_GPUVMyGPU VM manager — Mesa 24.1+ Vulkan
CONFIG_DRM_EXECyGPU execution context manager
CONFIG_DRM_PANELyDRM panel subsystem
CONFIG_DRM_PANEL_SIMPLEyGeneric eDP/LCD panel driver
CONFIG_DRM_BRIDGEyDisplay bridge chip support

Developer Tools

v2.2.4 adds a full developer visibility suite. Every tool below has zero overhead at rest — cost is incurred only when you actively use the tool.

KGDB — Kernel GNU Debugger

CONFIG_KGDB=y — attach GDB to a live or crashed kernel over serial or USB-serial.

KGDB turns any running Hyperion kernel into a full GDB target. You can inspect memory, set breakpoints, examine call stacks, and step through kernel code — all from a remote GDB session over a serial cable or USB-to-serial adapter.

# Boot target kernel with kgdbwait to halt at boot until GDB attaches# Add to kernel cmdline: kgdbwait kgdboc=ttyS0,115200# On the host machine
gdb vmlinux
(gdb) target remote /dev/ttyUSB0
(gdb) bt # backtrace
(gdb) p current->comm # current process name
(gdb) l schedule # list scheduler code

CONFIG_KGDB_KDB=y — KDB shell activates directly on the crashed machine's VT or serial console. No remote host required. Press Alt+SysRq+G to drop into KDB at any time.

[0]kdb> ps # list all processes
[0]kdb> bt # current backtrace
[0]kdb> md 0xffffffff81000000 32 # memory dump
[0]kdb> go # resume
ConfigValuePurpose
CONFIG_KGDByKernel GDB remote debugging
CONFIG_KGDB_SERIAL_CONSOLEySerial console transport
CONFIG_KGDB_KDByBuilt-in KDB shell on crash
CONFIG_KDB_KEYBOARDyPS/2 keyboard access in KDB
CONFIG_KDB_CONTINUE_CATASTROPHIC0Halt on catastrophic error

MAGIC_SYSRQ — Emergency Kernel Controls

CONFIG_MAGIC_SYSRQ=y — keyboard shortcuts that bypass the hung userspace and talk directly to the kernel.

When your Wayland compositor locks, when a process eats all RAM, when you need a clean emergency shutdown — SysRq saves the filesystem.

Key ComboAction
Alt+SysRq+BImmediate reboot (no sync)
Alt+SysRq+SEmergency sync all filesystems
Alt+SysRq+URemount all filesystems read-only
Alt+SysRq+OPower off immediately
Alt+SysRq+KKill all processes on current VT
Alt+SysRq+TDump all task states to dmesg
Alt+SysRq+MDump memory info to dmesg
Alt+SysRq+GEnter KDB debugger
Alt+SysRq+ESend SIGTERM to all processes
Alt+SysRq+ISend SIGKILL to all processes

The safe shutdown sequence (saves filesystem on a locked system):

Alt+SysRq+S → Alt+SysRq+U → Alt+SysRq+B
(sync) (remount-ro) (reboot)
ConfigValuePurpose
CONFIG_MAGIC_SYSRQyEnable SysRq
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE1Enable all SysRq keys by default
CONFIG_MAGIC_SYSRQ_SERIALySysRq over serial console

FTRACE — Full Kernel Function Tracer

CONFIG_FTRACE=y with the complete tracer suite — the most powerful kernel observability tool available, now built into Hyperion.

Ftrace lets you trace function calls, measure interrupt latency, find preemption stalls, detect hardware latency, and profile the scheduler — all without any external tools or module loading.

# Measure worst-case interrupt latency (audio glitch diagnosis)echo irqsoff > /sys/kernel/debug/tracing/current_tracer
echo 1 > /sys/kernel/debug/tracing/tracing_on
# ... reproduce the glitch ...echo 0 > /sys/kernel/debug/tracing/tracing_on
cat /sys/kernel/debug/tracing/trace
# Trace all calls to a specific functionecho schedule > /sys/kernel/debug/tracing/set_ftrace_filter
echofunction> /sys/kernel/debug/tracing/current_tracer
echo 1 > /sys/kernel/debug/tracing/tracing_on
# Hardware latency detector (finds BIOS SMI/SMM stalls)echo hwlat > /sys/kernel/debug/tracing/current_tracer
# Wakeup latency tracer (find scheduler stalls affecting audio/gaming)echo wakeup > /sys/kernel/debug/tracing/current_tracer
# Use trace-cmd for comfortable recording
trace-cmd record -e sched:sched_wakeup -e sched:sched_switch sleep 5
trace-cmd report | head -50
ConfigValuePurpose
CONFIG_FTRACEyCore function tracer infrastructure
CONFIG_FUNCTION_TRACERyPer-function call tracing
CONFIG_FUNCTION_GRAPH_TRACERyCall graph with timing
CONFIG_IRQSOFF_TRACERyWorst-case IRQ-disabled latency
CONFIG_PREEMPT_TRACERyWorst-case preempt-disabled latency
CONFIG_SCHED_TRACERyScheduler wakeup latency
CONFIG_HWLAT_TRACERyHardware (SMI/BIOS) latency detector
CONFIG_OSNOISE_TRACERyOS noise measurement
CONFIG_TIMERLAT_TRACERyTimer latency measurement
CONFIG_DYNAMIC_FTRACEyZero overhead when not tracing (NOP patching)
CONFIG_DYNAMIC_FTRACE_WITH_REGSyFull register state on trace
CONFIG_FPROBEyFunction-level kprobe via ftrace
CONFIG_FPROBE_EVENTSyFprobe as trace events

SCHED_DEBUG — Scheduler Diagnostics

CONFIG_SCHED_DEBUG=y — exposes /proc/sched_debug and /proc/schedstat for real-time scheduler inspection.

Essential for tuning BORE burst scores, monitoring sched-ext BPF scheduler behaviour, and diagnosing scheduling-related latency problems.

# Live scheduler state (per-CPU run queues, current tasks, latency stats)
watch -n 0.5 cat /proc/sched_debug
# Per-process scheduler statistics
cat /proc/self/sched
# Domain topology and load balancing stats
cat /proc/schedstat
# With sched-ext active: check which scheduler is running
cat /sys/kernel/sched_ext/ops_name
cat /sys/kernel/sched_ext/state

DYNAMIC_DEBUG — Per-Site Debug Messages

CONFIG_DYNAMIC_DEBUG=y — toggle kernel debug messages per module, file, or function at runtime, with zero overhead when off (implemented as jump labels).

# Enable DRM debug messages for GPU troubleshootingecho"module drm +p"> /sys/kernel/debug/dynamic_debug/control
# Enable AMDGPU-specific debugecho"module amdgpu +p"> /sys/kernel/debug/dynamic_debug/control
# Enable USB debug for a specific fileecho"file drivers/usb/core/hub.c +p"> /sys/kernel/debug/dynamic_debug/control
# Disable all debugecho"module drm -p"> /sys/kernel/debug/dynamic_debug/control

Network Additions

TAPRIO — Time-Aware Priority Shaper

CONFIG_NET_SCH_TAPRIO=y (IEEE 802.1Qbv) — the foundation for precision packet timing.

TAPRIO enables SO_TXTIME and SCM_TXTIME socket options, which allow applications to specify the exact nanosecond timestamp at which a packet should be transmitted. This is used by:

  • QUIC / HTTP3 — pacing packet bursts to avoid self-congestion
  • Game networking stacks — sending packets at precise intervals to reduce jitter
  • Time-Sensitive Networking (TSN) — industrial/audio real-time Ethernet
  • PTP hardware timestamping — sub-microsecond network clock synchronisation

CONFIG_NET_SCH_ETF=y (Earliest TxTime First) — companion to TAPRIO. Ensures packets are dequeued in SO_TXTIME order, preventing out-of-order transmission on hardware that supports launch time offload.

UDP GRO — Generic Receive Offload for UDP

CONFIG_UDP_GRO=y — approximately 2× UDP receive throughput for QUIC/HTTP3 workloads.

UDP GRO coalesces multiple small UDP datagrams into a single large skb before passing up the network stack. This dramatically reduces per-packet overhead for QUIC traffic (which uses many small UDP packets) and benefits any application that receives high-rate UDP streams (game servers, VoIP, DNS resolvers).

TCP_NOTSENT_LOWAT — Eliminate Kernel-Side Bufferbloat

CONFIG_TCP_NOTSENT_LOWAT=y — enables the SO_NOTSENT_LOWAT socket option.

This option prevents TCP from buffering more data in the kernel send buffer than can be sent immediately. Without it, applications that write aggressively to a TCP socket can fill the kernel buffer, adding hundreds of milliseconds of hidden latency — the "kernel-side bufferbloat" problem. Setting SO_NOTSENT_LOWAT on gaming and streaming sockets eliminates this hidden delay.

ConfigValuePurpose
CONFIG_NET_SCH_TAPRIOyTime-Aware Priority Shaper (SO_TXTIME)
CONFIG_NET_SCH_ETFyEarliest TxTime First dequeuing
CONFIG_TCP_NOTSENT_LOWATySO_NOTSENT_LOWAT kernel-side bufferbloat fix
CONFIG_UDP_GROy~2× UDP receive throughput
CONFIG_GRO_CELLSyMulti-producer GRO for high-pps NICs
CONFIG_NET_EMATCHyExtended TC classifier match framework

ZRAM Dual-Stream LZ4HC

CONFIG_ZRAM_DEF_COMP2="lz4hc" — the secondary compression stream for ZRAM multi-comp.

With CONFIG_ZRAM_MULTI_COMP=y (already present since v2.2.4), ZRAM supports two compression algorithms simultaneously:

  • Primary stream (zstd): best compression ratio — maximises the amount of data you can fit into ZRAM
  • Secondary stream (lz4hc): LZ4 High Compression — better ratio than plain LZ4, with 3–4× faster decompression than ZSTD under extreme memory pressure

When the system is critically low on memory and needs to decompress swap pages as fast as possible to recover, LZ4HC's speed advantage over ZSTD is the difference between a responsive system and a stall.

# Recommended ZRAM setup for a 32 GB systemecho 16G > /sys/block/zram0/disksize
echo zstd > /sys/block/zram0/comp_algorithm
echo lz4hc > /sys/block/zram0/comp_algorithm2
mkswap /dev/zram0
swapon -p 100 /dev/zram0
# Verify dual-stream is active
cat /sys/block/zram0/comp_algorithm
# Expected: [zstd] lz4hc lz4 deflate ...# Check compression stats
cat /sys/block/zram0/mm_stat

On a 32 GB system this configuration recovers approximately 3 GB of additional physical RAM versus single-stream ZSTD, with faster recovery under memory pressure peaks.


GCC Build Optimisation Flags

v2.2.4 documents the recommended KCFLAGS for squeezing maximum performance from the GCC-compiled kernel.

make -j$(nproc) \
LOCALVERSION="-Hyperion-2.2.4" \
KCFLAGS="-fivopts -fmodulo-sched -fno-semantic-interposition" \
bzImage modules
FlagEffect
-fivoptsInduction variable optimisation — restructures loop counter variables for better register allocation. Measurable win in tight loops (physics engines, video codecs, schedulers).
-fmodulo-schedSoftware pipelining — fills CPU execution slots between loop iterations by scheduling instructions from the next iteration. Benefit in audio DSP, SIMD loops, codec inner loops.
-fno-semantic-interpositionAllows GCC to inline and optimise calls within the same compilation unit that would otherwise be blocked by the default assumption of DSO interposition. ~3–5% function call overhead reduction across the vmlinux binary.

For Clang ThinLTO (even better — requires Clang toolchain):

make -j$(nproc) \
CC=clang LD=ld.lld AR=llvm-ar NM=llvm-nm \
LOCALVERSION="-Hyperion-2.2.4" \
LLVM=1 LLVM_IAS=1 \
bzImage modules

Clang ThinLTO (CONFIG_LTO_CLANG_THIN) provides link-time inlining across translation units — the most impactful single optimisation available for kernel performance.


BPF & JIT

BPF is the backbone of networking, security (LSM), and scheduling (sched-ext) in 2026. Every BPF program must run at native machine speed via JIT — interpreted BPF is 10–100× slower and carries additional Spectre-class attack surface.

ConfigValueImpact
CONFIG_BPF_JITyBPF programs compile to native x86_64 — prerequisite for everything else
CONFIG_BPF_JIT_ALWAYS_ONyRemoves the interpreter entirely; eliminates Spectre-BPF attack surface
CONFIG_BPF_JIT_DEFAULT_ONyJIT active from boot without sysctl — sched-ext and Cilium work out of the box
CONFIG_BPF_UNPRIV_DEFAULT_OFFyUnprivileged users cannot load BPF; closes CVE-2021-3490/2022-0185/2023-2163 class

Verify at runtime:

cat /proc/sys/net/core/bpf_jit_enable
# Expected: 1
cat /proc/sys/kernel/unprivileged_bpf_disabled
# Expected: 2 (fully disabled)

sched-ext: Runtime BPF Schedulers

CONFIG_SCHED_CLASS_EXT=y enables the extensible scheduler class merged in Linux 6.12. The CPU scheduling policy can now be replaced at runtime with a BPF program — no reboot, no recompile.

Install the scx tools:

# Arch
yay -S scx-scheds
# From source (requires Rust)
git clone https://github.com/sched-ext/scx
cd scx && cargo build --release
sudo cp target/release/scx_* /usr/local/bin/

Available schedulers:

SchedulerBest forNotes
scx_bpflandDesktop and gaming — interactive-first, lowest input latencyBORE-compatible
scx_lavdLatency-critical workloads — the CachyOS defaultBest with BORE
scx_rustyNUMA workstations and multi-socket serversMeta production
scx_ticklessHPC and ML inference — aggressive ticklessBatch workloads
# Load gaming scheduler
sudo scx_bpfland &# Verify
cat /sys/kernel/sched_ext/state # Expected: enabled
cat /sys/kernel/sched_ext/ops_name # Expected: bpfland# Switch to NUMA scheduler for a compile job
sudo pkill scx_bpfland && sudo scx_rusty &# Revert to CFS/BORE
sudo pkill scx_rusty

x86 Instruction Tuning

ConfigImpact
CONFIG_X86_X2APIC=yScales interrupt routing to 2^32 CPUs; reduces APIC register access latency on all platforms
CONFIG_X86_CHECK_BIOS_CORRUPTION=yPeriodic scan of BIOS reserved memory; catches firmware that silently overwrites kernel data
CONFIG_X86_INTEL_USERCOPY_CHECK=ySelects ERMSB (enhanced REP MOVSB) for copy_to/from_user — ~2× throughput on Haswell+ for large syscall buffers
CONFIG_X86_AMD_PSTATE_DEFAULT_MODE=3Active EPP: AMD hardware manages its own boost in microseconds, faster than any OS governor

Filesystem Integrity & Unicode

ConfigPurpose
CONFIG_FS_ENCRYPTION=yPer-file AES encryption (fscrypt) — required by Android, ChromeOS, ext4 encrypt
CONFIG_FS_VERITY=yPer-file Merkle-tree integrity — Android APK signing, Flatpak runtime verification
CONFIG_FS_VERITY_BUILTIN_SIGNATURES=yVerity digests verifiable against kernel keyring — enables IPE policy enforcement
CONFIG_UNICODE=y + CONFIG_UNICODE_UTF8_DATA=yCase-insensitive directory lookups — Steam/Wine Windows game asset compatibility

Virtualization & Container Hardening

All vhost/vsock options ensure zero-copy guest networking and reliable Waydroid/container communication:

ConfigEffect
CONFIG_VHOST_NET=yZero-copy virtio-net kernel backend — eliminates one context switch per packet vs QEMU userspace
CONFIG_VHOST_IOTLB=yIOMMU TLB for vhost devices — required for SR-IOV VF passthrough correctness
CONFIG_VHOST_VSOCK=yKernel-side vsock accelerator for host↔guest RPC
CONFIG_VSOCKETS=y + CONFIG_VSOCKETS_DIAG=yAF_VSOCK socket family + diagnostics
CONFIG_VSOCK_LOOPBACK=yLoopback vsock — fixes Waydroid clipboard, ADB, and full-UI

Security: Landlock & IPE

Landlock

CONFIG_SECURITY_LANDLOCK=y — unprivileged per-process filesystem sandboxing. Unlike AppArmor/SELinux which require root policy configuration, Landlock is application-driven: any process can sandbox its own file access via syscall. Used by Flatpak, bubblewrap, and systemd-run --property=.

Integrity Policy Enforcement (IPE)

IPE enforces policies that restrict code execution to files residing on dm-verity or fs-verity verified filesystems.

# Example IPE policy: allow execution only from boot-verified root
policy_name="hyperion-lockdown" policy_version=0.0.1
DEFAULT action=DENY
op=EXECUTE boot_verified=TRUE action=ALLOW
ConfigPurpose
CONFIG_SECURITY_IPE=yIPE LSM core
CONFIG_IPE_PROP_BOOT_VERIFIED=yExpose dm-verity boot-verified property to policy
CONFIG_IPE_PROP_DM_VERITY=ydm-verity integrity property
CONFIG_IPE_PROP_FS_VERITY=yfs-verity file integrity property
CONFIG_IPE_PROP_FS_VERITY_BUILTIN_SIG=ySigned verity property (kernel keyring)

Debug Discipline

The following are intentionally disabled. Each one is documented so the decision is visible and reviewable:

ConfigOverheadDecision
CONFIG_DEBUG_PREEMPT~3% syscall overheadOff — preemption code is correct
CONFIG_PROVE_LOCKING (lockdep)~40% lock overheadOff — use a debug kernel for lockdep
CONFIG_DEBUG_ATOMIC_SLEEPFalse positives in audio RTOff — breaks legitimate RT paths
CONFIG_DEBUG_VMPer-page overheadOff — unacceptable for gaming/media
CONFIG_KASAN2× memory overheadOff — use a sanitiser build separately
CONFIG_UBSANCodegen bloatOff — use a sanitiser build separately
CONFIG_KCSAN~50% overheadOff — data race detection for development only

Always on (zero overhead at rest):

  • CONFIG_STACKTRACE=y — required by perf, bpftrace, BPF stack maps, crash dumps
  • CONFIG_KGDB=y — dormant until activated via cmdline or SysRq
  • CONFIG_FTRACE=y with CONFIG_DYNAMIC_FTRACE=y — all trace sites are NOPs until enabled
  • CONFIG_DYNAMIC_DEBUG=y — all debug messages are disabled jumps until toggled
  • CONFIG_SCHED_DEBUG=y — data gathered only on /proc/sched_debug read
  • CONFIG_LOCKUP_DETECTOR=y — only fires when something is actually wrong

Philosophy

"A kernel should never be the reason your work stopped."

Hyperion is built on five principles:

  1. Config-Driven — improvements are kernel configuration choices backed by upstream code the kernel community maintains. No staging drivers. No out-of-tree patches for functionality available in-tree. BORE and ADIOS are the only patchset additions, and both are actively maintained with upstream submission in progress.

  2. Documented Decisions — every config option has a comment with its rationale and a source reference. This config is something you can read and learn from, not just apply blindly.

  3. Performance Without Sacrifice — every nanosecond of latency extracted from the hardware, never at the cost of correctness or stability. Debug infrastructure is included but costs nothing at rest.

  4. Developer First — KPROBES, UPROBE_EVENTS, KGDB, KDB, FTRACE with all tracers, DYNAMIC_DEBUG, bpftrace/bcc, LIVEPATCH, full sched-ext support, Rust infrastructure. The kernel is an observable, debuggable, modifiable system.

  5. Universal by Default — one bzImage boots correctly on Arch, Ubuntu, Fedora, RHEL, openSUSE, Gentoo, and NixOS without configuration.


Key Features

CategoryFeatureDetails
IdentityCustom brandinguname -r6.19.6-Hyperion-2.2.4
BuildMonolithic imageAll in-tree drivers promoted to =y — zero module-load latency
BuildZSTD compression~40% faster boot than GZIP on NVMe
BuildRust supportCONFIG_RUST=y — Rust kernel drivers enabled, GCC 14.2.0
BPFJIT always-onNative x86_64 BPF, no interpreter, Spectre-BPF mitigated
BPFUnprivileged blockedBPF_UNPRIV_DEFAULT_OFF — closes entire CVE class
SchedulerBOREBurst-Oriented Response Enhancer — best interactive feel under load
Schedulersched-extRuntime-swappable BPF schedulers: scx_bpfland, scx_lavd, scx_rusty
SchedulerFull preemptionPREEMPT=y + PREEMPT_DYNAMIC=y + PREEMPT_LAZY=y
SchedulerSub-ms ticksSCHED_HRTICK=y — hrtimer-resolution preemption
Timer1000 HzCONFIG_HZ_1000=y — 1 ms scheduler granularity
IOADIOSAdaptive Deadline I/O Scheduler — CachyOS 2025 default
IOBFQ + Kyber + DeadlineAll schedulers built-in, switchable per-device
IOio_uringBuilt-in — zero module-load delay
MemoryMGLRU + MMU walkAccurate cold-page detection, fewer false evictions
MemoryZRAM dual-streamZSTD primary + LZ4HC secondary via ZRAM_MULTI_COMP
MemoryZSWAP ZSTDCompressed in-RAM swap — defeats OOM before it starts
MemoryBOREInteractive tasks never OOM before batch tasks
NetworkBBR defaultGoogle's low-latency TCP congestion control
NetworkCAKE qdiscBest-in-class bufferbloat elimination
NetworkTAPRIOSO_TXTIME pacing for QUIC, TSN, game networking
NetworkUDP GRO~2× UDP receive throughput (QUIC/HTTP3)
NetworkTCP_NOTSENT_LOWATEliminates kernel-side bufferbloat
NetworkWireGuardBuilt-in modern VPN — ~10 Gbps with ChaCha20-NI
NetworkBPF sockmapZero-copy socket redirection for Cilium/Envoy
FilesystemFS_VERITYPer-file Merkle-tree integrity
FilesystemFS_ENCRYPTIONPer-file fscrypt AES encryption
FilesystemUnicodeCase-insensitive fs for Steam/Wine compatibility
CPUAMD P-State ActiveMode 3 EPP — best Zen3/4 boost
CPUIntel P-State + HWPHardware-managed boost
CPUX86_INTEL_USERCOPY_CHECKERMSB ~2× faster user↔kernel copies
GPUDRM_GPUVMGPU VM manager — Mesa 24.1+ Vulkan (radv/anv)
GPUDRM_EXECMulti-object GPU command submission
GPUDRM_PANEL + DRM_BRIDGELaptop eDP display coverage
GPUDRM_SCHEDPriority-aware GPU job scheduler
SecurityIPEBoot-verified integrity policy enforcement
SecurityLandlockUnprivileged per-process sandboxing
SecurityAppArmor (default)Arch, Ubuntu, Debian
SecuritySELinuxFedora, RHEL, CentOS
SecurityBPF LSMeBPF-based MAC policies
DevKGDB + KDBFull GDB remote debugging + on-machine KDB shell
DevMAGIC_SYSRQEmergency kernel controls — safe shutdown sequence
DevFTRACEFull tracer suite: irqsoff, preemptoff, hwlat, wakeup, osnoise
DevSCHED_DEBUG/proc/sched_debug for BORE/scx tuning
DevDYNAMIC_DEBUGPer-site debug message toggle at runtime
DevKPROBES + UPROBESbpftrace/bcc without configuration
DevLIVEPATCHZero-downtime CVE patching
VirtVHOST_NETZero-copy virtio-net kernel backend
VirtVSOCK_LOOPBACKWaydroid clipboard/ADB fixed
VirtKVM fullIntel VT-x + AMD-V, SEV, SEV-SNP, TDX
USBAutosuspend offUSB_AUTOSUSPEND_DELAY=-1 — no device ever sleeps
USB1 kHz pollingusbhid.mousepoll/kbpoll/jspoll=1
AudioSOF + HDA + AMDIce Lake through Meteor Lake, AMD ACP, RT5682, CS35L41
Wi-FiUniversalATH9K/10K/11K/12K, RTW88/89, MT7921/7925, IWLWIFI
ModulesIKHEADERSIn-kernel headers always available
ModulesMODVERSIONSABI mismatch caught at load, not panic

Performance Configuration

CPU Scheduling

Hyperion v2.2.4 ships with a three-layer scheduling stack:

  1. BORE (CONFIG_SCHED_BORE=y) — the base scheduler. Every process gets burst accounting. Interactive tasks always beat batch tasks in deadline competition.
  2. sched-ext (CONFIG_SCHED_CLASS_EXT=y) — replaces the entire CFS/BORE policy at runtime with a BPF scheduler. Use scx_bpfland for gaming, scx_lavd for CachyOS-style interactive, scx_rusty for NUMA.
  3. PREEMPT_DYNAMIC — boot parameter controls preemption model: preempt=full (gaming), preempt=lazy (compile workloads), preempt=voluntary (server).

I/O Scheduling

ADIOS is the new default. Switch per-device based on the hardware:

# NVMe (default: ADIOS — best latency + throughput)echo adios > /sys/block/nvme0n1/queue/scheduler
# Desktop HDD or SSHD (BFQ — per-process fairness)echo bfq > /sys/block/sda/queue/scheduler
# High-throughput server (deadline — simple, deterministic)echo deadline > /sys/block/nvme1n1/queue/scheduler

Memory

# THP: madvise mode (apps that want THPs get them; small allocs don't waste memory)echo madvise > /sys/kernel/mm/transparent_hugepage/enabled
# MGLRU: 4 generations (default)echo 4 > /sys/kernel/mm/lru_gen/min_ttl_ms
# ZRAM multi-stream dual-comp setupecho 16G > /sys/block/zram0/disksize
echo zstd > /sys/block/zram0/comp_algorithm
echo lz4hc > /sys/block/zram0/comp_algorithm2
mkswap /dev/zram0 && swapon -p 100 /dev/zram0

Hardware Support

Wi-Fi — Universal Chipset Coverage

VendorDriverStandards
Qualcomm/AtherosATH9K802.11n
Qualcomm/AtherosATH10K802.11ac
Qualcomm/AtherosATH11KWi-Fi 6 (AX)
Qualcomm/AtherosATH12KWi-Fi 7 (BE)
RealtekRTW88802.11ac
RealtekRTW89Wi-Fi 6/6E
IntelIWLWIFI (DVM + MVM)802.11ac/ax — AX200, AX210, AX211
MediaTekMT7921Wi-Fi 6
MediaTekMT7925Wi-Fi 7
BroadcomBRCMFMAC802.11ac

All drivers are built-in (=y). No module loading required at boot.

GPU & Display

DriverHardware
DRM_AMDGPUAMD GCN1 through RDNA3 — FreeSync, ROCm/HSA
DRM_I915Intel Gen4 through Xe (Arc)
DRM_XEIntel Arc/Battlemage
DRM_NOUVEAUNVIDIA Turing/Ampere/Lovelace display
DRM_VIRTIO_GPUQEMU/KVM guests
DRM_GPUVMGPU VM manager for Mesa 24.1+ Vulkan (new in v2.2.4)

Audio

PlatformCoverage
Intel SOFIce Lake through Meteor Lake (10th–14th gen)
AMD ACPRyzen 4000/5000/6000/7000 laptops
RT5682/CS35L41Virtually every modern laptop codec
USB audioSND_USB_AUDIO=y with autosuspend off — no DAC clicks

Storage

NVMe (PCIe), NVMe-oF TCP/RDMA/FC, SATA AHCI, SCSI multi-queue, UFS — all built-in. Filesystems: ext4, XFS, Btrfs, F2FS, NTFS3, exFAT, squashfs, EROFS, overlay, NFS v4.x, CIFS/SMB.


Security

Three LSMs compiled in simultaneously; active LSM selected via security= cmdline:

LSMDefault forActivation
AppArmorArch, Ubuntu, DebianDefault
SELinuxFedora, RHEL, Rockysecurity=selinux
TOMOYOopenSUSEsecurity=tomoyo
LandlockAllPer-process via syscall
BPF LSMAlllsm=bpf,... cmdline
IPEAllPolicy loaded via securityfs

Additional hardening active by default:

FeatureEffect
HARDENED_USERCOPY=yBuffer overflow detection at user/kernel boundaries
RANDOMIZE_KSTACK_OFFSET_DEFAULT=yPer-syscall kernel stack randomisation
INIT_STACK_ALL_ZERO=yZero-initialise all stack variables
FORTIFY_SOURCE=yGCC compile-time buffer length checks
STACKPROTECTOR_STRONG=yStack canary on all functions with local arrays
PAGE_TABLE_ISOLATION=y + RETPOLINE=ySpectre/Meltdown mitigations
BPF_UNPRIV_DEFAULT_OFF=yCloses entire unprivileged-BPF CVE class
SECURITY_IPE=yBoot-verified integrity policy enforcement
RANDOM_KMALLOC_CACHES=yRandomised slab caches defeating heap spray (Linux 6.6+)
HARDENED_USERCOPY_FALLBACK=nStrict mode — no fallback on boundary violations

Build Instructions

Prerequisites

# Arch
sudo pacman -S base-devel bc cpio pahole python rust rust-bindgen
# Fedora
sudo dnf install gcc make bc cpio pahole python3 rust rust-bindgen-cli
# Debian/Ubuntu
sudo apt install build-essential bc cpio dwarves python3 rustc bindgen

Quick Start

# Get kernel source
wget https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.19.6.tar.xz
tar -xf linux-6.19.6.tar.xz &&cd linux-6.19.6
# Apply BORE and ADIOS patchsets (if not already in-tree)forpin ../patches/*.patch;do patch -p1 --fuzz=5 <"$p";done# Apply config
cp ../hyperion.config .config
make olddefconfig LOCALVERSION="-Hyperion-2.2.4"# Build (standard)
make -j$(nproc) LOCALVERSION="-Hyperion-2.2.4" bzImage modules
# Build with extra GCC performance flags
make -j$(nproc) \
LOCALVERSION="-Hyperion-2.2.4" \
KCFLAGS="-fivopts -fmodulo-sched -fno-semantic-interposition" \
bzImage modules
# Build with Clang ThinLTO (maximum performance, requires Clang)
make -j$(nproc) \
CC=clang LD=ld.lld AR=llvm-ar NM=llvm-nm \
LOCALVERSION="-Hyperion-2.2.4" \
LLVM=1 LLVM_IAS=1 \
bzImage modules

Installation

sudo make modules_install
sudo make install
sudo update-grub # or grub2-mkconfig / grub-mkconfig per your distro

Generate initramfs:

# Arch (mkinitcpio)
sudo mkinitcpio -k 6.19.6-Hyperion-2.2.4 -g /boot/initramfs-hyperion-2.2.4.img
# Fedora/RHEL (dracut)
sudo dracut --force /boot/initramfs-6.19.6-Hyperion-2.2.4.img 6.19.6-Hyperion-2.2.4
# Debian/Ubuntu (update-initramfs)
sudo update-initramfs -c -k 6.19.6-Hyperion-2.2.4

Post-install verification:

uname -r
# Expected: 6.19.6-Hyperion-2.2.4
cat /proc/sys/net/core/bpf_jit_enable
# Expected: 1
cat /sys/module/usbcore/parameters/autosuspend
# Expected: -1# Verify v2.2.4 specific features
zcat /proc/config.gz | grep -E "^CONFIG_(RUST|SCHED_BORE|IOSCHED_ADIOS|KGDB|MAGIC_SYSRQ|FTRACE|DRM_GPUVM|NET_SCH_TAPRIO|UDP_GRO|ZRAM_MULTI_COMP)="# Verify BORE is available
cat /sys/kernel/debug/sched/bore_burst_smoothness
# Expected: 2# Verify ADIOS is the default scheduler
cat /sys/block/nvme0n1/queue/scheduler
# Expected: [adios] bfq kyber deadline mq-deadline none

Recommended Boot Parameters

AMD (Zen3/4 Desktop)

quiet splash
preempt=full threadirqs
usbcore.autosuspend=-1 usbcore.use_persist=1
usbhid.mousepoll=1 usbhid.kbpoll=1 usbhid.jspoll=1
amd_pstate=active amd_iommu=pt
transparent_hugepage=madvise hugepagesz=2M hugepages=512
nohz_full=1-N rcu_nocbs=1-N skew_tick=1 nosoftlockup
lsm=landlock,lockdown,yama,integrity,apparmor,bpf

Intel (12th/13th/14th gen Desktop)

quiet splash
preempt=full threadirqs
usbcore.autosuspend=-1 usbcore.use_persist=1
usbhid.mousepoll=1 usbhid.kbpoll=1 usbhid.jspoll=1
intel_pstate=active
transparent_hugepage=madvise hugepagesz=2M hugepages=512
nohz_full=1-N rcu_nocbs=1-N skew_tick=1 nosoftlockup
lsm=landlock,lockdown,yama,integrity,apparmor,bpf

With KGDB (Development / Debugging)

quiet splash preempt=full threadirqs
kgdboc=ttyS0,115200 # attach GDB over first serial port
# OR: kgdboc=kbd # use keyboard (requires KDB)
# To halt at boot: add kgdbwait
amd_pstate=active
lsm=landlock,lockdown,yama,integrity,apparmor,bpf

Replace N with your last CPU index (nproc --all minus 1).

Note: lsm= includes integrity (required for IMA/IPE) and places landlock first.


Runtime Tuning: sysctl Companion

Add to /etc/sysctl.d/99-hyperion.conf:

# =============================================# HYPERION v2.2.4 — Recommended sysctl tuning# =============================================# Memoryvm.swappiness = 10 # Strongly prefer RAM over swapvm.dirty_ratio = 10 # Flush dirty pages at 10% of RAMvm.dirty_background_ratio = 5 # Start background writeback at 5%vm.vfs_cache_pressure = 50 # Keep dentries/inodes cached longerkernel.numa_balancing = 1 # NUMA page migration enabled# Networkingnet.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = bbr
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
net.ipv4.tcp_fastopen = 3 # Client + server TFOnet.core.netdev_max_backlog = 8192 # NIC receive queue depth# BPF / unprivilegedkernel.unprivileged_bpf_disabled = 2
# Schedulerkernel.sched_autogroup_enabled = 1

Apply immediately:

sudo sysctl -p /etc/sysctl.d/99-hyperion.conf

Troubleshooting

BORE not active / burst tuning

# Confirm BORE is compiled in
zcat /proc/config.gz | grep SCHED_BORE
# Expected: CONFIG_SCHED_BORE=y# Read current burst smoothness
cat /sys/kernel/debug/sched/bore_burst_smoothness
# Expected: 2# Make more reactive for gaming (persist across boots via sysctl)echo 1 > /sys/kernel/debug/sched/bore_burst_smoothness

ADIOS scheduler not available

zcat /proc/config.gz | grep IOSCHED_ADIOS
# Expected: CONFIG_IOSCHED_ADIOS=y
cat /sys/block/nvme0n1/queue/scheduler
# If adios is missing, the ADIOS patch was not applied to the source tree# Check: ls ../patches/ | grep adios

KGDB not connecting

# Ensure kgdboc is set in cmdline
cat /proc/cmdline | grep kgdboc
# Trigger entry into KGDB from a running systemecho g > /proc/sysrq-trigger
# Then from host:
gdb vmlinux
(gdb) target remote /dev/ttyUSB0

FTRACE showing no output

# Check tracer is set
cat /sys/kernel/debug/tracing/current_tracer
# Check tracing is on
cat /sys/kernel/debug/tracing/tracing_on
# Enable and collectecho irqsoff > /sys/kernel/debug/tracing/current_tracer
echo 1 > /sys/kernel/debug/tracing/tracing_on
sleep 2
echo 0 > /sys/kernel/debug/tracing/tracing_on
cat /sys/kernel/debug/tracing/trace | head -40

sched-ext not loading

# Check kernel support
zcat /proc/config.gz | grep SCHED_CLASS_EXT
# Expected: CONFIG_SCHED_CLASS_EXT=y# Check BPF JIT is on
cat /proc/sys/net/core/bpf_jit_enable
# Expected: 1# Install scx tools
which scx_bpfland || yay -S scx-scheds

IPE policy not applying

# Check IPE is active
ls /sys/kernel/security/ipe/
# If empty, add "integrity" to lsm= cmdline parameter# Check FS verity is supported on your filesystem
tune2fs -l /dev/sdX | grep -i verity

ZRAM multi-comp not working

zcat /proc/config.gz | grep ZRAM_MULTI_COMP
# Expected: CONFIG_ZRAM_MULTI_COMP=y# Check available algorithms
cat /sys/block/zram0/comp_algorithm
# Expected: ... [zstd] lz4hc ...# If lz4hc is missing from list, kernel was built without lz4hc support
zcat /proc/config.gz | grep LZ4HC

Rust build failure

# Check rustc version (needs >= 1.78)
rustc --version
# Check bindgen
bindgen --version
# If wrong version, use rustup
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
rustup install 1.78
rustup override set 1.78

No Wi-Fi

lspci -k | grep -A3 -i "wireless\|network"
dmesg | grep -i "firmware\|ath\|iwl\|rtw\|mt76"# All drivers require firmware blobs from linux-firmware
sudo pacman -S linux-firmware # Arch
sudo apt install firmware-linux # Debian/Ubuntu
sudo dnf install linux-firmware # Fedora

Development Workflow

patches/*.patch → patch -p1 → hyperion.config → make olddefconfig → bzImage
  1. Config changes: edit hyperion.config directly. Every option needs a comment with rationale and source. Follow the inline comment style.
  2. Source patches: add NNNN-description.patch to patches/. BORE and ADIOS live here.
  3. Build:bash scripts/build-kernel.sh or the manual make commands above
  4. CI: auto-builds on every push via .github/workflows/build.yml

Verifying all v2.2.4 features after build

#!/bin/bash# hyperion-verify.shdeclare -A checks=(
[RUST]="CONFIG_RUST=y"
[BORE]="CONFIG_SCHED_BORE=y"
[ADIOS]="CONFIG_IOSCHED_ADIOS=y"
[KGDB]="CONFIG_KGDB=y"
[SYSRQ]="CONFIG_MAGIC_SYSRQ=y"
[FTRACE]="CONFIG_FTRACE=y"
[DRM_GPUVM]="CONFIG_DRM_GPUVM=y"
[TAPRIO]="CONFIG_NET_SCH_TAPRIO=y"
[UDP_GRO]="CONFIG_UDP_GRO=y"
[ZRAM_MULTI]="CONFIG_ZRAM_MULTI_COMP=y"
[SCHED_EXT]="CONFIG_SCHED_CLASS_EXT=y"
[BBR]="CONFIG_TCP_CONG_BBR=y"
[BPF_JIT]="CONFIG_BPF_JIT=y"
[IPE]="CONFIG_SECURITY_IPE=y"
[BORE_SMOOTHNESS]="CONFIG_SCHED_BORE_BURST_SMOOTHNESS=2"
)
echo"=== Hyperion v2.2.4 Feature Verification ==="fornamein"${!checks[@]}";do
val="${checks[$name]}"if zcat /proc/config.gz 2>/dev/null | grep -q "^$val";thenecho"$name"elseecho"$name (expected: $val)"fidone

Credits

RoleName
Linux Kernel DeveloperSoumalya Das
Base KernelLinus Torvalds & the Linux kernel community
Config inspirationCachyOS, XanMod, Nobara, Liquorix, Arch, Fedora, Ubuntu
BORE SchedulerMasahito Suzuki (firelzrd)
ADIOS I/O SchedulerCachyOS kernel team
sched-ext / BPF schedulerssched-ext/scx project, CachyOS team
sched-ext frameworkTejun Heo, David Vernet
BPF/JITAlexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
Rust for LinuxMiguel Ojeda, Alex Gaynor, and the Rust for Linux team
IPE frameworkFan Wu, Deven Bowers (Microsoft)
LandlockMickaël Salaün
ZRAM multi-compSergey Senozhatsky
FS VerityEric Biggers (Google)
DRM_GPUVMThomas Hellström (Intel)
UDP GROEric Dumazet (Google)
TAPRIO / TSNVinicius Costa Gomes (Intel)
AMD P-StateAMD Open Source driver team
Intel P-StateIntel Open Source Technology Center
BORE burst smoothnessMasahito Suzuki, CachyOS integration
BPF sockmapJohn Fastabend, Daniel Borkmann
Memory managementMGLRU: Yu Zhao (Google); DAMON: SeongJae Park (Amazon)
PREEMPT_LAZYPeter Zijlstra, Thomas Gleixner
USB autosuspend analysisSarah Sharp, Alan Stern
Live kernel patchingJosh Poimboeuf (Red Hat)
Security hardeningKees Cook
KGDBJason Wessel
ftrace / dynamic tracingSteven Rostedt
Performance researchPhoronix, LKML, r/linux_gaming, CachyOS/XanMod teams

License

Hyperion Kernel configuration, scripts, and documentation are released under the MIT License.

The Linux kernel itself is licensed under GPL-2.0-only.


Built with precision. Tuned for humans. Named after a Titan.

Hyperion Kernel v2.2.4 · Soumalya Das · 2026

🧠🐧⚡🦀

About

Hyperion Kernel 🚀 – 2026 Linux kernel optimized for performance ⚡, gaming 🎮, low-latency I/O ⚙️, Android 🤖, and programming 💻. Features automated CI ⚙️, patch management 📝, and release-ready builds 📦✅.

Topics

Resources

Code of conduct

Contributing

Stars

9 stars

Watchers

5 watching

Forks

Releases

Packages

Contributors

Languages