diff options
author | Paul Gortmaker <paul.gortmaker@windriver.com> | 2014-01-15 16:55:18 +1100 |
---|---|---|
committer | Stephen Rothwell <sfr@canb.auug.org.au> | 2014-01-15 16:55:18 +1100 |
commit | cb9ac9719363fd6a986d97a5c461848d7bd6623a (patch) | |
tree | 4bf19a0c9eb747162df4e367c8ff5d4264e4316e /mm | |
parent | 99a8d7a39ebf45a68a802c4dc165a0f5dec4955a (diff) |
mm/mm_init.c: make creation of the mm_kobj happen earlier than device_initcall
The use of __initcall is to be eventually replaced by choosing one from
the prioritized groupings laid out in init.h header:
pure_initcall 0
core_initcall 1
postcore_initcall 2
arch_initcall 3
subsys_initcall 4
fs_initcall 5
device_initcall 6
late_initcall 7
In the interim, all __initcall are mapped onto device_initcall, which as
can be seen above, comes quite late in the ordering.
Currently the mm_kobj is created with __initcall in mm_sysfs_init(). This
means that any other initcalls that want to reference the mm_kobj have to
be device_initcall (or later), otherwise we will for example, trip the
BUG_ON(!kobj) in sysfs's internal_create_group(). This unfairly restricts
those users; for example something that clearly makes sense to be an
arch_initcall will not be able to choose that.
However, upon examination, it is only this way for historical reasons
(i.e. simply not reprioritized yet). We see that sysfs is ready quite
earlier in init/main.c via:
vfs_caches_init
|_ mnt_init
|_ sysfs_init
well ahead of the processing of the prioritized calls listed above.
So we can recategorize mm_sysfs_init to be a pure_initcall, which in turn
allows any mm_kobj initcall users a wider range (1 --> 7) of initcall
priorities to choose from.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm')
-rw-r--r-- | mm/mm_init.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/mm/mm_init.c b/mm/mm_init.c index 68562e92d50c..857a6434e3a5 100644 --- a/mm/mm_init.c +++ b/mm/mm_init.c @@ -202,5 +202,4 @@ static int __init mm_sysfs_init(void) return 0; } - -__initcall(mm_sysfs_init); +pure_initcall(mm_sysfs_init); |