lkml.org 
[lkml]   [2007]   [Jul]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectSection mismatch warnings for early memory allocations
Date
From
Checking for section mismatches across all of vmlinux is kicking
out a bunch of new warnings. Many of them real, but I have a
few from routines like this:

foo(...)
{
static int first_time = 1;

if (first_time) {
all_i_need = alloc_bootmem(NR_CPUS * xxx);
first_time = 0;
}
... use smp_processor_id() to use pre-allocated memory ...
}


Now this is safe, since the first call to foo is made when alloc_bootmem
is still available. But it kicks out a "Section mismatch" warning since
a non __init routine (foo) is calling an __init one.

Any suggestions on how to tell modpost that this is safe?

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-07-23 18:25    [W:0.081 / U:0.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site