Live Patching
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Song Liu <song@kernel.org>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Miroslav Benes <mbenes@suse.cz>, Jiri Kosina <jikos@kernel.org>
Subject: [ANNOUNCEMENT/CFP] LPC 2026 Live Patching MC
Date: Wed, 1 Jul 2026 18:01:43 +0200	[thread overview]
Message-ID: <akU55z5bzhHhUV9R@pathway.suse.cz> (raw)

We are pleased to announce the Call for Subtopic Proposals (CFP)
for the Live Patching Micro Conference (MC)
at the 2026 edition of the Linux Plumbers Conference (LPC),
taking place in Prague, Czechia, from October 5–7, 2026:

 https://lpc.events/event/20/sessions/258/

The Live Patching MC at Linux Plumbers 2026 aims to gather
stakeholders  and interested parties to discuss proposed features
and outstanding issues in the kernel live patching.

Possible topics for this year:

  - Test framework for livepatch subsystem and the new klp-build
    toolchain

  - Live Patch compatibility with tracing solutions (kprobe, ftrace,
    BPF trampoline, etc.)

  - Replace the wild no-replace mode with independent replace sets,
    merge slots, provides, or obsoletes

  - Split a live patch module into submodules

  - SFrame and livepatch

  - Hybrid live patch idea

  - Use AI to help build live patch

Proposals can be submitted here (select "Live Patching MC" as the track):

 https://lpc.events/event/20/abstracts/

Please submit your proposals by August 7, 2026 to give us time to schedule talks
in advance of the conference.

Note that the primary purpose of a microconference talk is open discussion, not
formal presentations. Slides should be brief and only provide context. Each
15-30 minute topic is intended to encourage brainstorming and discuss open
issues, not necessarily to resolve them.

For any questions, feel free to contact the microconference leads:

 - Song Liu <song@kernel.org>
 - Joe Lawrence <joe.lawrence@redhat.com>
 - Josh Poimboeuf <jpoimboe@kernel.org>
 - Miroslav Benes <mbenes@suse.cz>
 - Petr Mladek <pmladek@suse.com>
 - Jiri Kosina <jikos@kernel.org>

We look forward to your proposals!

Best Regards,
Petr

                 reply	other threads:[~2026-07-01 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=akU55z5bzhHhUV9R@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=song@kernel.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