The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: kexec@lists.infradead.org
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	David Matlack <dmatlack@google.com>,
	Alexander Graf <graf@amazon.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	kvm@vger.kernel.org, linux-mm@kvack.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE/CFP] LPC 2026 Live Update Microconference
Date: Wed, 22 Jul 2026 18:56:07 +0300	[thread overview]
Message-ID: <amDoFzbQVdxjgqzH@kernel.org> (raw)
In-Reply-To: <ahcc3Qyuy7Oy03Iq@plex>

Hi,

This is a reminder that the CFP for Live Update microconference at Linux
Plumbers Conference is still open and even extended until August 7th.

On Wed, May 27, 2026 at 05:05:23PM +0000, Pasha Tatashin wrote:
> Hi,
> 
> The Call for Proposals is now open for the Live Update Microconference 
> [1], taking place at the Linux Plumbers Conference this October 5-7 in 
> Prague [2].
> 
> As infrastructure scales, minimizing workload disruption during host 
> updates has become a critical operational requirement. This 
> microconference focuses on the evolving engineering challenges behind 
> seamless software handovers, state preservation, and warm reboots that 
> bypass traditional hardware reset cycles.
> 
> We are seeking technical presentations, and problem statements spanning 
> the entire stack—including kexec optimizations, hypervisor integration, 
> user-space checkpoint/restore, firmware coordination, and device state 
> handovers.
> 
> ---
> A few focus areas we hope to cover during this year's sessions include:
> ---
>  * Orphaned Virtual Machine for zer-downtime upgrades.
>  * Live Update Orchestrator (LUO) enhancements and architecture
>  * Kexec HandOver (KHO) framework advancements
>  * Kexec reboot latencies to minimize guest/workload downtime
>  * Preserving guest states across live updates (guest_memfd, hugetlb)
>  * In-flight DMA, IOMMU tracking, and preservation
>  * VFIO device state preservation and live update migration mechanics
>  * PCI/PCIe device handovers, reset avoidance, and state restoration
>  * Live Update in Confidential Computing (TDX/SEV-SNP)
>  * Building robust testing, fuzzing, and validation frameworks for 
>    upgrade paths
> 
> ---
> Submission Details & Deadlines:
> ---
>  * CFP Portal: https://lpc.events/event/20/abstracts/
>  * Track Selection: "Live Update MC"
>  * Deadline: July 24th, 2026
> 
> Session Format Reminder:
> LPC sessions are highly interactive working groups, not static lecture 
> slots. Proposals should be designed to introduce a concrete technical 
> challenge quickly and leave substantial time open for real-time debate, 
> consensus-building, and problem-solving with the room. Keep slides 
> focused on architecture and open issues rather than heavy text blocks.
> 
> We hope to see you in Prague to help push the live update ecosystem 
> forward.
> 
> (Note: LPC attendance caps fill up exceptionally fast. We strongly 
> advise booking your passes early, as track organizers cannot always 
> guarantee speaker registration overrides once the event sells out.)
> 
> [1] https://lpc.events/event/20/contributions/2321/
> [2] https://lpc.events/
> 
> Best regards,
> Pasha

-- 
Sincerely yours,
Mike.

      reply	other threads:[~2026-07-22 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 17:05 [ANNOUNCE/CFP] LPC 2026 Live Update Microconference Pasha Tatashin
2026-07-22 15:56 ` Mike Rapoport [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=amDoFzbQVdxjgqzH@kernel.org \
    --to=rppt@kernel.org \
    --cc=dmatlack@google.com \
    --cc=graf@amazon.com \
    --cc=kexec@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox