From: Miroslav Benes <mbenes@suse.cz>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>,
yamada.masahiro@socionext.com, michal.lkml@markovi.net,
jeyu@kernel.org, pmladek@suse.com, linux-kbuild@vger.kernel.org,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Joao Moreira <jmoreira@suse.de>
Subject: Re: [PATCH] kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled
Date: Fri, 21 Dec 2018 10:45:49 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.1812211045400.3002@pobox.suse.cz> (raw)
In-Reply-To: <20181220144626.2uwuzsmdowbrmxxq@treble>
On Thu, 20 Dec 2018, Josh Poimboeuf wrote:
> On Thu, Dec 20, 2018 at 09:33:05AM +0100, Miroslav Benes wrote:
> > > > Though, upstream, almost everybody seems to use kpatch-build, for which
> > > > this patch doesn't help. And people will continue to do so until we
> > > > have decent source-based tooling. Will the klp-convert patches be
> > > > revived soon?
> > >
> > > Let me add Joao, who's working on that.
> > >
> > > Joao, I think you had something basically ready for upstream exposure,
> > > right?
> >
> > I think that when Joao posted it a long time ago, the conclusion was that
> > it would be better to wait for the source-based tooling and have the
> > complete solution. I may misremember though.
> >
> > If Josh thinks that it would be acceptable to have klp-convert merged even
> > without the tooling, I'm all for it.
> >
> > We're about to start using it at SUSE and staying close to upstream would
> > definitely be better.
>
> A complete toolchain should definitely be the end goal.
>
> But as a usable first step, only *some* of the tooling is required,
> since some of the steps can be done manually, right?
>
> So starting out, for something usable, I believe the following would be
> the bare minimum:
>
> * -flive-patching
>
> * The analysis tool which analyzes the -fdump-ipa-clones files
>
> * klp-convert
>
> * Documentation describing the end-to-end patch creation process,
> including the manual steps and how to use the above tools
>
> Did I miss anything?
>
> Then over time we can fill in the gaps (manual steps) with automation.
Agreed.
Miroslav
next prev parent reply other threads:[~2018-12-21 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 14:17 Miroslav Benes
2018-12-19 16:54 ` Josh Poimboeuf
2018-12-19 16:58 ` Jiri Kosina
2018-12-19 17:21 ` Josh Poimboeuf
2018-12-19 18:10 ` Jiri Kosina
2018-12-20 8:33 ` Miroslav Benes
2018-12-20 14:46 ` Josh Poimboeuf
2018-12-21 9:45 ` Miroslav Benes [this message]
2018-12-20 21:47 ` Joao Moreira
2018-12-21 9:48 ` Miroslav Benes
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=alpine.LSU.2.21.1812211045400.3002@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=jmoreira@suse.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=pmladek@suse.com \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®