-
05/10/2026, 09:57
-
Todd Kjos (Google)05/10/2026, 10:00
Android’s Generic Kernel Image (GKI) enforces a single binary kernel, restricting Android ecosystem partners from modifying core kernel code. To allow partner-specific optimizations, Google introduced "vendor hooks", based on Linux tracepoints, to act as in-kernel callback registration points. Partners use loadable kernel modules to register handlers for these hooks to implement...
Go to contribution page -
05/10/2026, 10:00
-
Kate Stewart (Linux Foundation), Philipp Ahmann (Etas GmbH (BOSCH))05/10/2026, 10:00
In regulated industries, Linux is widely used due to its strong software capabilities in areas such as dependability, reliability, and robustness. These industries follow best practices in terms of processes for requirements, design, verification, and change management. These processes are defined in standards that are typically not accessible to the open source kernel community.
However,...
Go to contribution page -
Gregory Price (Meta)05/10/2026, 10:05
Compressed RAM (where hardware offloads compression) presents a particularly novel problem for the kernel: the device fundamentally lies about its true capacity - while the kernel is written to assume any
struct pageit can get will always be backed by real capacity.Unlike zswap/zram - these devices provide cacheline/byte access to compressed memory, their memory can remain page-table...
Go to contribution page -
Mr Barry Song (Xiaomi Corporation), Mr Bo Zhang (Xiaomi Corporation), Mr Hongru Zhang (Xiaomi Corporation)05/10/2026, 10:15
Problem Statement
Android UI rendering is latency-sensitive — at 90Hz, each frame has only ~11ms time budget. When a UI-critical thread (e.g., RenderThread) is blocked in the kernel, the frame is likely to be dropped.
We profiled 40 popular Android applications on a Pixel 6 (kernel 6.18.0-mainline, 90Hz refresh rate), using ftrace lock_contention events correlated with Perfetto...
Go to contribution page -
Corinn Tiffany (Inria)05/10/2026, 10:15
XArray is a data structure used in many Linux kernel components, most notably the page cache. Its API contracts are not precisely documented, making it challenging to understand caller obligations and which invariants any changes to the implementation must maintain over the structure. Since its integration into the Linux source tree in 2019, errors in the use of the library have caused bugs...
Go to contribution page -
Rohan Tabish, Tengfei Fan05/10/2026, 10:30
The upstream Linux kernel explicitly excludes real-time (RT) tasks from the sched-ext extensible scheduler framework, restricting sched-ext BPF schedulers to only manage SCHED_NORMAL/SCHED_BATCH/SCHED_IDLE tasks. However, Android's production workloads present a fundamentally different reality: many performance-critical scenarios — including audio pipelines, camera capture, display...
Go to contribution page -
Arun George (Samsung Semiconductor)05/10/2026, 10:35
The PCIe Unordered I/O (UIO) feature (introduced in v6.1) relaxes the strict ordering rules of the PCIe fabric, providing benefits such as the avoidance of head-of-line (HOL) blocking. CXL v3.2 specification incorporates P2P UIO access into the HDM space, enabling the peer access from non-CXL capable accelerators (e.g., GPUs) over the PCIe bus.
Enabling UIO in the Linux kernel involves...
Go to contribution page -
Siddharth Nayyar (Google)05/10/2026, 10:45
Android partners have expressed significant interest in eBPF for a variety of purposes including system stability monitoring, performance monitoring, power consumption analysis, and customizable scheduling through sched_ext; however, providing an officially supported framework presents engineering challenges. Modern eBPF deployment requires CO-RE (Compile Once - Run Everywhere) support and...
Go to contribution page -
Igor Stoppa (nvidia)05/10/2026, 10:45
Safety-oriented use of the Linux Kernel presents a class of obstacles that are normally absent from other types of use, and therefore can be easily overlooked. Sometimes what would normally constitute a strength can actually turn into a weakness. Or aspects that are peculiar of creation of physical products (e.g. cars, robots) can present unexpected challenges.
Go to contribution page
This talk wants to raise... -
William McVicker05/10/2026, 11:00
Wattson is a trace based power estimation tool designed around perfetto to estimate CPU power consumption on ARM64 devices using a statistical per-SoC model. With support of both the Pixel 6 (gs101) and SM8750 upstream, you can now use the Wattson tool to detect CPU power regressions in the Linux kernel. This talk dives into how Google is using Wattson to catch CPU power regressions...
Go to contribution page -
Robert Richter (Advanced Micro Devices)05/10/2026, 11:05
The CXL specification defines a Component Performance Monitoring Unit (CPMU) register interface for performance monitoring of CXL devices. The Linux kernel includes a CPMU driver that exposes an interface to collect hardware events from CXL memory devices through the perf subsystem.
The current driver supports poll-based event counting using perf stat , providing events such as clock ticks,...
Go to contribution page -
George Chan (Google - Android Security), Neill Kapron (Google)05/10/2026, 11:15
The Android USB stack was originally architected around the constraints of early smartphones. Initially designed primarily for phones with a single USB Micro-B device port, the stack lacks the modern API surface required for advanced USB applications. While incremental changes have been implemented out of necessity, a larger refactoring is required to better support modern USB features like...
Go to contribution page -
Xirui Zhang, Yangtao Li05/10/2026, 12:00
The Android Super partition relies on static reserved space to guarantee OTA upgrade capability. However, this fixed allocation method possesses an inherent defect: if the reserved space is too large, it permanently occupies flash memory and cannot be utilized by the data partition; if it is too small, OTA upgrades will fail due to insufficient space. To address the industry pain points of...
Go to contribution page -
Bharata Bhasker Rao (AMD)05/10/2026, 12:00
Hardware platforms continue to expose useful and actionable memory access information to the OS in various ways. Sources of such information include CPU-level instruction/op sampling mechanisms (like AMD IBS and ARM SPE), PMU-based precise sampling (like Intel PEBS), and device-side facilities such as the CXL Hotness Monitoring Unit (HMU). These platform-provided hints can be used by...
Go to contribution page -
Chuck Wolber05/10/2026, 12:00
The fundamental unit of design is a requirement (i.e. "testable expectation"). All forms of design can be expressed as a (directed acyclic) knowledge graph of requirements. A software project that documents its design in this manner can derive both source code and automated test from the same idea. Without this, there is no guarantee that test and implementation reliably reflects the same...
Go to contribution page -
Daniel Zheng05/10/2026, 12:15
Hi I'm here to discuss the developments in android GBL + CF support, and talk about android dynamic partitions 2.0 feature (resizable super partition) to accommodate large OS updates.
- Quick GBL + Cuttlefish recap
- Cuttlefish default booting off GBL
- New android_esp partition
- Fastbootd deprecation
- u-boot implementation
Android Dynamic Partitions 2.0 allow for dynamic...
Go to contribution page -
SJ Park05/10/2026, 12:25
In the last LPC, we introduced a plan to extend DAMON (Data Access MONitor) for migrating pages around NUMA nodes based on their access pattern. Based on on/offline feedback, we continued discussions and development in the upstream community.
As a result of the collaborations, we made a concrete plan and a roadmap for the goal, including support of extensions for h/w features such as AMD...
Go to contribution page -
Naina Mehta05/10/2026, 12:30
Bootloaders play a vital role in the Android boot process, but the ecosystem has long been fragmented across silicon vendors and OEM-specific implementations. To address this, Google introduced the Generic Boot Loader (GBL), a Rust-based EFI application in AOSP, with the goal of standardizing Android boot logic.
Go to contribution page
This session focuses on how Qualcomm is adapting its boot chain to integrate GBL... -
Gabriele Paoloni (Red Hat), Kate Stewart (Linux Foundation)05/10/2026, 12:30
Following the [objections][1] in having requirements and even code documentation traceable to Kernel testing as optional part of the Linux Kernel development process, the ELISA project decided to start defining requirements and test specifications in a separate repository.
Go to contribution page
This session will present the current status for the requirements and test specifications framework and traceability to... -
Juan Yescas (Google), Kalesh Singh (Google)05/10/2026, 12:45
With the release of Android 17, partners are required to support the 16 KB developer option on devices meeting specific hardware requirements, such as CPU compatibility and memory configurations exceeding 8 GiB. While this transition significantly improves system performance and unlocks hardware efficiencies, Android partners frequently observe a noticeable memory footprint increase,...
Go to contribution page -
Yifan Qiao05/10/2026, 12:50
Cross-node Memory as a Linux Storage Tier：Exploring POSIX-based Shared Memory
Background & Motivation
Memory-semantic interconnects such as CXL 3.0 and Huawei United Bus make remote memory directly addressable. This raises a question for Linux: should cross-node memory become another storage tier that can be exposed through existing POSIX filesystem interfaces?**Our...
Go to contribution page -
Barry Song, Bo Zhang (Xiaomi Corporation), nanzhe zhao (Xiaomi Corporation)05/10/2026, 13:00
This topic proposes exploring the possibility of using 16 KB for both
page cache and mTHP on Android.Collaborating with Kalesh Singh, Ryan Roberts, David Hildenbrand and
others, Xiaomi is exploring the use of 16 KB large folios for both page
cache and anonymous memory.We have posted an RFC patchset for large folio support in F2FS, which
Go to contribution page
has been working well on Android devices so... -
Nicole Pappler05/10/2026, 13:00
A safety case is the structured argument that a system is acceptably safe: claims, the evidence supporting them, and the assumptions under which the argument holds. Building and maintaining one is largely manual, and keeping it consistent as a design evolves is harder still.
Go to contribution page
SPDX 3.1's Functional Safety profile changes the starting point by giving the safety case a machine-readable form. It... -
Mr Cong Wang (Multikernel Technologies)05/10/2026, 13:10
When multiple kernels or CXL-connected hosts share byte-addressable memory, every existing filesystem option pays a copy per participant: tmpfs replicates content N times, erofs and fscache keep a private page cache per kernel. To ground the discussion we bring DAXFS, a prototype filesystem that runs directly on DAX memory with no block layer: one shared namespace, a cooperative page cache in...
Go to contribution page -
Sungho Bae (LG Electronics)05/10/2026, 13:15
Background
Automotive and embedded virtualization stacks increasingly run Android(AAOS) or Linux as a GuestVM that needs access to platform infrastructure -- clocks and regulators -- managed by a host or
Go to contribution page
hypervisor. The upstream Linux kernel provides a complete guest-side solution for this via SCMI-over-virtio:clk-scmi(upstream since v4.17),scmi-regulator, and the SCMI virtio... -
Kate Stewart (Linux Foundation), Philipp Ahmann (Etas GmbH (BOSCH))05/10/2026, 13:25
-
Will Deacon05/10/2026, 15:00
There have been a bunch of attempts [1] to reduce the memory consumed by kernel stacks for x86 and arm64, largely based around the idea of dynamically growing the kernel stack allocation based on page faults. This poses what appear to be insurmountable challenges, as it introduces complexity into the architecture exception entry code (which needs to be able to transition cleanly to a new...
Go to contribution page -
Ignat Korchagin (Citadel)05/10/2026, 15:00
Linux Crypto API has recently come under fire due to a series of discovered vulnerabilities, like [Copy Fail][1] and friends. This resulted in a drastic response from some maintainers: deprecation of the [Linux Crypto API userspace interface][2]. However, it feels like cracking a nut with a sledgehammer, as some vulnerabilities, like [Dirty Frag][3], do not even use the userspace interface...
Go to contribution page -
Muhammad Usama Sardar (TU Dresden)05/10/2026, 15:25
Abstract:
Go to contribution page
This talk is a follow-up of LPC'25, where we introduced the security problem to the community for the suitable approach of attested TLS protocols. We have defended our position (cf. [expat BoF][1]) to standardize the attested TLS protocol in the [IETF][2], and a new Working Group named [Secure Evidence and Attestation Transport (SEAT)][3] has been formed to exclusively tackle... -
Kairui Song (Tencent)05/10/2026, 15:30
When handling swap page faults, the kernel often don't reads just a single page. For legacy HDDs, an entire cluster is read in. For SSDs, we check the VMA and page tables to see if nearby pages are likely to be needed soon, using a basic statistic-driven heuristic. For compressed RAM (like zram, and potentially soon zswap), traditional readahead is skipped entirely. Meanwhile, enabling (m)THP...
Go to contribution page -
Hongming Qiu (University of Illinois Urbana-Champaign)05/10/2026, 15:45
eBPF programs enter the kernel as privileged extensions and, once admitted, become part of the system’s trusted computing base. Prior LPC discussions established BPF signing as a way to track the provenance of these programs, while deliberately separating signature verification from the policy that consumes it [1,2]. IMA was identified as one possible consumer through LSM integration, but its...
Go to contribution page -
Albert Esteve (Red Hat), T.J. Mercier (Google)05/10/2026, 15:50
On embedded and automotive Linux systems, a single daemon often allocates DMA-buf memory on behalf of other clients. Today, most of that memory is invisible to cgroup accounting, only system-heap buffers can carry a charge via __GFP_ACCOUNT, and even then it lands on the allocator’s cgroup rather than the app that requested the buffer.
The misattribution has real consequences on any system...
Go to contribution page -
Matthew Wilcox (Oracle)05/10/2026, 16:10
In 2023 we introduced per-VMA locks to solve contention and priority inversion on the mmap_lock for multithreaded programs. While successful, the initial implementation did not solve every case of contention and some workloads can still demonstrate problems. This session will discuss ways of fixing the remaining problems.
Go to contribution page -
Nandakumar Raghavan05/10/2026, 16:10
Linux has no standard model for provisioning and unlocking encrypted persistent storage at boot in environments where the underlying platform cannot be fully trusted. Today, every deployment stack solves this independently: custom boot agents, post-provisioning scripts, and platform-specific unlock logic. The mechanism exists — LUKS2 tokens and the cryptsetup plugin interface — but the...
Go to contribution page -
Kevin Brodsky (Arm)05/10/2026, 17:00
On supported configurations, the direct map is built using large
PMD/PUD-level block mappings. This is expected to bring many of the
benefits of hugepages: improved TLB hit rate, less page table walking,
smaller page table memory footprint.This optimisation is most effective when the direct map gives access to
Go to contribution page
the entire physical memory with uniform permissions. Unfortunately,... -
Sherif Nagy05/10/2026, 17:00
This talk walks through the end-to-end process for Linux distributions to have their SHIM submitted for review and eventual signing by Microsoft, surfacing the challenges faced by both distribution teams and the SHIM review team.
We examine this process in depth from dual vantage points: distribution maintainers navigating submission requirements -- including SBAT entries, CVE patching, DBX...
Go to contribution page -
Anushka Nabar (Qualcomm)05/10/2026, 17:25
ARM SystemReady defines a standard firmware-to-OS boot path via UEFI, but provides no standard mechanism for booting Type 1 hypervisors such as Gunyah or Xen. Platforms relying on Type 1 hypervisors to isolate security- or latency-sensitive workloads, lack a standardized boot flow, which creates fragmentation across mobile, IoT, and compute ecosystems.
We have implemented a solution for...
Go to contribution page -
Shivank Garg (AMD), Zi Yan (NVIDIA)05/10/2026, 17:30
As the memory hierarchy deepens at both ends, with HBM adding a faster tier on top and CXL adding cheaper, slower capacity below, keeping hot data in the fast tier and shedding cold data downward makes page migration central to NUMA, tiered-memory and coherent CPU-GPU systems (where device memory is exposed as NUMA nodes).
Profiling move_pages(2) shows the folio copy dominates (~97% of...
Go to contribution page -
Yi-Yo Chiang (Google)05/10/2026, 17:45
Android is evaluating the Linux EFI boot stub to standardize OS handoff and reduce bootloader feature duplication. We examine the architectural blockers that arise when dealing with strict embedded hardware constraints, aiming to brainstorm solutions.
Topics for Discussion:
-
EL2 Elevation and KVM within an EFI context
- The Problem: KVM requires booting the kernel at EL2....
-
-
Shakeel Butt05/10/2026, 18:00
On a densely shared host, a routine event breaks tenant isolation: a task holding a shared kernel lock (filesystem metadata, a control-plane mutex/rwsem) allocates inside the critical section, the allocation falls into memory reclaim, and until reclaim finishes every other task waiting on that lock — from any cgroup — pays the stall. Shared kernel locks aren't mediated by cgroups or memcg...
Go to contribution page -
Piotr Król (3mdeb)05/10/2026, 18:10
Arm's DRTM architecture (DEN 0113) defines a dynamic root of trust for measurement: a DCE-Preamble triggers a dynamic launch event, EL3 firmware (TF-A) measures a protected payload into a fresh chain of trust, and the dynamically launched measured environment (DLME) continues under a smaller TCB. Yet a working implementation exists only against the Base AEM FVP TF-A's plat_drtm hooks...
Go to contribution page -
Neil Armstrong (Linaro)06/10/2026, 10:00
Since early 2024, U-Boot has been synchronizing the DTS and bindings of each Linux release into the U-Boot source tree using git subtree functionality. Since this transition, some platforms like Amlogic or Qualcomm have immediately switched, and some older platforms have been actively migrating to upstream Linux DT sources and bindings while maintaining minimal local U-Boot DTS...
Go to contribution page -
Krzysztof Kozlowski (Qualcomm)06/10/2026, 10:20
The great benefit of Devicetree bindings in the current DT schema format is the ability to validate the correctness of DTS (Devicetree sources) against those bindings. However, once validation was introduced, we discovered that many in-kernel DTS files simply did not pass.
Continuing such summary from 2025, what is the status of dtbs_check now? Which platforms have the most warnings and...
Go to contribution page -
Srini Kandagatla06/10/2026, 10:45
Last year's LPC discussion explored whether ACPI-defined hardware descriptions could be reused on systems booting with Devicetree, and where the boundary should exist between the two firmware ecosystems.
Since then, several related efforts have continued across the kernel community, having intermediate representation for MIPI DISCO tables for SDCA, emerging ACPI-DT hybrid approaches. At the...
Go to contribution page -
Amit Kucheria06/10/2026, 11:10
Corporate adoption of an "upstream-first" strategy is gaining traction, with companies increasingly willing to allocate engineering bandwidth to contribute hardware support directly to the Linux kernel. However, integrating these contributions smoothly remains a practical challenge. The review process frequently experiences friction during Device Tree (DT) binding discussions, which can extend...
Go to contribution page -
Hervé Codina06/10/2026, 12:00
Device Tree has been extremely successful at describing non-discoverable hardware in Linux and other embedded systems. However, it remains fundamentally monolithic: each Device Tree describes a complete system, and reuse across independently developed hardware components is limited.
This becomes problematic for modular platforms where expansion boards, mezzanines, daughter cards, or...
Go to contribution page -
Mathieu Desnoyers (EfficiOS Inc.)06/10/2026, 12:00
The current situation regarding LTTng vs upstream Linux:
1) There are maintainers who push for everything to be in tree
2) There are maintainers who are proponents for no-GPL-export when there are no in-tree users
3) Most of the tracer common facilities are used by tracers which do not compile as modules (only builtin)
4) Linus Torvalds stated that LTTng will stay out of treeAs a...
Go to contribution page -
Doug Anderson06/10/2026, 12:30
It is commonplace that many boards in the real world have many sibling or cousin boards that are 95-99% the same as each other. Some examples:
- During development, most boards go through several revisions. A board might have proto0, proto1, evt0, evt1, evt1.1, dvt1, pvt, and mp revisions. These revisions almost the same with just small changes. While only "mp" (mass production) devices...
-
Agathe Porte (Qualcomm), Hans de Goede (Qualcomm)06/10/2026, 13:00
SBCs like the Arduino UNO Q can have a number of extension boards, like the UNO Media Carrier or an Arduino shield connected. On top of this extra hardware may be connected through e.g. CSI camera connectors and DSI display connectors.
Each of these possible hardware addons needs a DT overlay to work. This requires some method for the user to select which DT overlays to use.
There have...
Go to contribution page -
Dr Daniel Lezcano (Qualcomm)06/10/2026, 15:00
The Linux thermal framework has proven to be flexible and robust over the years. However, some aspects of its event handling have become increasingly difficult to reason about, resulting in inconsistent behaviors and corner cases.
Examples include trip point updates while the temperature has already fallen within the hysteresis range after the notification was generated, inconsistent...
Go to contribution page -
Dr Daniel Lezcano (Qualcomm)06/10/2026, 15:20
The Linux thermal management and power capping frameworks currently evolve independently, despite relying on the same Energy Model (EM) to describe the power-performance characteristics of devices.
The thermal framework regulates temperature by estimating a sustainable power budget using the power_allocator governor. A PID control loop computes the power reduction required to maintain a...
Go to contribution page -
Srinivas Pandruvada06/10/2026, 15:40
Modern System-on-Chip designs increasingly incorporate built-in hardware thermal controllers to manage thermal conditions efficiently. Intel platforms, beginning with the Lunar Lake generation, feature integrated platform temperature controllers capable of autonomous thermal management. However, not all platform designs directly interface temperature readings and thermal thresholds with these...
Go to contribution page -
Jie Zhan (HiSilicon)06/10/2026, 16:00
SoC uncore components, such as interconnects, system-level caches, and memory controllers, can account for a substantial share of package power, and their operating frequency bounds the achievable bandwidth and latency. Core DVFS is well supported by cpufreq, but there is no generic upstream mechanism for uncore DVFS - a gap felt most on server platforms. We propose building uncore DVFS on top...
Go to contribution page -
Sumit Gupta06/10/2026, 16:45
ACPI CPPC "autonomous selection" lets the platform pick the CPU performance level itself, within OS-provided min/max bounds and guided by an Energy Performance Preference (EPP) hint. Today cppc_cpufreq exposes this as a per-policy auto_select sysfs toggle layered on top of whatever scaling governor is attached. The result is confusing: once autonomous mode is on, the attached governor...
Go to contribution page -
Samuel Wu (Google)06/10/2026, 17:05
Transitioning a CPU into and out of idle has a non-negligible energy overhead. This "wakeup tax" is frequently triggered by background tasks with low utilization but a high number of wakeups. Furthermore, these tasks largely escape detection from existing energy-aware mechanisms like PELT and EAS, which are optimized for continuous execution rather than transient hardware states.
This talk...
Go to contribution page -
Mr Brian Masney06/10/2026, 17:25
At last year's Linux Plumbers Conference, we had some great discussions about how to fix clock tree propagation in the Common Clk Framework (https://lpc.events/event/19/contributions/2152/). Taking that feedback into account, a v8 patch set has been posted that solves the problem in a simple manner.
https://lore.kernel.org/linux-clk/20260327-clk-scaling-v8-0-86cd0aba3c5f@redhat.com/
The...
Go to contribution page -
Ricardo Neri (Intel Corporation)06/10/2026, 17:50
The scheduler's task wake-up logic and capacity-aware load balancing rely on arch_scale_cpu_capacity() to determine how much work a CPU can absorb. It also has logic to account for the effects of transient thermal- and power-driven capacity loss. This mechanism, known as hardware pressure, is currently not used on x86: arch_scale_cpu_capacity() returns a fixed constant on non-hybrid systems,...
Go to contribution page -
Aiqun Yu (Qualcomm), Mr Cong Zhang (Qualcomm)06/10/2026, 18:10
Benefits of Accurate Exit Latency can have:
More Accurate hrtimer Expiration
Better CPU Idle level Selection
Improved Support for Latency-Sensitive SystemsCpu different low power state can have different exit latency. And the exit latency may be affected by:
- current cpu frequency
- Different firmware version
- Different hardware difference and etc.
So...
Go to contribution page -
Michal Koutný (SUSE)07/10/2026, 10:00
Triggered by:
Subject: [PATCH 0/4] bpf: add a few hooks for sandboxing
Message-Id: 20260220-work-bpf-namespace-v1-0-866207db7b83@kernel.orgProblem statements:
Go to contribution page
- Users (admins) are sometimes confused by some entity (PAM, systemd, container
runtimes) migrating their processes away from intended cgroup.
- Coarse-grained DAC doesn't express well who (migrating process) can operate
... -
Dr Gary Guo (Red Hat)07/10/2026, 10:00
Self-reference is a common need in kernel code. In fact, this is what motivates the development of
Go to contribution pagepin-init. So far, self-references can only be created with unsafe code with explicit use ofOpaque. This is a discussion about on-going working to support safe creation of self references in thepin-initcrate. -
Jori Koolstra (N/A)07/10/2026, 10:20
For quite a while there has been a wish from container runtime to be able to restrict how we can reuse a particular file descriptor. For instance, CVE-2019-5736 showcased a privilege escalation in runc, whereby the possibility of reopening
Go to contribution page/proc/self/exeas writeable allowed a malicious image to overwrite the runc binary. That was patched on the user space side by copying runc to a sealed... -
Mr Andreas Hindborg (Samsung)07/10/2026, 10:20
The
kernel::block::mq::Requesttype [1] sits on the I/O hot path of every Rust block device driver. ARequestis jointly referenced by the block layer and the driver, with completion arriving on multiple asynchronous paths, so the type has to encode a non-trivial sharing and lifecycle model with minimal runtime cost.The introduction of
Go to contribution pageOwnable[2] gave us a general mechanism for... -
Shailja Shaktawat07/10/2026, 10:40
CRIU’s incremental checkpointing is being used for forensic container snapshot(Stoyanov et al., DFRWS 2026) chains. Soft-dirty tracking cuts snapshot size by about 10× and makes high-frequency capture practical. Live migration only needs a correct final state. Forensics needs the path that led there. Soft-dirty was built for migration and is now being reused for forensics.
A forensic...
Go to contribution page -
Philipp Stanner07/10/2026, 10:40
The kernel's dma_fence subsystem lays at the heart of every graphics processing unit (GPU) driver. It is a primitive for synchronizing the state of jobs running on GPUs with receiver parties, notably userspace. A number of circumstances make the correct implementation and usage of both C and Rust dma_fence very challenging:
- The highly asynchronous nature of GPUs, including the fact that...
-
Andrei Vagin07/10/2026, 11:00
Checkpoint/Restore (C/R) is increasingly used for both startup acceleration (restoring pre-warmed snapshot instances on demand) and live migration. However, deploying static snapshots or migrating tasks across heterogeneous clusters creates severe runtime bottlenecks when source and target nodes possess differing CPU capabilities. While CRIU and container runtimes can accurately preserve...
Go to contribution page -
Daniel Almeida (Collabora)07/10/2026, 11:00
Briefly cover the status of the Tyr project and discuss the current blockers in upstream, specially those related to missing Rust abstractions. This presentation intends to discuss and validate the job submission model, including the proposed GPUVM/JobQueue Rust abstractions and their current upstream status, showcasing the different designs between Tyr's initial implementation and what is...
Go to contribution page -
Radostin Stoyanov (University of Oxford)07/10/2026, 12:00
With the increased adoption of AI workloads, efficient GPU checkpointing mechanisms are becoming crucial for inference, training, fine-tuning, and reinforcement learning workloads. One of the key challenges with GPU checkpointing today is the lack of memory-tracking support that enables incremental snapshots. When the GPU state is checkpointed into host memory, all pages appear modified,...
Go to contribution page -
Michał Wilczyński07/10/2026, 12:00
Problem Statement:
Independent developers driving new Rust bindings often face a major bottleneck: getting their work mainlined by hesitant C subsystem maintainers, and just as importantly, sustaining that collaboration post-merge. Translating modern Rust architectures to maintainers who evaluate designs strictly through C paradigms remains a massive hurdle.Session Focus:
Go to contribution page
The PWM... -
Pavel Tikhomirov07/10/2026, 12:20
After moving OpenVZ containers to cgroup-v2 we are struggling a bit to reach
feature parity with what we had before. One such feature is running nested
Docker containers inside an OpenVZ (system) container — part of making our
containers behave as close to a regular server as possible.In cgroup-v2 the device controller was reformed drastically: device
Go to contribution page
availability can only be... -
Alice Ryhl (Google)07/10/2026, 12:20
Rust is expanding into more and more places, and it's becoming clear that Rust creates some unique challenges when it comes to drivers that are out-of-tree.
Like all other Rust drivers, out-of-tree drivers written in Rust require abstractions for the subsystems they interact with. If the driver requires a subsystem that does not yet have abstractions, or if the abstractions exist but are...
Go to contribution page -
Andrei Zhadchenko (Virtuozzo)07/10/2026, 12:40
Container storage commonly relies on directory overlays, filesystem-native subvolumes, or thin-provisioned block devices. We will explore another approach: exposing QCOW2 images directly as Linux block devices through a device-mapper target. QCOW2 is the standard virtual-disk format across much of the QEMU/KVM ecosystem. Its widespread adoption, mature tooling, and features such as...
Go to contribution page -
Michal Rostecki (Anza)07/10/2026, 12:40
Writing BPF programs in the long past meant wrestling with Linux kernel version fragmentation. That problem was solved, many years ago, thanks to CO-RE (Compile Once, Run Everywhere) relocations. CO-RE is a mechanism that uses the BTF type format and its relocation entries (
Go to contribution pageBTF.ext) to handle layout differences, by patching the loaded BPF bytecode with correct offsets that match the running... -
Chen-Yu Tsai (Google, LLC)07/10/2026, 15:00
On x86 / ACPI platforms, devices on enumerable busses can normally be seen directly by the OS. On device tree platforms, these devices sometimes require extra power sequencing like toggling regulator supplies or GPIO lines. Over the years most of these cases have been solved, but there are still some gaps.
As of kernel version v7.0, support for power sequencing generic PCI devices, ones...
Go to contribution page -
Petr Mladek (SUSE)07/10/2026, 15:00
Kernel livepatches are kernel modules which are able to modify the kernel behavior by redirecting kernel functions, calling pre/post patch callbacks, and allocating shadow variables.
The interface between the kernel and the kernel livepatch module is defined in
include/linux/livepatch.h.The API has evolved over the years. But it has stayed backward compatible since the commit...
Go to contribution page -
07/10/2026, 15:00
-
Josh Don (Google), Mr Vineeth Remanan Pillai (Google)07/10/2026, 15:10
As production workloads increasingly transition to virtual machines for security isolation and resource consolidation in multi-tenant environments, traditional CPU scheduling faces a critical M:N preemption challenge. The host operating system schedules opaque virtual CPUs rather than the actual workload threads. Consequently, the host scheduler remains blind to the varying priorities and...
Go to contribution page -
Bartosz Golaszewski (Qualcomm)07/10/2026, 15:25
Certain critical subsystems - clocks, timers and interrupt controllers - sometimes need to be initialized before driver core is made available in driver_init(). To that end, we provide a set of macros: IRQCHIP_DECLARE(), CLK_OF_DECLARE(), TIMER_OF_DECLARE() which allow the kernel to call initialization functions based on compatibles either before reaching the point where actual platform...
Go to contribution page -
Emil Tsalapatis (Meta Platforms)07/10/2026, 15:28
All sched_ext schedulers currently use kfuncs to manage their idle cpumask using a hardcoded policy provided by the kernel. This lack of configurability of the current cpumask requires us to add policy through explicit masking operations directly in the scheduler code. This in turn leads to duplicating idle CPU selection logic across schedulers as it is difficult to factor it out.
This...
Go to contribution page -
Yafang Shao07/10/2026, 15:30
My employer relies heavily on livepatch to rapidly experiment with new kernel features without interrupting production workloads. Our use cases include:
- Case 1: Deploying a livepatch function as a stable BPF hook.
For example, some proposals for such a use case has already been submitted upstream but has not yet been accepted:
https://lwn.net/Articles/1054030/
...
- Case 1: Deploying a livepatch function as a stable BPF hook.
-
Changwoo Min (Igalia)07/10/2026, 15:46
Preempting a lock holder — or failing to promptly schedule a just-woken
Go to contribution page
lock waiter — extends the serialized critical section and produces severe
tail-latency (P99) spikes: degraded server throughput, frame-time
spikes and dropped frames in games. Applications hit this on both
kernel-space locks and user-space primitives backed by futexes and SysV
semaphores. Existing techniques help but... -
Ulf Hansson (Qualcomm)07/10/2026, 15:50
At last LPC in Tokyo we discussed about the limitations of the sync_state support that quite recently was added to the generic PM domain (genpd) subsystem. The conclusion was to mainly focus on making it more fine grained, as this should address most of the problems. Attempts to implement this has been submitted to LKML [1]. Discussion and iterations of the series are moving forward, but a...
Go to contribution page -
Yi Zhu (Google)07/10/2026, 16:00
Abstract
Go to contribution page
Large Linux fleets increasingly depend on always-on observability: BPF programs, ftrace, kprobes, kretprobes, and continuous profiling agents are part of the core production control plane. Kernel livepatching depends on some of the same low-level mechanisms, especially dynamic ftrace-based redirection at function entry. In large production environments, we routinely observe fleet... -
Andrea Righi (NVIDIA)07/10/2026, 16:04
Proxy execution allows a waiting task (the "donor") to donate its execution context to a mutex owner, enabling the owner to continue running while the donor remains eligible on the runqueue.
Today, proxy execution and sched_ext are mutually exclusive build-time options: a kernel cannot be built with both CONFIG_SCHED_PROXY_EXEC=y and CONFIG_SCHED_CLASS_EXT=y.
This limitation is...
Go to contribution page -
Thomas Weißschuh (Linutronix)07/10/2026, 16:15
Sysfs attributes are used throughout the kernel to implement UAPI.
Subsystems either use common attributes, likekobj_attributeanddevice_attror define their own wrapper structures.
These structures are only descriptors defining the behavior of an attribute and normally never change.Historically the attribute however are not marked as
Go to contribution pageconstand could be modified through their... -
Dylan Hatch07/10/2026, 17:00
The Livepatch consistency model [1] requires the kernel to provide reliable stacktrace in order to be fully supported. On x86, the ORC unwinder provides these reliable stacktraces. However, arm64 misses the required support from objtool: it cannot generate ORC unwind tables for arm64. Prior RFCs have proposed to add this support to objtool, but feedback from the upstream community has...
Go to contribution page -
Gavin Guo07/10/2026, 17:00
Work-conserving schedulers prefer running tasks on idle CPUs
Go to contribution page
immediately, ensuring no processing capacity is wasted while work is
waiting. In the lavd select_cpu process, when a task wakes, the
scheduler will do its best to seek an idle core and run the task over
there. However, this idle-oriented CPU selection generally prioritizes
idle cores over the cache-warm cores, leading to more... -
AngeloGioacchino Del Regno (Collabora Ltd.), Sebastian Reichel (Collabora)07/10/2026, 17:10
We are seeing hard to solve cross-dependencies between different SoC subsystems (Rockchip, MediaTek, etc.). For example a power domain needing an I2C regulator, but the I2C regulator needing the I2C bus and the I2C bus driver needing a (different) power domain. This creates a cyclic dependency, since the power domains (or clocks) are usually all behind a single device.
Go to contribution page -
Srinivas Pandruvada07/10/2026, 17:18
This presentation explores how Intel HFI can be integrated with a sched_ext to improve task placement and power-performance efficiency on hybrid Intel systems. HFI provides real-time hardware guidance on which CPUs are better suited for performance- or efficiency-oriented work, or which to avoid, while sched_ext like LAVD supplies an adaptive scheduling framework capable of using that guidance...
Go to contribution page -
dongtai guo07/10/2026, 17:30
A series adding LoongArch support to objtool's
Go to contribution pageklp diffsubcommand (the
diffing engine klp-build invokes to generate a patch module) is under
review (v4: ... -
Pravin Kumar Ravi (Qualcomm Innovation Center, Inc.)07/10/2026, 17:35
Abstract
Modern SoCs increasingly run parts of a single pipeline (AI/ML,
Go to contribution page
vision, camera, graphics, sensors) across a mix of Linux drivers
and firmwares on remote processors (NPUs and AI processors, ISPs,
companion cores). Coordinating that pipeline requires
synchronization objects that can be created, synchronously or
asynchronously waited on, signaled, and released by... -
Balbir Singh, Lee Trager (NVIDIA)07/10/2026, 17:36
Proposal
On modern multi-socket, multi-GPU systems, application performance is often limited not by compute availability but by poor CPU/GPU locality. Today, customers are frequently instructed to rely on strict node pinning (numactl) and disabling NUMA balancing in order to avoid costly cross-node memory accesses. While effective in some cases, this approach can be suboptimal, since it...
Go to contribution page -
Lorenzo Pieralisi07/10/2026, 18:00
In ACPI based system,devices can be created out of ACPI static tables entries (eg ARM64 IORT, GTDT). For those devices, the GSI HW interrupt number is retrieved by reading table specific fields that are different for different static tables. Devices created out of static ACPI tables might be created before the interrupt controller drivers their GSI interrupt is routed to is probed, which...
Go to contribution page -
Joe Lawrence (Red Hat), Song Liu (Meta)07/10/2026, 18:00
Abstract
With klp-build now merged into mainline, establishing an automated test
Go to contribution page
suite is the logical next step. Historically, maintenance of
kpatch-build, a similar livepatching creation tool, has shown that the
object diff and correlation layer accounts for the vast majority of
regressions. Variations across compiler versions, optimization levels,
LTO modes, CFI, and... -
07/10/2026, 18:02
-
Chris Mason (Meta), Josef Bacik (Anthropic), Roman Gushchin (Google)
Overview
AI coding tools (LLMs, code assistants, AI agents) are rapidly becoming part of the developer workflow across the software industry. Open source communities are beginning to grapple with how these tools intersect with their development processes — from code generation and review assistance to documentation, debugging, and large-scale refactoring. This microconference will bring...
Go to contribution page -
John Stultz (Google), Karim Yaghmour (Opersys inc.), Sumit Semwal (Linaro)
The Android Micro Conference brings the upstream community and Android systems developers together to discuss issues and changes to the Android platform and their dependencies and interactions with the Linux kernel, allowing for collaboration on solutions for upstream.
Some highlights of progress made since last year’s MC:
- On 16k kernels, a set of recommendations were put together...
-
Pravin Kumar Ravi (Qualcomm Innovation Center, Inc.)
Abstract
Android platform pipelines (camera, video, graphics, XR and AI) on
Go to contribution page
modern SoCs routinely span Linux drivers and firmware running on
DSPs, ISPs, NPUs, and other remote processors.dma_fenceand
sync_filework well when a fence's state and callbacks are owned
by Linux kernel participants, but don't natively support a fence
that a remote, non-Linux core needs to create,... -
Omar Sandoval
Breakpoint support for drgn is currently underway (https://github.com/osandov/drgn/issues/626). Support is planned for:
- KGDB
- Linux kernel QEMU guests
- Live kernels in production (a sequel to my 2023 LPC session).
- Userspace processes (ptrace)
Each of these targets has its challenges and deficiencies. I will discuss these problems as well as next steps.
Go to contribution page -
Behan Webster (Linaro), Philip Balister (OpenEmbedded)
The Linux ecosystem supports a diverse set of methods for assembling complete, bootable systems—ranging from binary distributions to source-based systems, embedded platforms, and container-native environments. Despite differences in tooling and architecture, all of these systems face shared challenges: managing build complexity, ensuring security and reproducibility, maintaining cross-platform...
Go to contribution page -
Joshua Lilly (Meta)
A build is bitwise reproducible when compiling the same source with the same configuration and toolchain yields byte-for-byte identical output — an identical vmlinux and bzImage, verifiable by a simple sha256sum. For a normal kernel this is a hygiene property; for a Trusted Execution Environment it is foundational. A platform that measures the code it boots and reports a cryptographic hash is...
Go to contribution page -
Denver Gingerich (Software Freedom Conservancy)
OpenWrt has been fully reproducible for a few months now, the culmination of many years of work to achieve this important milestone. In this talk we'll discuss how we got here, what it took, and tips for other build systems that are looking for the same, including how to handle the unique challenges of reproducibility across multiple cross-compilation targets.
We'll also go into some of...
Go to contribution page -
Khem Raj (Qualcomm)
Most of Linux distros who follow time based releases, do have LTS release policy e.g. Ubuntu, Yocto, Debian, buildroot to name a few, and then there are rolling releases like archlinux and its family of distros. This talk is to discuss the LTS in the wake of genAI coding agents. There is a fair bit of coding agents at work for yocto project and other distributions doing different functions...
Go to contribution page -
286. The last step to secure reproducible distribution kernels: Hash-based module integrity checkingThomas Weißschuh (Linutronix)
The kernels current module signature scheme does not work well together with reproducible builds. If the key is generated at build-time the build is not reproducible. A static key that is known to the public does not provide security, but a static key not known to the public does prevent public rebuilds of the kernel for validation purposes.
Currently distributions need to make a...
Go to contribution page -
Alejandro Hernandez Samaniego
Modern embedded Linux build systems such as Yocto and Buildroot rely on complex pipelines that reuse intermediate artifacts and external inputs. While this improves performance and reproducibility, it also creates opportunities for supply chain attacks that are difficult to detect.
This talk demonstrates practical attack vectors targeting build systems at different stages of the pipeline....
Go to contribution page -
Krish Pandya (Undergraduate Researcher)
Sugar has been in tree since April 2006. Its last toolkit transition, GTK2 to GTK3, ran from October 2011 to the 0.98 release in November 2012. The current one, GTK3 to GTK4 and X11 to Wayland, is in its second year across twelve repositories. I ported the toolkit and presented that work at GNOME Asia Summit 2025; this year I mentor the two contributors...
Go to contribution page -
Dhaval Giani, Joerg Roedel (AMD)
Confidential Computing MC
Over the last few years, the Confidential Computing microconferences at LPC have been a key driver in advancing support for trusted execution workloads across the Linux virtualization and software ecosystem.
As a result of the previous confidential computing microconference, the following major features were merged:
- SEV-SNP support
- TDX support
-...
-
Mathias Brossard (Arm)
Arm is developing Live Migration ABIs for the Arm Confidential Compute Architecture (CCA), with input and requirements from ecosystem partners. The ABIs are provided by the Realm Management Monitor (RMM), the trusted firmware component responsible for managing Realms.
The presentation will start with a short overview of the high-level CCA Live Migration design and the end-to-end process. It...
Go to contribution page -
Ruoqing He (LingCage), Mr Xiaoxia Cui (Damo)
RISC-V CoVE (Confidential VM Extension) brings confidential computing — hardware-enforced isolation of tenant workloads from the hypervisor and cloud operator — to a fully open architecture.
Go to contribution page
A lightweight TEE Security Manager (TSM) sits below the hypervisor and enforces per-VM memory isolation, while tenants verify their environment through a standard IETF RATS attestation flow. The... -
Ryan Afranji (Google)
Coco VMs rely on bounce buffering to use the guest's vCPUs to encrypt and decrypt data for DMA. This memory copy is performed via the SWIOTLB bounce buffer.
Persistent disk read operations handle completions within their storage interface’s interrupt handler. When SWIOTLB is disabled, the interrupt handler is invoked only after the DMA data transfer is completed. This makes the handler only...
Go to contribution page -
Ankit Agrawal
We are extending Arm CCA device assignment to CXL Type-2 accelerators so a Realm VM can receive such a device with a coherent device memory window. Standard RME-DA assigns a PCIe TDI to a Realm through TDISP, SPDM and IDE, protecting CXL.io traffic. A CXL Type-2 device also exposes a coherent CXL.mem window through HDM decoders and which confidential assignment must also secure.
RMM v2.0...
Go to contribution page -
Elena Reshetova (Intel)
Live migration and runtime attestation are two critical features for Confidential Computing to get right, not just in terms of fulfilling customer requirements, but also correct integration into common Linux codebase and overall code simplicity and maintainability. Based on Linux community feedback, TDX architecture went through a few big changes last year wrt to Live Migration and...
Go to contribution page -
Manali Shukla
PMU Event filtering is a security feature that allows hypervisors to restrict which performance events guests can monitor, preventing potential side-channel attacks. However, when using hardware-acceleration PMU virtualization, the encrypted VMSA in SEV-ES and SEV-SNP creates a fundamental challenge: hypervisors cannot read or modify guest PMU states directly, which breaks PMC filtering with...
Go to contribution page -
Alexey Kardashevskiy (AMD)
SEV-TIO is quite known by now, the upstream development is split in stages and continues. The current stages are set to support basic functionality.
The talk will focus on extended features and how AMD hardware/firmware is going to implement these. This includes:
Go to contribution page
- huge pages handling in IOMMU and KVM, how RMP works and what TMPM does in PSMASH_IO.
- IOMMU TLB flushing challenges: a hack... -
Adrian Reber (Red Hat), Mr Christian Brauner, Michal Koutný (SUSE), Mike Rapoport, Stéphane Graber (Zabbly)
The Containers and Checkpoint/Restore micro-conference focuses on both userspace and kernel related work.
The micro-conference targets the wider container ecosystem ideally with participants from all major container runtimes as well as init system developers.
The microconference will be discussing recent advancements in container technologies with some of the usual candidates being:
...
Go to contribution page -
Serapheim Dimitropoulos (CoreWeave)
CoreWeave is a bare-metal cloud provider. A typical machine in our fleet has at least 2TB of RAM, and customers tend to run close to that limit. That has two immediate consequences: the crash-kernel memory reservation matters a lot (every GB we reserve is a GB the customer doesn't get), and when a machine panics the resulting crash dump is huge. Because it's so big, the downtime during a...
Go to contribution page -
Sam Crossley (Meta)
This talk explores Meta's approaches to identifying production issues rooted in the Linux kernel. Our investigation process, spanning detection, correlation, and deep triage, relies on a unified framework of telemetry and monitoring tools. A common challenge arising in hyperscale kernel releases is that of robustly comparing kernel performance across lifecycle phases, despite vast variations...
Go to contribution page -
Davidlohr Bueso (Samsung Semiconductor), Jonathan Cameron
The Device and Specific Purpose Memory Microconference is proposed as a space to discuss topics that cross MM, Virtualization, and Memory device-driver boundaries. Beyond CXL this includes software methods for device-coherent memory via ZONE_DEVICE, physical memory pooling / sharing, and specific purpose memory application ABIs like device-dax, hugetlbfs, and guest_memfd. Some suggested topic...
Go to contribution page -
Mr Krzysztof Kozlowski (Qualcomm)
The Devicetree Microconference focuses on discussing and solving problems present in the systems using Devicetree as firmware representation. This notably is Linux kernel and U-Boot, which share the Devicetree bindings and sources, but also can cover topics relevant to Zephyr or System Devicetrees. Systems using Devicetree are majority of embedded boards, mobile devices and ARM64...
Go to contribution page -
Bartosz Golaszewski (Qualcomm)
Driver Core Microconference focuses on general problems of the linux kernel driver model.
The goal is to discuss the various aspects and problems of device driver core, platform and auxiliary devices, subsystem architecture, firmware description, fw_devlink, API design and object life-time issues.
Current problems:
**Object life-time issues and proposed...
Go to contribution page -
André Almeida (Igalia), David Vernet (Meta)
The Gaming on Linux Microconference welcomes the community to discuss a broad range of topics around improvements for Gaming devices running Linux. Gaming on Linux has pushed the kernel to improve in several areas and has helped create new features for Linux, such as the futex_waitv() syscall, the Unicode subsystem, HDR support, sched_ext, and much more. Although some of these were initially...
Go to contribution page -
André Almeida (Igalia)
Atomics can be challenging enough by themselves, and emulating them can be even worse. The lack of correctness will crash the application sooner or later, and the lack of performance will be very noticeable.
One key difference between x86 and arm64 is how they handle atomic operations on unaligned addresses. While on x86 such operations are supported transparently, on arm64 they raise a...
Go to contribution page -
David Vernet (Meta)
I've observed that on the Steam Deck, changes to the AMD p-state driver can have a significant impact on tail latencies and stale frame numbers. I've submitted an RFC upstream which proposes a per-CPU EPP boost heuristic: https://lore.kernel.org/all/20260728073150.54964-1-void@manifault.com/.
We should discuss gaps in the current cpufreq / AMD p-state driver, and how to best address...
Go to contribution page -
Daniel Almeida (Collabora), Philipp Stanner
The Linux kernel is responsible for managing the dependency graph of userspace's compute and graphics shaders. Moreover, it handles the GPU load balancing and tries to guarantee forward progress and deadlock resistance.
Historically, most graphics drivers have used drm_sched, a problematic legacy code base, for these tasks. More recently, Rust drivers are ramping up their own infrastructure...
Go to contribution page -
Srinivas Pandruvada
Gaming performance remains critical for user experience, but power efficiency has become equally important, particularly for battery-powered devices. Also improves thermal management and reduce thermal throttling. LPMD offers a solution for enhancing energy efficiency by dynamically selecting optimal processor configurations and power slider settings based on CPU and GPU utilization.
Go to contribution page
This... -
David Hildenbrand (Arm), Lorenzo Stoakes
Some people say that 2026 is the year of Linux Memory Management. Others weirdly disagree.
In any case, there is plenty to discuss, as MM is as busy as ever.
We are looking for topics that would be of interest to the kernel memory-management community.
In particular, we are also interested in topic suggestions from outside the core kernel community, including userspace, drivers,...
Go to contribution page -
Arisu Tachibana, Guillaume Tucker
The Kernel Testing & Dependability Micro-Conference (a.k.a. Testing MC) focuses on advancing the current state of testing of the Linux kernel and its related infrastructure.
Building upon the momentum from previous years, the Testing MC's main purpose is to promote collaboration between all communities and individuals involved with kernel testing and dependability. We aim to create...
Go to contribution page -
Arisu Tachibana
kci-dev was created as a standalone command-line tool that allows kernel developers and maintainers to interact directly with KernelCI. Since its initial releases, the project has grown beyond its original role as a thin client for triggering jobs and retrieving results.
The latest development cycle, including the v0.1.11 release, introduced a reusable Python library interface, direct...
Go to contribution page -
Mr Cong Wang (Multikernel Technologies)
Our CI systems build thousands of kernels a day, yet the kernel build itself has no canonical identity and no portable distribution format. Reproducing the exact binary behind a regression report is guesswork, and correlating KCIDB results back to a build is convention, not verification.
KBI (Kernel Bundle Image, Apache-2.0) is a concrete starting point for fixing this. It packages vmlinuz,...
Go to contribution page -
Ethan Graham (Student at ETH Zurich)
At LPC 2025 we introduced KFuzzTest, a framework for exposing stateless and low-state internal kernel functions, such as complex data parsers and the like, directly to a userspace fuzzer, reaching code that system-call fuzzers struggle to exercise. Developers define targets alongside their functions using a simple macro-based API, with constraints and type annotations compiled into dedicated...
Go to contribution page -
Aleksandr Nogikh (Google), Chuyang Wang
Coverage-guided fuzzing has proven to be highly effective at discovering Linux kernel vulnerabilities. Since its appearance in 2016, syzkaller - especially through the automated syzbot platform - has reported over 14,000 findings to the public kernel mailing lists.
Despite the success, traditional fuzzing methods struggle to reach deep code paths within complex kernel subsystems, even when...
Go to contribution page -
David Gow
The
Go to contribution pagekunit.pytool currently spreads its configuration across three places:kunitconfigfiles, which contain Kconfig entries for the kernel being tested;qemu_configpython scripts, which configure architecture- and emulator-specific options; and command-line arguments, which specify what is being done (building, testing, parsing, etc.), and any options specific to the run (filters,... -
Muhammad Bilal (Individual)
The Linux accel/ subsystem is still relatively young, yet it already exposes
complex userspace interfaces for machine learning accelerators. These drivers
process user-controlled command streams, DMA descriptors, tensors, and region
metadata, making input validation critical.This talk presents the results of a security audit of the accel/ethosu driver
Go to contribution page
that led to seven upstream fixes... -
Mr Norbert Manthey (AWS), Stanislav Uschakow (AWS)
KernelCI provides continuous testing for the Linux kernel. Over the past year we extended testing into the cloud. AWS lab is now integrated upstream and visible on the KernelCI dashboard.
We will describe the architecture and how it maps onto KernelCI's pull-mode lab model so other cloud vendors can attach their own infrastructure. We will share the gotchas of testing on remote virtualized...
Go to contribution page -
Paolo Bonzini (Red Hat, Inc.), Sean Christopherson (Google)
KVM (Kernel-based Virtual Machine) enables the use of hardware features to
Go to contribution page
improve the efficiency, performance, and security of virtual machines
created and managed by userspace. KVM was originally developed to host
and accelerate "full" virtual machines running a traditional kernel and
operating system, but has long since expanded to cover a wide array of use
cases, e.g. hosting real... -
Mostafa Saleh (Google)
As Protected KVM (pKVM) progresses on arm64, achieving full isolation requires hypervisor-controlled IOMMUs to prevent DMA attacks. While there has been progress on SMMUv3 support for pKVM via trap-and-emulate on the mailing list [1], a major architectural design question remains unresolved: managing the stage-2 translation tables.
Currently, the series relies on maintaining a shadow...
Go to contribution page -
Ackerley Tng
To improve performance of CoCo VMs, there's active work on huge pages for guest_memfd. The first "backend" in the works for providing huge pages is HugeTLB.
Frank summarized interest in having devdax/ZONE_DEVICE memory as another backend [1] for guest_memfd.
If guest_memfd is to be the guest memory provider of KVM, it has to support (almost) any memory backend that can be configured in...
Go to contribution page -
Pasha Tatashin
As cloud infrastructure continues to push toward zero-downtime host maintenance, extending the capabilities of kexec-based Live Update to minimize guest disruption is becoming increasingly critical. This proposal introduces the architectural concept of an "Orphaned VM"—a virtual machine that actively executes guest instructions on isolated physical hardware while completely decoupled from a...
Go to contribution page -
Claudio Imbrenda (IBM)
KVM uses the mmu_notifier infrastructure to keep the guest mapping up to date. After having completely rewritten the memory management of KVM/s390 to use mmu_notifiers, I have noticed some of the shortcomings in how KVM uses the notifiers.
Some of areas where KVM's usage of the notifiers, or the mmu_notifier infrastructure itself can be improved:
- passing the reason code to the KVM...
-
Pratyush Yadav, Tarun Sahu (Google)
Orhpaned VMs [0] is proposed to be the next evolution of hypervisor live update. It relies on a specialized micro-hypervisor, called the Caretaker, which handles VM Exits during the time between old kernel shutting down and new kernel booting up. The Caretaker reduces the downtime observed by the VM during live update by servicing VM Exits during this transition period.
The Caretaker is not...
Go to contribution page -
Breno Leitao (Meta), Jason Xing (Tencent), Usama Arif
The Linux System Monitoring and Observability MC brings together developers, maintainers, system engineers, and researchers to tackle unsolved problems in understanding, monitoring, and maintaining the health of Linux systems at scale.
Engineers managing millions of Linux servers face monitoring and observability challenges that no single team can solve alone. This track provides a forum...
Go to contribution page -
Jakub Sitnicki (Cloudflare)
Operating a network at scale, we routinely need to answer a deceptively simple question: what path did this packet take through the kernel, and where did it get dropped? On our edge, a single packet can cross several network namespaces, get encapsulated in GRE or IPIP, be encrypted with IPsec, and pass through multiple nftables chains before it leaves the box. Tagging the payload the way we...
Go to contribution page -
David Dai, Shakeel Butt
We've observed issues in the fleet where kernel lock holders are unable to obtain CPU time, causing waiters to block and stall overall system wide progress which can be broken into 3 main phenomena:
CPU Bandwidth Limiter: Kernel lock holders being throttled(This should be solved in sched/fair on newer kernels, but presents a problem for BPF schedulers that support cpu.max)
Go to contribution page
CPUSET... -
John Harrison (Igalia)
Debugging end user kernel issues is a problem
Reporting bugs is hard - important information is scattered across many log files, crash files, sysfs entries, etc. Most end users don't know where or how to file a bug. They might not even know that a crash has happened (just a glitch on the screen or a log entry somewhere).
When a bug is reported, triage can be difficult. Likely only...
Go to contribution page -
Yuan Tan
Linux kernel bugs are reported through fuzzers, static analyzers, mailing lists, and increasingly AI-assisted tools. These reports vary widely in quality: some are duplicates or false positives, while others describe exploitable vulnerabilities or issues with little practical impact. Maintainers still need to determine what is real, what matters, and what deserves attention first.
We are...
Go to contribution page -
Jiri Kosina (SUSE), Joe Lawrence (Red Hat), Josh Poimboeuf (Red Hat), Miroslav Beneš, Petr Mladek (SUSE), Song Liu (Meta)
Kernel Live Patching allows fixing kernel bugs without rebooting
or stopping the workload. It is an essential tool to keep modern
data centers health with fast evolving kernels and workloads.The Live Patching MC at Linux Plumbers 2026 aims to gather
stakeholders and interested parties to discuss proposed features
and outstanding issues in live patching.Possible topics for this...
Go to contribution page -
Kris Van Hees (Oracle USA)
One pain point that is emerging more and more as live patching becomes more common on systems is that although there is coordination between ftrace and live patching (for live patching approaches that use it), the same cannot be said for kprobe and kretprobe. Sudden lack of trace data being generated is often the only indication that the function being traced is being bypassed due to live...
Go to contribution page -
Song Liu (Meta)
In modern data centers, both livepatch and tracing (kprobe, ftrace, BPF, etc.) are expected to work 100% of the time. However, when livepatch and tracing are attached to the same kernel functions, they may negatively affect each other.
Go to contribution page
In this talk, we will present a survey of the compatibility of livepatch and tracing mechanisms, i.e., whether livepatch and different tracing mechanisms can... -
Alexander Graf, David Matlack (Google), Mike Rapoport, Pasha Tatashin
Proposal
Live Update is a specialized reboot process where selected devices are kept operational and kernel state is preserved and recreated across a kexec. For devices, DMA and interrupts may continue during the reboot.
The primary use-case of Live Update is to enable hypervisor updates in cloud environments with minimal disruption to running virtual machines. During a Live Update,...
Go to contribution page -
yanjun zhu
As cloud infrastructure scales and Confidential Computing adoption increases, host-level Live Update via kexec has become vital for maintaining zero-downtime operations. While progress has been made in preserving guest memory (guest_memfd, hugetlb) and hardware device states (VFIO), a critical gap remains in the network stack: preserving virtual networking topologies and stateful...
Go to contribution page -
Mr Prasanna Kumar T S M (Microsoft), Srivatsa Bhat (Microsoft)
Motivation:
Kexec Hand-Over (KHO) helps minimize downtime during kernel updates by preserving state across the kexec reboot. However, there are some scenarios which need a deeper form of reboot to be effective -- for example, performing a firmware update or a device-tree refresh, or even to avoid known hardware/platform bugs that make the kexec path itself unreliable. In such cases, the...
Go to contribution page -
Tarun Sahu (Google)
Guest_memfd is a specialized, guest-first memory subsystem within the Linux kernel, specifically designed for KVM. It provides an isolated file-descriptor-based approach to managing Virtual Machine memory.
For this MC, I want to propose the topic on Preservation of guest_memfd with LUO.
I will discuss the current development on guest_memfd preservation during kernel Liveupdate and (If...
Go to contribution page -
Logan Odell (Google), Pratyush Yadav
Data that is serialized and preserved through a live update may have formatting differences between two kernels. This can affect the compatibility between two kernels when trying to perform a Live Update. Current efforts have been to use compatibility strings with implicit version numbers, like "memfd-v2" to help provide compatibility data. Changes to the formatting of the preserved data may...
Go to contribution page -
Pranjal Shrivastava, Samiullah Khawaja
Go to contribution page
The current IOMMU Live Update framework establishes the mechanism for preserving IOMMU hardware state and translation units (HWPTs) across a live update. By utilizing the IOMMUFD and Kernel Handover (KHO) framework. This session talks about the current state of Liveupdate IOMMU and the upcoming features, challenges and enhancements.
The session dives deeper into the design challenges... -
Mr Luca Boccassi (Microsoft)
systemd v261 added native support for LUO. System services, user services and nspawn containers can preserve data across kexec in a simple and transparent manner, using the existing File Descriptor Store API.
This talk will explore what is implemented and how to use it, and what are the next steps.
Go to contribution page -
David Matlack (Google)
Live Update minimizes downtime by allowing PCI devices, like those assigned to VMs via VFIO, to continue operating during a host kernel upgrade. The recently proposed v7 patch series introduces the foundational PCI core support for Live Update. By leveraging LUO to preserve the list of preserve devices, the infrastructure allows PCI devices to maintain uninterrupted memory transactions to/from...
Go to contribution page -
Michał Cłapiński (Google)
Many use-cases of live-update require it to be fast. For cloud providers, executing host kernel updates without impacting guest workloads demands low-downtime live-update reboots.
We will discuss what improvements were already done to the Linux kernel, the ongoing work and future plans. This talk will also explain to developers how to configure their systems to achieve the best reboot performance.
Go to contribution page -
Samiullah Khawaja
Preserving subsystem state across a live update introduces a complex challenge: managing the dependencies of File Descriptors. Interconnected subsystems—such as VFIO and IOMMUFD with a lot of shared state, IOMMUFD's dependency on memory providers memfd/guest_memfd or KVMfd/guest_memfd dependency requires preservation ordering to guarantee state immutability and performance.
Currently, the...
Go to contribution page -
Vipin Sharma (Google)
Live Update enables hypervisor updates with minimal guest downtime by preserving VM state across
kexec. While memory preservation (via KHO/LUO) covers VM RAM, pass-through PCIe devices assigned to VMs (e.g., GPUs, NICs, NVMe, accelerators) require kernel support to maintain device state across the reboot boundary.This talk presents the design of VFIO Live Update (Phase 1, recently posted...
Go to contribution page -
Imran Khan
Production incidents often require answering concrete questions about current kernel state: which tasks are blocked, what is on each runqueue, where D-state tasks are stuck, or what reclaim and I/O state looks like while the host is still alive. Existing tools such as drgn and crash are powerful, but live inspection can require substantial kernel memory traversal from userspace and may be...
Go to contribution page -
Danilo Krummrich, John Hubbard (NVIDIA)
This workshop will center on Nova, the upstream Rust-based kernel driver for NVIDIA GPUs, and on Rust in the DRM subsystem in general.
On the Nova side, discussion topics will include the design and evolution of the firmware APIs exposed by the GPU System Processor (GSP), in particular the new GMC APIs, as well as user-space submission interfaces, compute APIs, and interactions with the...
Go to contribution page -
Brendan Gregg (OpenAI)
A new era is upon performance engineering where we ask AI to do much of our analysis and thinking: we run "performance prompts" (and skills and agents) instead of "performance tools." These can analyze all sources, including flame graphs, bcc and bpftrace tools (eBPF), Ftrace, PMCs, and MSRs; they can also propose new metrics and tools. How well does it currently work, and what does this mean...
Go to contribution page -
Dr Daniel Lezcano (Qualcomm), Rafael Wysocki (Intel), Ulf Hansson (Qualcomm)
The Power Management and Thermal Control micro-conference is about all things related to saving energy and managing heat. Among other things, we care about CPU, platform and device power-management mechanisms, thermal control support, and power capping. In particular, we are interested in improving and extending thermal control support in the Linux kernel and utilizing energy-saving features...
Go to contribution page -
Drew Fustini (Tenstorrent), Paul Walmsley (SiFive)
LPC 2026: RISC-V Microconference
The RISC-V ecosystem continues to expand rapidly, with new silicon like the RVA23-compatible SpacemiT K3, a steady cadence of ratified and vendor-defined ISA extensions, and platform classes reaching from embedded parts to server-class SoCs. Session topics cover architecture work, platform and vendor enablement, firmware/SBI coordination, and userspace...
Go to contribution page -
Mr Himanshu Chauhan (Qualcomm Technologies)
Error INJection (EINJ), defined by ACPI, offers a platform-independent mechanism to inject hardware errors and validate system resilience paths. By avoiding platform-specific tooling, EINJ enables consistent testing of the Linux error-handling stack across architectures, including APEI and broader RAS workflows.
This session discuss the design and implementation strategy for enabling EINJ...
Go to contribution page -
Mr Tom Gall (RISC-V International)
The RISC-V ISA specs contained the ratified collection of bases, extensions and profiles. This talk will cover recently ratified extensions, as well as cover upcoming extensions and profiles which are close to ratification. We'll dive into kernel / user space design considerations that implementors will want to care about.
Go to contribution page -
Mr Roman Storozhenko (Intel)
RISC-V Linux TLB flushing has several runtime paths. A flush may be local to the current hart, may use SBI remote fence support, or may fall back to Linux IPIs. The kernel also makes range-versus-full decisions, performs ASID-aware flushing, and carries different flush strides for normal and huge-page ranges. These decisions can matter when debugging correctness issues, performance anomalies,...
Go to contribution page -
Cong Wang, Mr Yuning Liang (Deep Computing)
Boot mainline on SpacemiT's Key Stone K3 and half the machine stays dark: eight 1024-bit AI cores rejected by smpboot because riscv_v_vsize allows exactly one vlenb per system. This is not a bring-up bug, it is the first shipping proof that RISC-V vendors will not pay for matched vector widths, and the SG2042's RVV 0.7.1 installed base makes it worse: not narrower, incompatible. Per-process...
Go to contribution page -
Tao Chiu
The territory of using a larger context in the kernel-mode has been a forbidden topic since the existence of Linux. The use of SIMD unit in the kernel-mode is strictly restricted because the program is highly optimized for stack footprint, responsiveness, and maximum hardware compatibility. However, as hardware and compiler technologies advance, the benefit of enabling autovectorization has...
Go to contribution page -
Yunhui Cui (ByteDance)
Svnapot gives RISC-V an architectural way to encode contiguous PTE ranges as folded mappings, and 64K mTHP is a particularly good match
for that capability.This session presents a patch series that enables that model through dynamic fold/unfold and a split between public and raw page-table
Go to contribution page
APIs. Public helpers preserve the logical sub-PTE view expected by core MM, while raw helpers... -
SUNIL V L (Qualcomm)
To support RISC-V E-trace/N-trace components in ACPI, we propose using the Device Graph UUID defined in the DSD Guide, aligned with how similar topologies are described on other architectures. Beyond discussing the proposal itself and how it should appear in the ACPI namespace, we also want feedback on implementation strategy.
Today, ACPI fwnode graph handling does not interpret Device...
Go to contribution page -
Guodong Xu
RVA23 is ratified and the first (vendor-announced) compliant silicon is shipping, but between "the profile exists" and "userspace can rely on it" sit three unresolved kernel questions.
Discovery. Extension capability discovery between user mode and the kernel is still messy: hwprobe and prctl can disagree, so which interface should IFUNC resolvers actually trust, or does the discovery...
Go to contribution page -
Mr Qiubing Zhang (SpacemiT), Mr Dong Xu (SpacemiT)
Background
SpacemiT K3 is among the first production RVA23-compatible SoCs, shipping since late 2024. K3 features heterogeneous vector lengths:
- 8× X100 cores: RV64GCV, VLEN=256, full RVA23 compliance, H-extension — general-purpose
- 8× A100 cores: RV64GCV, VLEN=1024, no H-extension — AI/vector compute
Both core types implement RVV 1.0, but their incompatible vector...
Go to contribution page -
Palmer Dabbelt (Google), Paul Walmsley (SiFive)
Review the past year in RISC-V Linux kernel maintenance, and discuss upcoming plans for the next year - similar to what we did last year
Go to contribution page -
Miguel Ojeda
Rust is a systems programming language that is making great strides in becoming the next big one in the domain. Rust for Linux is the project adding support for the Rust language to the Linux kernel.
Rust has a key property that makes it very interesting as the second language in the kernel: it guarantees no undefined behavior takes place (as long as unsafe...
Go to contribution page -
Kate Stewart (Linux Foundation), Philipp Ahmann (Etas GmbH (BOSCH))
Description/Motivation
As Linux continues to be deployed in systems with varying criticality constraints, the need for consistent linkage between requirements, code, and tests becomes increasingly important at the higher assurance levels. Establishing such traceability can improve development and testing efficiency, supports necessary analysis, and reduces long‑term maintenance...
Go to contribution page -
Andrea Righi (NVIDIA), Changwoo Min (Igalia)
sched_ext is a Linux kernel feature that enables implementing safe task schedulers in BPF and dynamically loading them at runtime. Its key strength is flexibility, allowing rapid iteration of scheduling policies, deploying changes on the fly and quickly addressing topology inefficiencies or workload-specific issues.
This MC provides a space for the...
Go to contribution page -
Vincent Guittot (Linaro)
Building upon the success of last year, we propose a combined microconference focused on the Real-Time and Scheduler subsystems. These two areas are fundamentally intertwined and continue to drive cross-cutting changes, especially following the upstream integration of PREEMPT_RT. The Linux scheduler is central to overall system performance. Addressing the challenges of modern computing—from...
Go to contribution page -
John Stultz (Google), Suleiman <> Souhlal (Google)
More and more we’re seeing issues around priority (sometimes called performance) inversion of SCHED_NORMAL/BATCH tasks. Particularly if any sort of constraints are put on “background” deprioritized tasks. These background tasks will eventually grab an important lock, and then won’t be constrained and prevented from running for some extended period of time, resulting in all the important tasks...
Go to contribution page -
Mr Waiman Long (Red Hat)
By using the cpuset isolated partition functionality in the Linux
kernel, users are now able to change the set of "isolcpus[=domain]"
HK_TYPE_DOMAIN housekeeping CPUs at runtime. This feature is used by
some Kubernetes based container orchestration platforms to enable the
creation of containers running latency sensitive workloads like DPDK.Domain isolation by itself doesn't provide...
Go to contribution page -
Ricardo Neri (Intel Corporation)
During OSPM 2026, there was an agreement to stop requiring schedutil to enable EAS on x86 platforms, which implies EAS may soon be active by default on these systems.
Energy-Aware Scheduling (EAS) places tasks by comparing estimated energy costs across performance domains, directing light tasks to power-efficient cores on asymmetric systems. The known trade-off is that EAS packing...
Go to contribution page -
Mr Qais Yousef (Google)
Following last year discussion about userspace assissted scheduling [1], schedqos utility is announced [2] and a proposal for kernel interface to help address one of the QoS issues folks see in the wild, DVFS and migration latencies, was sent also [3].
The interface proposal is a simple extension to sched_attr, but has the goal of being extensible without requiring further addition to...
Go to contribution page -
Mr Felix Moessbauer (Siemens AG), Mr Florian Bezdeka (Siemens AG)
Realtimers know: Resource configuration for RT enabled systems is key. RT applications rely on a proper system configuration and expect this configuration to stay unmodified as long as the application is alive.
As it turned out, Linux might silently reconfigure IRQ affinities of network adapters in a way that violates the expected system configuration. While we run into this kind of problem...
Go to contribution page -
Richard Joseph Buturla (IBM)
A task running in a vCPU may be holding a spinlock when it gets preempted by the host scheduler. Other tasks running in other vCPUs may now be blocked on that spinlock, wasting CPU time.
At IBM, we observed that under overcommit, this manifests as directed yield storms and long spinlock wait times which people have tried to mitigate in many different ways including adjusting scheduler...
Go to contribution page -
Vincent Guittot (Linaro)
Recent improvements have been made in tasks ordering, scheduling latency and lag of the fair/EEVDF scheduler but some issues still remain and will involve more complex mechanisms. The talk will discuss possible solutions for a number of open issues:
Go to contribution page
How to fix the remaining out of range lag of tasks ?
How to further decrease the scheduling latency ?
How to select the best CPU to minimize... -
Prateek Nayak (AMD Inc.)
As CPU counts grow, Linux scheduler scalability suffers from contention on global cpumasks — frequent atomic updates to shared cachelines become a measurable bottleneck on large core-count systems.
Two proposals address this: Steve Sistare's sparsmask, which distributes a cpumask across multiple cachelines to reduce contention [1], and Peter Zijlstra's sbm (sparse bitmap) [2], a simpler,...
Go to contribution page -
Mr Piotr Król (3mdeb), Mr Daniel Kiper
The System Boot and Security Microconference remains a key venue for engineers and researchers focused on the intersection of firmware, bootloaders, and kernel security. For 2026, we continue our mission to address the persistent friction encountered when upstreaming security-focused boot improvements. Our goal is to bridge the gap between low-level hardware initialization and the Linux kernel...
Go to contribution page -
Manivannan Sadhasivam
The Linux PCI Endpoint Framework provides the software infrastructure for a Linux system to present itself as a PCIe Endpoint device to an external Host. It consists of an Endpoint Controller layer that abstracts the hardware, an Endpoint Function layer that implements device behavior, and a ConfigFS interface for userspace to bind them together. For testing, the upstream pci_endpoint...
Go to contribution page -
Jason Xing (Tencent)
This is a follow-up to "Methodology and Practice in Observing Kernel Networking" in 2025[1], which introduced why a solid methodology is essential before building a monitoring system and how to implement it in a real world. In this session, the concept of "agentic" is further proposed to achieve a truly automatically monitoring powered by an AI inference module. However, before utilizing AI,...
Go to contribution page -
Steven Rostedt
Description:
Visibility into the Linux kernel has always been critical for debugging and validating the execution of the code. The never ending challenge is to be able to trace the code without causing extra overhead, as tracing is most useful in a production environment.Possible topics for this year include:
- Updating the [deferred stack tracer][1] for [sframes][2].
- A...
-
Madhavan Srinivasan, Steven Rostedt, Tanushree Shah
The Linux kernel tracing ecosystem comprises two complementary toolchains: perf for statistical profiling and performance analysis, and ftrace/trace-cmd for event timeline visualization. While perf captures comprehensive performance data with minimal overhead, understanding temporal relationships and event sequences remains challenging through its native interfaces. In contrast, KernelShark...
Go to contribution page -
Ian Rogers (Google)
Performance event sampling traditionally captures virtual addresses, resolving them to file offsets and symbols post-facto via mmap metadata. Conversely, BPF enables a direct approach: recording the file's build ID and offset within the sample itself. While virtual addresses are smaller inline, the required mmap event stream may lead to much larger raw data files.
In this talk, we examine...
Go to contribution page -
Byungchul Park
DEPT (DEPendency Tracker) is a runtime dependency tracking framework
Go to contribution page
that detects potential deadlocks by tracking wait/event relationships
rather than lock acquisition order. Unlike lockdep, which is limited to
typical locking primitives, DEPT can detect deadlocks involving general
synchronization mechanisms such as folio locks, completions, DMA fences,
and other wait/event-based... -
Ms Alice Rogers, Ian Rogers (Google)
Traditionally, the Linux perf tool has relied on a text user interface (TUI) based on libslang and embedded Python/Perl interpreters for scripting support. However, developing robust user interfaces in C is tedious and error-prone, and using perf itself as the interpreter integrates poorly with broader programming language ecosystems.
In this talk, we will describe how we refactored perf...
Go to contribution page -
Steven Rostedt
Stack tracing of events can be very useful, for both kernel stack tracing as well as user space stack tracing. Stack traces can fill the buffer quickly with many duplicate stacks. Having a way to consolidate them would make it possible to store even more data. There's been [efforts][1] to do this but how to implement it and the interface is still an ongoing subject.
On top of that, tracing...
Go to contribution page -
Mr Wander Costa (Red Hat)
Debugging latency issues in production RT kernels often requires
Go to contribution page
understanding where and why preemption and interrupts are being
disabled. Today, enabling thepreempt_disable/enableand
irq_disable/enabletracepoints requires pulling in heavyweight
infrastructure — either the preemptoff/irqsoff latency tracers or the
full lockdep IRQ tracking — that carries too much overhead... -
Mr Masami Hiramatsu (Google)
BTF fetcharg has been introduced since v6.5 for fprobe and kprobe events for fetching function parameters by name, and now we intrdouced typecast feature for BTF. This typecast feature is not only casting type, but also, the series supports nested typecasts, container_of(), this_cpu_ptr(), and "current" task structure access. With these features, we can access more context local data from...
Go to contribution page -
Alex Williamson, Bjorn Helgaas (Google), Krzysztof Wilczyński, Lorenzo Pieralisi
The [PCI][1] interconnect specification, the devices that implement it, and the system IOMMUs that provide memory and access control to them have become the de-facto standard for connecting high-speed components. The specification continues to expand with features spanning address translation (ATS/PRI), I/O virtualisation ([SR-IOV][2]/PASID/SVA), high-performance data movement (RDMA,...
Go to contribution page -
Prakash Gupta (Qualcomm), Mr Vijayanand Jitta (Qualcomm)
This talk covers ARM SMMU contiguous-hint support in Linux stage-1 page tables and the ARM-SMMU PMU support used to measure its impact. The work enables larger effective mappings, including 64K regions built from 16 adjacent 4K entries, and extends IOMMU map/unmap support for mixed and larger mapping sizes. In parallel, ARM-SMMU PMU integration exposes TBU and TCU counters through perf,...
Go to contribution page -
Leon Romanovsky, Lukas Wunner
The kernel uses a [whitelist][1] do determine whether peer-to-peer DMA is supported between devices. But constantly amending the whitelist is a maintenance burden.
We are proposing to extend the ACPI HMAT table with bandwidth and latency characteristics for P2PDMA traffic between PCI host bridges (and between devices below the same host bridge).
This will remove the need for a...
Go to contribution page -
Logan Odell (Google), Pranjal Shrivastava
Go to contribution page
The current Linux memory management framework lacks the mechanism for tracking IOMMU page table (IOPT) consumption across sparse virtualization workloads. By utilizing the IOMMUFD and VFIO frameworks, hypervisors dynamically map and unmap massive IOVA regions, often leaving intermediate page table directories stranded and invisible to the core kernel. This session talks about the current... -
Jacob Pan
Device assignment in Microsoft Hypervisor (/dev/mshv) host environments has requirements beyond existing KVM-oriented workflows, including direct HWPT attachment for assigning a device to a guest while preserving existing Stage-2 page tables, and VMM-assigned virtual device information to facilitate hypercall-based device operations.
We plan to publish an RFC before LPC describing the...
Go to contribution page -
Mr Suravee Suthikulpanit, Vasant Hegde
Modern cloud computing increasingly relies on confidential virtual machines (VMs) - isolated environments
where sensitive workloads run securely, even from the underlying hypervisor. A key challenge in this space
is enabling these confidential VMs to safely communicate with hardware devices without exposing their data
to the host system or hypervisor.Virtual IOMMU (vIOMMU) is an...
Go to contribution page -
Maciej Grochowski
In 2024, hotplug on our NVMe storage fleet — NTB behind Microchip/Switchtec switches — was
Go to contribution page
not stable on mainline, so we ran Keith Busch's out-of-tree bus-locking series on a private
branch. It held. Then a new hardware generation arrived, we needed a kernel we could
validate against, and that meant mainline: 6.8, now 6.17. Going upstream meant giving up the
structural work that had been... -
Mr Chengwen Feng (Huawei)
PCIe TPH enables cache steering for high-performance P2PDMA, RDMA and SDXI workloads. Today Linux only supports TPH operations within host kernel space; userspace/VFIO passthrough environments lack a standard interface to resolve and program steering tags.
Go to contribution page
I’ve posted a complete patch series adding native VFIO TPH support, aligned with community incremental security policy design. The series...
Choose timezone
Your profile timezone: