Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933229AbcCOB1L (ORCPT ); Mon, 14 Mar 2016 21:27:11 -0400 Received: from mx2.suse.de ([195.135.220.15]:60827 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750912AbcCOB1I (ORCPT ); Mon, 14 Mar 2016 21:27:08 -0400 Date: Tue, 15 Mar 2016 02:27:02 +0100 (CET) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: Michael Ellerman cc: linuxppc-dev@ozlabs.org, pmladek@suse.com, jeyu@redhat.com, linux-kernel@vger.kernel.org, rostedt@goodmis.org, kamalesh@linux.vnet.ibm.com, duwe@lst.de, live-patching@vger.kernel.org, mbenes@suse.cz Subject: Re: [v3,1/8] powerpc: Create a helper for getting the kernel toc value In-Reply-To: <3qNsms00H7z9snl@ozlabs.org> Message-ID: References: <3qNsms00H7z9snl@ozlabs.org> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1258 Lines: 32 On Mon, 14 Mar 2016, Michael Ellerman wrote: > > Move the logic to work out the kernel toc pointer into a header. This is > > a good cleanup, and also means we can use it elsewhere in future. > > > > Reviewed-by: Kamalesh Babulal > > Reviewed-by: Torsten Duwe > > Signed-off-by: Michael Ellerman > > Tested-by: Kamalesh Babulal > > Series applied to powerpc next. > > https://git.kernel.org/powerpc/c/a5cab83cd3d2d75d3893276cb5 Thanks Michael; this is an excellent basis for ppc live patching, but FYI I am not merging that one to my tree just yet. The solution (*) for functions with non-trivial argument list is not there yet, and it's my requirement for this to be taken care of in a way that's not prone to easily-done human errors on the patch-producer side. (*) both "making it work" or "making it so broken that it's guaranteed that noone would ever produce a patch that brings the kernel down" is okay, but I really don't feel that just documenting the limitation is sufficient and safe in this case; kudos to Torsten here for idenfitfying the problem before it actually became The Problem Thanks, -- Jiri Kosina SUSE Labs