From: Jessica Yu <jeyu@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: jpoimboe@redhat.com, jikos@kernel.org, mmarek@suse.com,
pmladek@suse.com, jmoreira@suse.de,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] livepatch: Make livepatch dependent on !TRIM_UNUSED_KSYMS
Date: Fri, 26 May 2017 14:53:25 -0700 [thread overview]
Message-ID: <20170526215325.fa4qeyhstijgmb7e@jeyu> (raw)
In-Reply-To: <20170526124521.28592-1-mbenes@suse.cz>
+++ Miroslav Benes [26/05/17 14:45 +0200]:
>If TRIM_UNUSED_KSYMS is enabled, all unneeded exported symbols are made
>unexported. Two-pass build of the kernel is done to find out which
>symbols are needed based on a configuration. This effectively
>complicates things for out-of-tree modules.
>
>Livepatch exports functions to (un)register and enable/disable a live
>patch. The only in-tree module which uses these functions is a sample in
>samples/livepatch/. If the sample is disabled, the functions are
>trimmed and out-of-tree live patches cannot be built.
>
>Note that live patches are intended to be built out-of-tree.
>
>Suggested-by: Michal Marek <mmarek@suse.com>
>Signed-off-by: Miroslav Benes <mbenes@suse.cz>
Makes sense to me:
Acked-by: Jessica Yu <jeyu@redhat.com>
>---
> kernel/livepatch/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/kernel/livepatch/Kconfig b/kernel/livepatch/Kconfig
>index 045022557936..ec4565122e65 100644
>--- a/kernel/livepatch/Kconfig
>+++ b/kernel/livepatch/Kconfig
>@@ -10,6 +10,7 @@ config LIVEPATCH
> depends on SYSFS
> depends on KALLSYMS_ALL
> depends on HAVE_LIVEPATCH
>+ depends on !TRIM_UNUSED_KSYMS
> help
> Say Y here if you want to support kernel live patching.
> This option has no runtime impact until a kernel "patch"
>--
>2.12.2
>
next prev parent reply other threads:[~2017-05-27 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 12:45 Miroslav Benes
2017-05-26 17:41 ` Josh Poimboeuf
2017-05-26 21:53 ` Jessica Yu [this message]
2017-05-26 22:28 ` Jiri Kosina
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=20170526215325.fa4qeyhstijgmb7e@jeyu \
--to=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=jmoreira@suse.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mmarek@suse.com \
--cc=pmladek@suse.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®