From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [RFC][PATCH] extable: Make sure all archs define _sdata Date: Fri, 20 May 2011 11:04:31 -0400 Message-ID: <1305903871.1465.22.camel@gandalf.stny.rr.com> References: <1305855298.1465.19.camel@gandalf.stny.rr.com> <4DD67A90.7010908@twiddle.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4DD67A90.7010908@twiddle.net> Sender: linux-alpha-owner@vger.kernel.org To: Richard Henderson Cc: LKML , Ingo Molnar , Ivan Kokshaysky , Matt Turner , linux-alpha@vger.kernel.org, Hirokazu Takata , Geert Uytterhoeven , Roman Zippel , linux-m68k@vger.kernel.org, Ralf Baechle , Kyle McMartin , Helge Deller , "JamesE.J.Bottomley" List-Id: linux-m68k@vger.kernel.org On Fri, 2011-05-20 at 07:28 -0700, Richard Henderson wrote: > Although I suppose if we're supposedly standardizing on _sdata, > the two uses of _data in arch/alpha/mm/ could be transitioned. > If we start getting more uses of _sdata, then perhaps this would be a good idea. Currently I only need it to know if a pointer passed in to one of my functions can be freed or not. If the pointer is pointing to a struct in the core kernel data, it is safe from being freed. Anything else will need the extra work to keep it safe (rcu logic and such) and takes a path with a bit more overhead. Thanks! -- Steve