| /linux/kernel/module/ |
| H A D | Kconfig | 2 menuconfig MODULES config 4 modules 7 Kernel modules are small pieces of compiled code which can 11 many parts of the kernel can be built as modules (by 18 modules_install" to put the modules under /lib/modules/ 24 if MODULES 34 modules. You don't need these options on production systems. 44 For example, size of all modules, average size, text size, a list 45 of failed modules and the size for each of those. For failed 46 modules we keep track of modules which failed due to either the [all …]
|
| H A D | stats.c | 64 * DOC: dup_failed_modules - tracks duplicate failed modules 66 * Linked list of modules which failed to be loaded because an already existing 79 * All virtual memory allocated to these failed modules will be freed with 82 * To help with this the dup_failed_modules allows us to track modules which 116 * * total_mod_size: total bytes ever used by all modules we've dealt with on 130 * promote it to be processed to be added to our @modules linked list. These 136 * add_unformed_module() will add a module to our &modules list and 137 * subsequent loads of modules with the same name will error out at the 140 * on layout_and_allocate() for modules already being processed. These 141 * duplicate failed modules are non-fatal, however they typically are [all …]
|
| H A D | procfs.c | 43 /* We don't know the usage count, or what modules are using. */ in print_unload_info() 48 /* Called by the /proc file system to return a list of modules. */ 52 return seq_list_start(&modules, *pos); in m_start() 57 return seq_list_next(p, &modules, pos); in m_next() 81 /* We always ignore unformed modules. */ in m_show() 149 proc_create("modules", 0, NULL, &modules_proc_ops); in proc_modules_init()
|
| /linux/scripts/package/ |
| H A D | kernel.spec | 40 Summary: Development package for building kernel modules to match the %{version} kernel 44 This package provides kernel headers and makefiles sufficient to build modules 55 This package provides debug information for the kernel image and modules from the 75 # later, we make all modules executable so that find-debuginfo.sh strips 82 find %{buildroot}/lib/modules/%{KERNELRELEASE} -name "*.ko" -type f \\\ 101 mkdir -p %{buildroot}/lib/modules/%{KERNELRELEASE} 102 cp $(%{make} %{makeflags} -s image_name) %{buildroot}/lib/modules/%{KERNELRELEASE}/vmlinuz 106 cp System.map %{buildroot}/lib/modules/%{KERNELRELEASE} 107 cp .config %{buildroot}/lib/modules/%{KERNELRELEASE}/config 109 %{make} %{makeflags} INSTALL_DTBS_PATH=%{buildroot}/lib/modules/%{KERNELRELEASE}/dtb dtbs_install [all …]
|
| H A D | builddeb | 39 rm -f "${pdir}/lib/modules/${KERNELRELEASE}/build" 43 mkdir -p "${pdir}/usr/lib/uml/modules" 44 mv "${pdir}/lib/modules/${KERNELRELEASE}" "${pdir}/usr/lib/uml/modules/${KERNELRELEASE}" 46 cp System.map "${pdir}/usr/lib/uml/modules/${KERNELRELEASE}/System.map" 111 # Parse modules.order directly because 'make modules_install' may sign, 112 # compress modules, and then run unneeded depmod. 116 dbg="${pdir}/usr/lib/debug/lib/modules/${KERNELRELEASE}/kernel/${mod}" 123 done < modules.order 129 mkdir -p ${pdir}/usr/lib/debug/lib/modules/${KERNELRELEASE}/ 130 cp vmlinux ${pdir}/usr/lib/debug/lib/modules/${KERNELRELEASE}/ [all …]
|
| /linux/scripts/ |
| H A D | Makefile.modinst | 3 # Installing modules 19 install-$(CONFIG_MODULES) += $(addprefix $(MODLIB)/, build modules.order) 27 $(MODLIB)/modules.order: modules.order FORCE 33 # Install modules.builtin(.modinfo,.ranges) even when CONFIG_MODULES is disabled. 34 install-y += $(addprefix $(MODLIB)/, modules.builtin modules.builtin.modinfo) 36 install-$(CONFIG_BUILTIN_MODULE_RANGES) += $(MODLIB)/modules.builtin.ranges 38 $(addprefix $(MODLIB)/, modules.builtin modules.builtin.modinfo modules.builtin.ranges): $(MODLIB)/… 43 modules := $(call read-file, modules.order) 62 modules := $(patsubst %.o, $(dst)/%.ko$(suffix-y), $(modules)) 63 install-$(CONFIG_MODULES) += $(modules) [all …]
|
| H A D | Makefile.modpost | 11 # d) modules.order, which lists all the modules 14 # 1) Find all modules listed in modules.order 32 # Step 4 is solely used to allow module versioning in external modules, 51 $(if $(KBUILD_NSDEPS),-d modules.nsdeps) \ 58 # 'make -i -k' ignores compile errors, and builds as many modules as possible. 63 # Read out modules.order to pass in modpost. 66 modpost-args += -T modules.order 67 modpost-deps += modules.order 106 output-symdump := modules-only.symvers 115 # set src + obj - they may be used in the modules's Makefile [all …]
|
| H A D | Makefile.vmlinux | 102 # modules.builtin.modinfo 121 targets += modules.builtin.modinfo 122 modules.builtin.modinfo: vmlinux.unstripped FORCE 125 # modules.builtin 128 __default: modules.builtin 130 # The second line aids cases where multiple modules share the same object. 138 targets += modules.builtin 139 modules.builtin: modules.builtin.modinfo FORCE 142 # modules [all...] |
| H A D | Makefile.modfinal | 13 # find all modules listed in modules.order 14 modules := $(call read-file, modules.order) 16 __modfinal: $(modules:%.o=%.ko) 65 targets += $(modules:%.o=%.ko) $(modules:%.o=%.mod.o) .module-common.o
|
| /linux/samples/ |
| H A D | Kconfig | 14 tristate "Build trace_events examples -- loadable modules only" 20 tristate "Build custom trace event example -- loadable modules only" 67 different kobject sample modules showing how to use kobjects, 73 tristate "Build kprobes examples -- loadable modules only" 76 This build several kprobes example modules. 79 tristate "Build kretprobes example -- loadable modules only" 87 This builds kernel hardware breakpoint example modules. 90 tristate "Build fprobe examples -- loadable modules only" 97 tristate "Build kfifo examples -- loadable modules only" 101 different kfifo sample modules showing how to use the [all …]
|
| /linux/Documentation/security/ |
| H A D | lsm.rst | 2 Linux Security Modules: General Security Hooks for Linux 33 framework could then be used by loadable kernel modules to implement any 37 The Linux Security Modules (LSM) project was started by WireX to develop 50 security modules. In particular, the LSM framework is primarily focused 51 on supporting access control modules, although future development is 54 the infrastructure to support security modules. The LSM framework is 63 It also adds functions for registering security modules. 65 of security modules that are active on the system. 69 the framework or by the individual security modules that use it. 87 ``include/linux/shm.h`` as appropriate) to allow the security modules to [all …]
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 63 To build these modules essentially amounts to just running "Make", 115 modules should have any business using this header. All external 130 pvrusb2-i2c-chips-\*.c - These modules implement the glue logic to 131 tie together and configure various I2C modules as they attach to 136 V4L, where we might encounter other possibly "challenging" modules 137 from ivtv or older kernel snapshots (or even the support modules 141 compatible commands to the I2C modules. It is here where state 143 commands that are in turn send to the various I2C modules. 146 compatible commands to the I2C modules. It is here where state 148 commands that are in turn send to the various I2C modules. [all …]
|
| /linux/Documentation/core-api/ |
| H A D | symbol-namespaces.rst | 17 kernel. As of today, modules that make use of symbols exported into namespaces, 22 limiting which modules are allowed to use these symbols. 84 intended for in-tree modules. 87 modules to access this symbol. Simple tail-globs are supported. 93 will limit usage of this symbol to modules whose name matches the given 99 In order to use symbols that are exported into namespaces, kernel modules need 121 Loading Modules that use namespaced Symbols 127 the kernel is to reject loading modules that don't specify sufficient imports. 129 allow loading of modules that don't satisfy this precondition, a configuration 155 in-tree modules:: [all …]
|
| /linux/drivers/iio/common/ |
| H A D | Makefile | 3 # Makefile for the IIO common modules. 4 # Common modules contains modules, which can be shared among multiple 5 # IIO modules. For example if the trigger processing is common for 6 # multiple IIO modules then this can be moved to a common module
|
| /linux/tools/testing/selftests/livepatch/ |
| H A D | README | 7 The test suite loads and unloads several test kernel modules to verify 26 The command above will compile all test modules and test programs, making them 32 Test kernel modules are built before running the livepatch selftests. The 33 modules are located under test_modules directory, and are built as out-of-tree 34 modules. This is specially useful since the same sources can be built and 36 compatible. The modules will be loaded by the test scripts using insmod.
|
| /linux/scripts/gdb/linux/ |
| H A D | modules.py | 23 return utils.gdb_eval_or_none("modules") is not None 27 modules = utils.gdb_eval_or_none("modules") 28 if modules is None: 33 for module in lists.list_for_each_entry(modules, module_ptr_type, "list"): 47 $lx_module("MODULE"): Given the name MODULE, iterate over all loaded modules 66 """List currently loaded modules."""
|
| /linux/ |
| H A D | .gitignore | 59 modules.order 65 /modules-only.symvers 75 /modules.builtin 76 /modules.builtin.modinfo 77 /modules.builtin.ranges 78 /modules.nsdeps
|
| H A D | Makefile | 142 $(error building multiple external modules is not supported)) 192 # source directory or kernel build directory), external modules 698 @if [ -f $(srcroot)/modules.order ]; then \ 754 # but instead __all depend on modules 759 __all: modules 770 # If we have only "make modules", don't compile built-in objects. 771 ifeq ($(MAKECMDGOALS),modules) 775 # If we have "make <whatever> modules", compile modules 777 # Just "make" or "make all" shall build modules a 1629 modules: vmlinux global() target 1632 modules: modules_prepare global() target 1990 modules modules_install: __external_modules_error global() target 2030 modules: modpost global() target 2041 modules: global() target [all...] |
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-taos-evm.rst | 7 This is a driver for the evaluation modules for TAOS I2C/SMBus chips. 8 The modules include an SMBus master with limited capabilities, which can 9 be controlled over the serial port. Virtually all evaluation modules 38 modules: 48 practice, as these modules are meant for evaluation and testing only.
|
| /linux/Documentation/userspace-api/ |
| H A D | lsm.rst | 6 Linux Security Modules 12 Linux security modules (LSM) provide a mechanism to implement 15 The various security modules may support any of these attributes: 20 This is supported by the SELinux, Smack and AppArmor security modules. 27 This is supported by the SELinux and AppArmor security modules. 43 This is supported by the SELinux and AppArmor security modules.
|
| /linux/drivers/mfd/ |
| H A D | janz-cmodio.c | 26 /* Maximum number of MODULbus modules on a CMOD-IO carrier board */ 31 static char *modules[CMODIO_MAX_MODULES] = { variable 35 module_param_array(modules, charp, &num_modules, S_IRUGO); 36 MODULE_PARM_DESC(modules, "MODULbus modules attached to the carrier board"); 126 name = modules[i]; in cmodio_probe_submodules() 135 /* print an error message if no modules were probed */ in cmodio_probe_submodules() 137 dev_err(&priv->pdev->dev, "no MODULbus modules specified, " in cmodio_probe_submodules() 138 "please set the ``modules'' kernel " in cmodio_probe_submodules()
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | imx7ulp-scg-clock.yaml | 7 title: Freescale i.MX7ULP System Clock Generation (SCG) modules Clock Controller 14 Clock Generation (SCG) modules, Peripheral Clock Control (PCC) 15 modules, and Core Mode Controller (CMC)1 blocks 23 M4 clock management consists of SCG0, PCC0, PCC1, and CMC0 modules. 24 A7 clock management consists of SCG1, PCC2, PCC3, and CMC1 modules.
|
| /linux/Documentation/livepatch/ |
| H A D | module-elf-format.rst | 5 This document outlines the ELF format requirements that livepatch modules must follow. 31 preserved for livepatch modules (see section 5). Livepatch manages its own 43 affect modules not yet loaded at patch module load time (e.g. a patch to a 59 Livepatch modules are required to have the "livepatch" modinfo attribute. 62 Livepatch modules can be identified by users by using the 'modinfo' command 64 used by the kernel module loader to identify livepatch modules. 84 relocations to modules as well as to the kernel (vmlinux) at the 98 Since ELF information is preserved for livepatch modules (see Section 5), a 146 module that patches vmlinux and modules 9p, btrfs, ext4:** 205 loader can identify and ignore them. Livepatch modules keep these symbols [all …]
|
| /linux/scripts/clang-tools/ |
| H A D | gen_compile_commands.py | 60 '(files should be *.o, *.a, or modules.order). ' 128 """Generate the iterator of .cmd files associated with the modules.order. 130 Parse the given modules.order, and yield every .cmd file used to build the 131 contained modules. 134 modorder: The modules.order file to parse 201 # Modules are listed in modules.order. 206 elif path.endswith('modules.order'):
|
| /linux/Documentation/power/ |
| H A D | basic-pm-debugging.rst | 131 unloaded all modules. In that case, you may want to look in your kernel 132 configuration for the drivers that can be compiled as modules (and test again 133 with these drivers compiled as modules). You may also try to use some special 164 can try to compile more drivers as modules, so that they can be tested 166 find it by loading a half of the modules you normally use and binary searching 168 - if there are n modules loaded and the attempt to suspend and resume fails, 169 unload n/2 of the modules and try again (that would probably involve rebooting 171 - if there are n modules loaded and the attempt to suspend and resume succeeds, 172 load n/2 modules more and try again. 207 configuration and compiling more drivers as modules is not practical or some [all …]
|