-
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...
-
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 -
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
-...
-
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 -
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 -
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 -
Gregory Price (Meta)
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 -
Bharata Bhasker Rao (AMD)
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 -
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 -
Hervé Codina
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 -
Neil Armstrong (Linaro)
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 -
Mr Krzysztof Kozlowski (Qualcomm)
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 -
Doug Anderson
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...
-
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 -
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 -
Shivank Garg (AMD), Zi Yan (NVIDIA)
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 -
Kairui Song (Tencent)
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 -
Kevin Brodsky (Arm)
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,... -
Albert Esteve (Red Hat), T.J. Mercier (Google)
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)
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 -
Will Deacon
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 -
Shakeel Butt
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 -
Arisu Tachibana
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 -
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... -
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 -
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 -
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 -
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 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 -
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 -
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 -
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...
-
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
Choose timezone
Your profile timezone: