From: Li Zefan <lizefan@huawei.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] [TECH TOPIC] live kernel patching
Date: Sun, 4 May 2014 16:34:00 +0800 [thread overview]
Message-ID: <5365FB78.8020901@huawei.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1405022123320.29834@pobox.suse.cz>
On 2014/5/3 3:42, Jiri Kosina wrote:
> Runtime/live kernel patching is becoming a topic these days. There are
> several parallel implementations currently evolving in parallel (kpatch,
> kgraft, criu-based solution, ksplice to some extent), all of them having
> their pros and cons.
>
> It's clear that what is going to get merged at the end of the day would
> have to be some super-position of the currently existing solutions.
>
> Finding a reasonable compromise might be challenging. Having discussion
> between the groups working on those solutions (tech topic) and with
> "general maintainer audience" to face the flame^W^W^Wobtain feedback
> (core topic) would be very valuable step in converging to unified
> solution.
>
> Suggested participants: see the list of "competing" projects above
>
Thanks for working on KGraft!
In Huawei we want to use live patching, but we're conservative, so we really
want to see a mainline solution.
next prev parent reply other threads:[~2014-05-04 8:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 19:42 Jiri Kosina
2014-05-02 21:17 ` James Bottomley
2014-05-04 8:34 ` Li Zefan [this message]
2014-05-05 14:00 ` Chris Mason
2014-05-05 21:58 ` Andy Lutomirski
2014-05-05 22:08 ` Jiri Kosina
2014-05-06 13:17 ` James Bottomley
2014-05-06 13:23 ` Pavel Emelyanov
2014-05-06 14:07 ` Chris Mason
2014-05-06 15:44 ` Pavel Emelyanov
2014-05-06 17:02 ` Chris Mason
2014-05-06 1:33 ` Kees Cook
2014-05-06 7:05 ` Jiri Kosina
2014-05-06 13:16 ` Dave Jones
2014-05-06 13:23 ` Jiri Kosina
2014-05-06 13:18 ` Kees Cook
2014-05-06 13:28 ` James Bottomley
2014-05-06 13:41 ` Kees Cook
2014-05-06 17:11 ` Mimi Zohar
2014-05-06 18:34 ` James Bottomley
2014-05-06 12:30 ` Masami Hiramatsu
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=5365FB78.8020901@huawei.com \
--to=lizefan@huawei.com \
--cc=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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