aboutsummaryrefslogtreecommitdiffstats
path: root/lib/test_printf.c
diff options
context:
space:
mode:
authorMiroslav Benes <[email protected]>2019-04-04 18:44:11 +0000
committerPetr Mladek <[email protected]>2019-04-08 14:48:52 +0000
commit43bd3a95c98e1a86b8b55d97f745c224ecff02b9 (patch)
tree624c5f37459b9734e8cc1eddf7d6839a5943cd59 /lib/test_printf.c
parentMerge branch 'for-5.1/atomic-replace' into for-linus (diff)
downloadkernel-43bd3a95c98e1a86b8b55d97f745c224ecff02b9.tar.gz
kernel-43bd3a95c98e1a86b8b55d97f745c224ecff02b9.zip
kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled
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 <[email protected]> Signed-off-by: Miroslav Benes <[email protected]> Acked-by: Josh Poimboeuf <[email protected]> Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'lib/test_printf.c')
0 files changed, 0 insertions, 0 deletions