From: Miroslav Benes <mbenes@suse.cz>
To: Joao Moreira <jmoreira@suse.de>
Cc: Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
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
Subject: Re: [PATCH] kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled
Date: Fri, 21 Dec 2018 10:48:25 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.1812211046140.3002@pobox.suse.cz> (raw)
In-Reply-To: <3fec8358-f64c-57e4-fa7f-1ee91a45be9b@suse.de>
On Thu, 20 Dec 2018, Joao Moreira wrote:
> On 12/20/18 12:33 AM, Miroslav Benes wrote:
> > On Wed, 19 Dec 2018, Jiri Kosina wrote:
> >
> >> On Wed, 19 Dec 2018, Josh Poimboeuf wrote:
> >>
> >>> Also the commit message needs an analysis of the performance impacts.
> >>
> >> Agreed. Especially as it's expected (*) to be completely in the noise
> >> particularly for the kernel, it'd be good to have that documented in the
> >> changelog.
> >>
> >> (*) actually measured already for some subset of the IPA optimizations
> >
> > Ok, we can do that. I don't expect the results to be different from the
> > last measurement as Jiri mentions. The sets of disabled optimizations are
> > similar.
> >
> > I'll add it to v2.
> >
> > On Wed, 19 Dec 2018, Jiri Kosina wrote:
> >
> >> On Wed, 19 Dec 2018, Josh Poimboeuf wrote:
> >>
> >>>>> This option only makes sense for source-based patch generation, so isn't
> >>>>> it a bit premature to make this change without proper source-based patch
> >>>>> tooling?
> >>>>
> >>>> The reality is though that before the full-fledged patch tooling exists,
> >>>> people are actually already writing livepatches by hand, so this option
> >>>> is
> >>>> useful for them.
> >>>
> >>> Fair enough.
> >
> > Yes, that was the reason I sent it. It would not make sense to wait for
> > the tooling in this case, because -flive-patching is useful even now,
> > since there is a way to prepare livepatches without any tooling.
> >
> >>> 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.
>
> Your memories match mine, Miroslav.
>
> FTR, we recently integrated klp-convert to SLE. There were some fixes in
> comparison with the version which was submitted upstream, thus a v2 of the
> patches is necessary.
>
> >
> > If Josh thinks that it would be acceptable to have klp-convert merged even
> > without the tooling, I'm all for it.
> >
> Of course I can work on that and I'll be glad to do so / submit this new
> version, if this is now something considered useful.
Yes, please.
Some context first. We decided to remove the integration into kbuild at
SUSE. klp-convert is called from rpm .spec file directly after a livepatch
module is compiled.
I think we should preserve kbuild process in upstream though. It makes
more sense there.
Miroslav
prev parent reply other threads:[~2018-12-21 9:48 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
2018-12-20 21:47 ` Joao Moreira
2018-12-21 9:48 ` Miroslav Benes [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=alpine.LSU.2.21.1812211046140.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®