On Wed, 9 Mar 2016, Petr Mladek wrote: > LivePatch framework deserves some documentation, definitely. > This is an attempt to provide some basic info. I hope that > it will be useful for both LivePatch producers and also > potential developers of the framework itself. Thanks for starting the efforts; this is really needed if we want the infrastructure to be used also by someone else than its developers :) [ ... snip ... ] > +7. Limitations > +============== Miroslav Benes, who is working on creating the actual patches we are shipping for our kernels, should already have a decent cheat-sheet regarding things that the patch author should be extra careful when creating a patch (inlining and other gcc optimizations such as isra, functions that use switch_to(), percpu, ...). I am not really sure whether these should go to limitations, or maybe they'd better be placed into a separate chapter, but I'd really like to see it included. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
