module_init剖析

最新推荐文章于 2023-09-13 11:36:45 发布

小小波浪vante

最新推荐文章于 2023-09-13 11:36:45 发布

阅读量276

点赞数

分类专栏：内核笔记文章标签： linux

本文链接：https://blog.csdn.net/Target__Me/article/details/121850882

版权

这篇博客深入探讨了Linux内核中的module_init、__initcall及do_initcalls过程，揭示了它们在模块加载时的执行顺序，数值越小的initcall优先级越高。

摘要由CSDN通过智能技术生成

module_init/module_exit

 include/linux/module.h
 /**
 * module_init() - driver initialization entry point
 * @x: function to be run at kernel boot time or module insertion
 *
 * module_init() will either be called during do_initcalls() (if
 * builtin) or at module insertion time (if a module).  There can only
 * be one per module.
 */
#define module_init(x)	__initcall(x);

/**
 * module_exit() - driver exit entry point
 * @x: function to be run when driver is removed
 *
 * module_exit() will wrap the driver clean-up code
 * with cleanup_module() when used with rmmod when
 * the driver is a module.  If the driver is statically
 * compiled into the kernel, module_exit() has no effect.
 * There can only be one per module.
 */
#define module_exit(x)	__exitcall(x);

__initcall(x)

include/linux/init.h
/*
 * A "pure" initcall has no dependencies on anything else, and purely
 * initializes variables that couldn't be statically initialized.
 *
 * This only exists for built-in code, not for modules.
 * Keep main.c:initcall_level_names[] in sync.
 */
#define pure_initcall(fn)