From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Miroslav Benes <mbenes@suse.cz>,
yamada.masahiro@socionext.com, michal.lkml@markovi.net,
jikos@kernel.org, joe.lawrence@redhat.com, ggherdovich@suse.cz,
linux-kbuild@vger.kernel.org, live-patching@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled
Date: Tue, 9 Apr 2019 09:36:07 +0200 [thread overview]
Message-ID: <20190409073607.ms4amehc23quaio3@pathway.suse.cz> (raw)
In-Reply-To: <20190404201855.xtvtgxaaomcmowrt@treble>
On Thu 2019-04-04 15:18:55, Josh Poimboeuf wrote:
> On Thu, Apr 04, 2019 at 08:44:11PM +0200, Miroslav Benes wrote:
> > GCC 9 introduces a new option, -flive-patching. It disables certain
> > optimizations which could make a compilation unsafe for later live
> > patching of the running kernel.
> >
> > The option is used only if CONFIG_LIVEPATCH is enabled and $(CC)
> > supports it.
> >
> > Performance impact of the option was measured on three different
> > Intel machines - two bigger NUMA boxes and one smaller UMA box. Kernel
> > intensive (IO, scheduling, networking) benchmarks were selected, plus a
> > set of HPC workloads from NAS Parallel Benchmark. The tests were done on
> > upstream kernel 5.0-rc8 with openSUSE Leap 15.0 userspace.
> >
> > The majority of the tests is unaffected. The only significant exception
> > is the scheduler section which suffers 1-3% degradation.
> >
> > Evaluated-by: Giovanni Gherdovich <ggherdovich@suse.cz>
> > Signed-off-by: Miroslav Benes <mbenes@suse.cz>
> > ---
> > The patch is based on master branch of the livepatching tree on
> > git.kernel.org.
> >
> > Many thanks to Giovanni who ran the whole testing campaign and analyzed
> > the results. I archived the dashboard and detailed data. If anyone is
> > interested, we could probably set up a public website somewhere.
>
> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
I have committed the patch into the branch for-5.2/core.
Best Regards,
Petr
prev parent reply other threads:[~2019-04-09 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 18:44 [PATCH v2] kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled Miroslav Benes
2019-04-04 20:18 ` Josh Poimboeuf
2019-04-05 8:33 ` Miroslav Benes
2019-04-09 7:36 ` Petr Mladek [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=20190409073607.ms4amehc23quaio3@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=ggherdovich@suse.cz \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=michal.lkml@markovi.net \
--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