From: Miroslav Benes <mbenes@suse.cz>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: live-patching@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jmoreira@suse.de
Subject: Re: [PATCH RFC 0/2] livepatch: patch creation tooling proposal
Date: Wed, 1 Mar 2017 11:53:05 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.20.1703011147250.5005@pobox.suse.cz> (raw)
In-Reply-To: <cover.1477578530.git.jpoimboe@redhat.com>
On Thu, 27 Oct 2016, Josh Poimboeuf wrote:
> TODO:
> - support .klp.arch.objname..altinstructions/parainstructions
> - split up the patches better
> - patch creation documentation
> - more tooling support for detecting missing relocations? or
> automatically converting them if a sympos isn't needed?
Hi Josh,
I owe you (and others) update...
- I split up the patch set (but it is still not nice enough)
- Konstantin's changes are merged
- I removed a dependency on modinfo and made some changes
But much more importantly. Joao (CC'd) took it over from now on. He can
help us with userspace tooling in the future too. I am sure there is
going to be faster progress with it now, because something has always
distracted me recently :/ and it is important to finish it.
Regards,
Miroslav
prev parent reply other threads:[~2017-03-01 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 14:35 [PATCH RFC 0/2] livepatch: patch creation tooling proposal Josh Poimboeuf
2016-10-27 14:35 ` [PATCH RFC 1/2] livepatch: add klp-convert tool and integrate with module build Josh Poimboeuf
2016-12-17 13:08 ` [PATCH] livepatch: fixup klp-convert tool integration Konstantin Khlebnikov
2016-12-19 14:29 ` Miroslav Benes
2016-10-27 14:35 ` [PATCH RFC 2/2] livepatch: update sample module to use klp relocations Josh Poimboeuf
2016-11-10 15:36 ` [PATCH RFC 0/2] livepatch: patch creation tooling proposal Josh Poimboeuf
2016-11-10 15:48 ` Miroslav Benes
2016-11-10 15:54 ` Miroslav Benes
2016-11-10 16:10 ` Josh Poimboeuf
2017-03-01 10:53 ` Miroslav Benes [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=alpine.LSU.2.20.1703011147250.5005@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=jmoreira@suse.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).