Live-Patching Archive on
 help / color / Atom feed
From: Nicolai Stange <>
Cc: Petr Mladek <>, Nicolai Stange <>,
	Kamalesh Babulal <>,
	Joe Lawrence <>,
	Miroslav Benes <>,
	Alice Ferrazzi <>,
	Josh Poimboeuf <>,
	Jiri Kosina <>
Subject: LPC19 Live Patching MC: materials for "Source-based livepatch creation tooling"
Date: Fri, 06 Sep 2019 15:44:13 +0200
Message-ID: <> (raw)


to get the most out of the "Source-based livepatch creation tooling"
session at this year's LPC Live Patching MC, I'd like to spend as little
time as possible on (re-)introducing klp-ccp and the approch behind it,
but focus more on discussing open questions.

So, to give everybody a chance to get a good overview on past
discussions as well as the current state, let me share a few pointers.

First of all, there had been Miroslav's talk from last year about
compiler optimizations ([1]) and also mine, where I outlined an initial
approach to automating source based livepatch creation ([2]). Recordings
are available.

Meanwhile, the implementation of the proposed tool for copying&pasting
live patches together, klp-ccp, has progressed to a state where it can
actually be used (*).

The sources for klp-ccp have recently been published at ([3]). I've put
together a preliminary README describing the overall mode of operation
and its interface. The topics I'd like to bring up for discussion are
mostly related to integration, so it would be awesome if you could have
a brief look.

Finally, in case you'd like to get an idea of how the actual output from
klp-ccp would look like, you can find the results from three different
runs against more or less random function sets at [4], [5] and [6].

Wish you all a save journey and see you next week!


    (LPC18, GCC optimizations and their impacts on live patching")
    (Livepatch patch creation tooling")

(*) with caution

SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 247165, AG München), GF: Felix Imendörffer

                 reply index

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

Reply instructions:

You may reply publically 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:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Live-Patching Archive on

Archives are clonable:
	git clone --mirror live-patching/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 live-patching live-patching/ \
	public-inbox-index live-patching

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone