lkml.org 
[lkml]   [2013]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Status of __cpuinit removal

* Paul Gortmaker <paul.gortmaker@windriver.com> wrote:

> As some of you are probably aware, a decision to remove __cpuinit and
> variants was made, since the cost/complexity outweighs the amount of
> memory reclaim that it provides. Details of that decision are at:
>
> https://lkml.org/lkml/2013/5/20/589
>
> It seems that the suggestion to do this was partly motivated by the
> fix in commit 5e427ec2 ("x86: Fix bit corruption at CPU resume time").
> It is a good example of the nasty type of bugs that can be created
> with improper use of the various types of __init prefixes.
>
> I have created a patch queue against the latest linux-next tree (Jun20)
> that removes all the variants of __cpuinit and the asm __CPUINIT variants,
> and the surrounding infrastructure for section handling of it. There
> are no Kconfig changes; this is complex enough. We can independently
> revisit later whether keeping CPU_HOTPLUG makes sense or not.
>
> I have done this in 33 commits. I decided against a giant monolithic
> patch for several reasons:

[...]

> scripts/mod/modpost.c | 52 ++++------------------
> 307 files changed, 895 insertions(+), 1036 deletions(-)

Cool, thanks Paul for addressing all this!

Thanks,

Ingo


\
 
 \ /
  Last update: 2013-06-23 13:01    [W:0.061 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site