From: Miroslav Benes <mbenes@suse.cz>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH v6 1/3] livepatch: add (un)patch callbacks
Date: Wed, 18 Oct 2017 15:05:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.1710181504360.8638@san.suse.cz> (raw)
In-Reply-To: <1507921723-1996-2-git-send-email-joe.lawrence@redhat.com>
On Fri, 13 Oct 2017, Joe Lawrence wrote:
> Provide livepatch modules a klp_object (un)patching notification
> mechanism. Pre and post-(un)patch callbacks allow livepatch modules to
> setup or synchronize changes that would be difficult to support in only
> patched-or-unpatched code contexts.
>
> Callbacks can be registered for target module or vmlinux klp_objects,
> but each implementation is klp_object specific.
>
> - Pre-(un)patch callbacks run before any (un)patching transition
> starts.
>
> - Post-(un)patch callbacks run once an object has been (un)patched and
> the klp_patch fully transitioned to its target state.
>
> Example use cases include modification of global data and registration
> of newly available services/handlers.
>
> See Documentation/livepatch/callbacks.txt for details and
> samples/livepatch/ for examples.
>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
Acked-by: Miroslav Benes <mbenes@suse.cz>
Miroslav
next prev parent reply other threads:[~2017-10-18 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 19:08 [PATCH v6 0/3] livepatch callbacks Joe Lawrence
2017-10-13 19:08 ` [PATCH v6 1/3] livepatch: add (un)patch callbacks Joe Lawrence
2017-10-18 13:05 ` Miroslav Benes [this message]
2017-10-13 19:08 ` [PATCH v6 2/3] livepatch: move transition "complete" notice into klp_complete_transition() Joe Lawrence
2017-10-13 19:08 ` [PATCH v6 3/3] livepatch: add transition notices Joe Lawrence
2017-10-17 23:33 ` [PATCH v6 0/3] livepatch callbacks Josh Poimboeuf
2017-10-19 8:14 ` 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=alpine.LSU.2.21.1710181504360.8638@san.suse.cz \
--to=mbenes@suse.cz \
--cc=chris.j.arges@canonical.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--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®