Task List¶
Tasks may have the following fields:
Complexity: Describes the required familiarity with Rust and / or the corresponding kernel APIs or subsystems. There are four different complexities,Beginner,Intermediate,AdvancedandExpert.Reference: References to other tasks.Link: Links to external resources.Contact: The person that can be contacted for further information about the task.
Enablement (Rust)¶
Tasks that are not directly related to nova-core, but are preconditions in terms of required APIs.
FromPrimitive API¶
Sometimes the need arises to convert a number to a value of an enum or a structure.
A good example from nova-core would be the Chipset enum type, which defines
the value AD102. When probing the GPU the value 0x192 can be read from a
certain register indication the chipset AD102. Hence, the enum value AD102
should be derived from the number 0x192. Currently, nova-core uses a custom
implementation (Chipset::from_u32 for this.
Instead, it would be desirable to have something like the FromPrimitive
trait [1] from the num crate.
Having this generalization also helps with implementing a generic macro that automatically generates the corresponding mappings between a value and a number.
Generic register abstraction¶
Work out how register constants and structures can be automatically generated through generalized macros.
Example:
register!(BOOT0, 0x0, u32, pci::Bar<SIZE>, Fields [
MINOR_REVISION(3:0, RO),
MAJOR_REVISION(7:4, RO),
REVISION(7:0, RO), // Virtual register combining major and minor rev.
])
This could expand to something like:
const BOOT0_OFFSET: usize = 0x00000000;
const BOOT0_MINOR_REVISION_SHIFT: u8 = 0;
const BOOT0_MINOR_REVISION_MASK: u32 = 0x0000000f;
const BOOT0_MAJOR_REVISION_SHIFT: u8 = 4;
const BOOT0_MAJOR_REVISION_MASK: u32 = 0x000000f0;
const BOOT0_REVISION_SHIFT: u8 = BOOT0_MINOR_REVISION_SHIFT;
const BOOT0_REVISION_MASK: u32 = BOOT0_MINOR_REVISION_MASK | BOOT0_MAJOR_REVISION_MASK;
struct Boot0(u32);
impl Boot0 {
#[inline]
fn read(bar: &RevocableGuard<'_, pci::Bar<SIZE>>) -> Self {
Self(bar.readl(BOOT0_OFFSET))
}
#[inline]
fn minor_revision(&self) -> u32 {
(self.0 & BOOT0_MINOR_REVISION_MASK) >> BOOT0_MINOR_REVISION_SHIFT
}
#[inline]
fn major_revision(&self) -> u32 {
(self.0 & BOOT0_MAJOR_REVISION_MASK) >> BOOT0_MAJOR_REVISION_SHIFT
}
#[inline]
fn revision(&self) -> u32 {
(self.0 & BOOT0_REVISION_MASK) >> BOOT0_REVISION_SHIFT
}
}
Usage:
let bar = bar.try_access().ok_or(ENXIO)?;
let boot0 = Boot0::read(&bar);
pr_info!("Revision: {}\n", boot0.revision());
Delay / Sleep abstractions¶
Rust abstractions for the kernel’s delay() and sleep() functions.
FUJITA Tomonori plans to work on abstractions for read_poll_timeout_atomic() (and friends) [1].
IRQ abstractions¶
Rust abstractions for IRQ handling.
There is active ongoing work from Daniel Almeida [1] for the “core” abstractions to request IRQs.
Besides optional review and testing work, the required pci::Device code
around those core abstractions needs to be worked out.
Page abstraction for foreign pages¶
Rust abstractions for pages not created by the Rust page abstraction without direct ownership.
There is active onging work from Abdiel Janulgue [1] and Lina [2].
Scatterlist / sg_table abstractions¶
Rust abstractions for scatterlist / sg_table.
There is preceding work from Abdiel Janulgue, which hasn’t made it to the mailing list yet.
ELF utils¶
Rust implementation of ELF header representation to retrieve section header tables, names, and data from an ELF-formatted images.
There is preceding work from Abdiel Janulgue, which hasn’t made it to the mailing list yet.
PCI MISC APIs¶
Extend the existing PCI device / driver abstractions by SR-IOV, config space, capability, MSI API abstractions.
Auxiliary bus abstractions¶
Rust abstraction for the auxiliary bus APIs.
This is needed to connect nova-core to the nova-drm driver.
Debugfs abstractions¶
Rust abstraction for debugfs APIs.
Vec extensions¶
Implement Vec::truncate and Vec::resize.
Currently this is used for some experimental code to parse the vBIOS.
GPU (general)¶
Parse firmware headers¶
Parse ELF headers from the firmware files loaded from the filesystem.
Build radix3 page table¶
Build the radix3 page table to map the firmware.
vBIOS support¶
Parse the vBIOS and probe the structures required for driver initialization.
Initial Devinit support¶
Implement BIOS Device Initialization, i.e. memory sizing, waiting, PLL configuration.
Boot Falcon controller¶
Infrastructure to load and execute falcon (sec2) firmware images; handle the GSP falcon processor and fwsec loading.
GPU Timer support¶
Support for the GPU’s internal timer peripheral.
MMU / PT management¶
Work out the architecture for MMU / page table management.
We need to consider that nova-drm will need rather fine-grained control, especially in terms of locking, in order to be able to implement asynchronous Vulkan queues.
While generally sharing the corresponding code is desirable, it needs to be evaluated how (and if at all) sharing the corresponding code is expedient.
VRAM memory allocator¶
Investigate options for a VRAM memory allocator.
- Some possible options:
Rust abstractions for - RB tree (interval tree) / drm_mm - maple_tree
native Rust collections
Instance Memory¶
Implement support for instmem (bar2) used to store page tables.
GPU System Processor (GSP)¶
Export GSP log buffers¶
Recent patches from Timur Tabi [1] added support to expose GSP-RM log buffers (even after failure to probe the driver) through debugfs.
This is also an interesting feature for nova-core, especially in the early days.
GSP firmware abstraction¶
The GSP-RM firmware API is unstable and may incompatibly change from version to version, in terms of data structures and semantics.
This problem is one of the big motivations for using Rust for nova-core, since it turns out that Rust’s procedural macro feature provides a rather elegant way to address this issue:
generate Rust structures from the C headers in a separate namespace per version
build abstraction structures (within a generic namespace) that implement the firmware interfaces; annotate the differences in implementation with version identifiers
use a procedural macro to generate the actual per version implementation out of this abstraction
instantiate the correct version type one on runtime (can be sure that all have the same interface because it’s defined by a common trait)
There is a PoC implementation of this pattern, in the context of the nova-core PoC driver.
This task aims at refining the feature and ideally generalize it, to be usable by other drivers as well.
GSP message queue¶
Implement low level GSP message queue (command, status) for communication between the kernel driver and GSP.
Bootstrap GSP¶
Call the boot firmware to boot the GSP processor; execute initial control messages.
Client / Device APIs¶
Implement the GSP message interface for client / device allocation and the corresponding client and device allocation APIs.
Bar PDE handling¶
Synchronize page table handling for BARs between the kernel driver and GSP.
FIFO engine¶
Implement support for the FIFO engine, i.e. the corresponding GSP message interface and provide an API for chid allocation and channel handling.
GR engine¶
Implement support for the graphics engine, i.e. the corresponding GSP message interface and provide an API for (golden) context creation and promotion.
CE engine¶
Implement support for the copy engine, i.e. the corresponding GSP message interface.
VFN IRQ controller¶
Support for the VFN interrupt controller.
External APIs¶
nova-core base API¶
Work out the common pieces of the API to connect 2nd level drivers, i.e. vGPU manager and nova-drm.
vGPU manager API¶
Work out the API parts required by the vGPU manager, which are not covered by the base API.
nova-core C API¶
Implement a C wrapper for the APIs required by the vGPU manager driver.
Testing¶
CI pipeline¶
Investigate option for continuous integration testing.
This can go from as simple as running KUnit tests over running (graphics) CTS to booting up (multiple) guest VMs to test VFIO use-cases.
It might also be worth to consider the introduction of a new test suite directly sitting on top of the uAPI for more targeted testing and debugging. There may be options for collaboration / shared code with the Mesa project.