News › linux
By The Linux Camp News, October 13, 2026
The October 12 pull request adds Nova memory-management infrastructure and changes its userspace query interface. It establishes proposed development work, not a released driver update.
An October 12, 2026 DRM Rust pull request targeting Linux 7.4-rc1 proposes new memory management, CPU access to GPU memory and interrupt handling for Nova, the developing Rust NVIDIA driver. Phoronix reported the submission on October 13. The sources retrieved that day establish a request to pull the work into DRM-Next, not acceptance or availability in a released kernel. 2 1 3
The memory work separates obtaining memory from arranging access to it. A buddy allocator manages VRAM, the GPU's memory; MMU v2/v3 page-table support supplies the mapping machinery. Virtual-address tracking uses a maple tree, while allocation and mapping execution become separate operations. BAR1 then gives the CPU access to mapped VRAM. Together, these are building blocks for managing and accessing GPU memory, rather than a reported rendering-performance improvement. 2
The immediate compatibility issue is for developers maintaining Nova userspace tools. The proposed INFO ioctl, a userspace request to the driver, reports GPU identity and memory sizes and supports discovering the required output size. It truncates output to the supplied buffer. BAR-size queries move into GPU information and GETPARAM disappears, changing the userspace API. Tool maintainers should therefore review existing GETPARAM calls and buffer-size handling when testing against this submission, rather than assume the old query interface remains available. 2
Event handling also changes: GPU Interrupt and Notification support uses MSI-X with an MSI fallback, and a threaded handler drains GSP events between commands. Error and notification reporting can continue without aborting command waits. That does not mean faults are ignored: persistent falcon faults or event-drain errors disable GSP event interrupts. The distinction matters when testing failures because reporting a message and shutting down its interrupt path are separate responses. 2
Developers evaluating the proposed code can check whether CONFIG_NOVA_CORE_SELFTESTS enables its optional probe-time tests. A separate CPU-access facility uses the movable 1 MiB BAR0 PRAMIN window to reach VRAM, with architecture-specific support described as Turing through Blackwell. That range applies to this access facility; it should not be treated as a full-driver compatibility matrix. The submission lists tests but supplies no execution results establishing reliability. 2
Integration also depends on shared driver-core changes for the register macro rework and DMA bound-lifetime enforcement. Anyone evaluating the pull request must account for those dependencies rather than treating the Nova patches as an isolated driver update. The request does not settle which eventual released kernel will contain the work. 2