| /kernel/linux/linux-6.6/kernel/module/ |
| D | Kconfig | 2 menuconfig MODULES config
4 modules
6 Kernel modules are small pieces of compiled code which can
10 many parts of the kernel can be built as modules (by
17 modules_install" to put the modules under /lib/modules/
23 if MODULES
33 modules. You don't need these options on production systems.
43 For example, size of all modules, average size, text size, a list
44 of failed modules and the size for each of those. For failed
45 modules we keep track of modules which failed due to either the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | module-signing.rst | 10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
21 The kernel module signing facility cryptographically signs modules during
23 allows increased kernel security by disallowing the loading of unsigned modules
24 or modules signed with an invalid key. Module signing increases security by
49 (1) :menuselection:`Require modules to be validly signed`
55 If this is off (ie. "permissive"), then modules for which the key is not
56 available and modules that are unsigned are permitted, but the kernel will
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | module-signing.rst | 10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
21 The kernel module signing facility cryptographically signs modules during
23 allows increased kernel security by disallowing the loading of unsigned modules
24 or modules signed with an invalid key. Module signing increases security by
49 (1) :menuselection:`Require modules to be validly signed`
55 If this is off (ie. "permissive"), then modules for which the key is not
56 available and modules that are unsigned are permitted, but the kernel will
[all …]
|
| /kernel/uniproton/build/uniproton_config/config_armv8_raspi4/ |
| D | defconfig | 7 # Arch Modules Configuration
37 # Core Modules Configuration
41 # IPC Modules Configuration
55 # Kernel Modules Configuration
59 # IRQ Modules Configuration
67 # Exc Modules Configuration
92 # Timer Modules Configuration
97 # MM Modules Configuration
101 # OM Modules Configuration
120 # security Modules Configuration
[all …]
|
| /kernel/uniproton/build/uniproton_config/config_armv8_hi3093/ |
| D | defconfig | 7 # Arch Modules Configuration
37 # Core Modules Configuration
41 # IPC Modules Configuration
55 # Kernel Modules Configuration
59 # IRQ Modules Configuration
67 # Exc Modules Configuration
92 # Timer Modules Configuration
97 # MM Modules Configuration
101 # OM Modules Configuration
120 # security Modules Configuration
[all …]
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | modules.rst | 2 Building External Modules
10 === 2 How to Build External Modules
19 --- 3.4 Building Multiple Modules
28 --- 6.1 Symbols From the Kernel (vmlinux + modules)
29 --- 6.2 Symbols and External Modules
39 "kbuild" is the build system used by the Linux kernel. Modules must use
41 to pick up the right flags to "gcc." Functionality for building modules
43 either is similar, and all modules are initially developed and built
47 in building out-of-tree (or "external") modules. The author of an
54 2. How to Build External Modules
[all …]
|
| D | kbuild.rst | 9 modules.order
11 This file records the order in which modules appear in Makefiles. This
13 multiple modules.
15 modules.builtin
17 This file lists all modules that are built into the kernel. This is used
20 modules.builtin.modinfo
22 This file contains modinfo from all modules that are built into the kernel.
37 Additional options to the assembler (for built-in and modules).
41 Additional assembler options for modules.
49 Additional options to the C compiler (for built-in and modules).
[all …]
|
| /kernel/linux/linux-6.6/Documentation/kbuild/ |
| D | modules.rst | 2 Building External Modules
10 === 2 How to Build External Modules
19 --- 3.4 Building Multiple Modules
28 --- 6.1 Symbols From the Kernel (vmlinux + modules)
29 --- 6.2 Symbols and External Modules
39 "kbuild" is the build system used by the Linux kernel. Modules must use
41 to pick up the right flags to "gcc." Functionality for building modules
43 either is similar, and all modules are initially developed and built
47 in building out-of-tree (or "external") modules. The author of an
54 2. How to Build External Modules
[all …]
|
| D | kbuild.rst | 9 modules.order
11 This file records the order in which modules appear in Makefiles. This
13 multiple modules.
15 modules.builtin
17 This file lists all modules that are built into the kernel. This is used
20 modules.builtin.modinfo
22 This file contains modinfo from all modules that are built into the kernel.
37 Additional options to the assembler (for built-in and modules).
41 Additional assembler options for modules.
49 Additional options to the C compiler (for built-in and modules).
[all …]
|
| /kernel/uniproton/build/uniproton_config/config_m4/ |
| D | defconfig | 7 # Arch Modules Configuration
32 # Core Modules Configuration
36 # IPC Modules Configuration
53 # Kernel Modules Configuration
57 # IRQ Modules Configuration
65 # Exc Modules Configuration
86 # Timer Modules Configuration
91 # MM Modules Configuration
95 # OM Modules Configuration
114 # security Modules Configuration
[all …]
|
| /kernel/linux/linux-5.10/samples/ |
| D | Kconfig | 14 tristate "Build trace_events examples -- loadable modules only"
17 This build trace event example modules.
45 different kobject sample modules showing how to use kobjects,
51 tristate "Build kprobes examples -- loadable modules only"
54 This build several kprobes example modules.
57 tristate "Build kretprobes example -- loadable modules only"
65 This builds kernel hardware breakpoint example modules.
68 tristate "Build kfifo examples -- loadable modules only"
72 different kfifo sample modules showing how to use the
78 tristate "Build kdb command example -- loadable modules only"
[all …]
|
| /kernel/linux/linux-6.6/scripts/ |
| 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) even when CONFIG_MODULES is disabled.
34 install-y += $(addprefix $(MODLIB)/, modules.builtin modules.builtin.modinfo)
36 $(addprefix $(MODLIB)/, modules.builtin modules.builtin.modinfo): $(MODLIB)/%: % FORCE
41 modules := $(call read-file, $(MODORDER))
58 modules := $(patsubst $(extmod_prefix)%.o, $(dst)/%.ko$(suffix-y), $(modules))
59 install-$(CONFIG_MODULES) += $(modules)
72 # INSTALL_MOD_STRIP, if defined, will cause modules to be stripped after they
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/ |
| D | Makefile | 32 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/inc
33 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/freesync
34 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/color
35 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/info_packet
36 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/power
40 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/hdcp
46 DAL_LIBS = amdgpu_dm dc modules/freesync modules/color modules/info_packet modules/power dmub/src
49 DAL_LIBS += modules/hdcp
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/amd/display/ |
| D | Makefile | 32 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/inc
33 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/freesync
34 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/color
35 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/info_packet
36 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/power
39 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/hdcp
44 DAL_LIBS = amdgpu_dm dc modules/freesync modules/color modules/info_packet modules/power dmub/src
46 DAL_LIBS += modules/hdcp
|
| /kernel/linux/linux-6.6/scripts/package/ |
| D | kernel.spec | 41 Summary: Development package for building kernel modules to match the %{version} kernel
45 This package provides kernel headers and makefiles sufficient to build modules
58 mkdir -p %{buildroot}/lib/modules/%{KERNELRELEASE}
59 cp $(%{make} %{makeflags} -s image_name) %{buildroot}/lib/modules/%{KERNELRELEASE}/vmlinuz
62 cp System.map %{buildroot}/lib/modules/%{KERNELRELEASE}
63 cp .config %{buildroot}/lib/modules/%{KERNELRELEASE}/config
64 ln -fns /usr/src/kernels/%{KERNELRELEASE} %{buildroot}/lib/modules/%{KERNELRELEASE}/build
74 /usr/bin/kernel-install add %{KERNELRELEASE} /lib/modules/%{KERNELRELEASE}/vmlinuz
77 if ! cmp --silent "/lib/modules/%{KERNELRELEASE}/${file}" "/boot/${file}-%{KERNELRELEASE}"; then
78 cp "/lib/modules/%{KERNELRELEASE}/${file}" "/boot/${file}-%{KERNELRELEASE}"
[all …]
|
| /kernel/linux/linux-5.10/scripts/ |
| 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,
37 # KBUILD_MODPOST_NOFINAL can be set to skip the final link of modules.
71 output-symdump := modules-only.symvers
79 Module.symvers: vmlinux.symvers modules-only.symvers FORCE
88 # set src + obj - they may be used in the modules's Makefile
95 # modpost option for external modules
103 # modpost options for modules (both in-kernel and external)
109 # 'make -i -k' ignores compile errors, and builds as many modules as possible.
[all …]
|
| D | Makefile.modinst | 3 # Installing modules
11 modules := $(sort $(shell cat $(if $(KBUILD_EXTMOD),$(KBUILD_EXTMOD)/)modules.order))
13 PHONY += $(modules)
14 __modinst: $(modules)
17 # Don't stop modules_install if we can't sign external modules.
26 # Modules built outside the kernel source tree go into extra by default
32 $(modules):
|
| D | Makefile.modsign | 3 # Signing modules
11 modules := $(sort $(shell cat modules.order))
13 PHONY += $(modules)
14 __modsign: $(modules)
20 # Modules built outside the kernel source tree go into extra by default
26 $(modules):
|
| /kernel/linux/linux-6.6/samples/ |
| 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 …]
|
| /kernel/linux/linux-5.10/scripts/package/ |
| D | builddeb | 90 mkdir -p $pdir/lib/modules/$version/
91 ln -s /usr/src/linux-headers-$version $pdir/lib/modules/$version/build
142 …mkdir -p "$tmpdir/usr/lib/uml/modules/$version" "$tmpdir/usr/bin" "$tmpdir/usr/share/doc/$packagen…
143 cp System.map "$tmpdir/usr/lib/uml/modules/$version/System.map"
161 rm -f "$tmpdir/lib/modules/$version/build"
162 rm -f "$tmpdir/lib/modules/$version/source"
164 mv "$tmpdir/lib/modules/$version"/* "$tmpdir/usr/lib/uml/modules/$version/"
165 rmdir "$tmpdir/lib/modules/$version"
168 for module in $(find $tmpdir/lib/modules/ -name *.ko -printf '%P\n'); do
169 module=lib/modules/$module
[all …]
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/security/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/media/platform/davinci/ |
| D | Kconfig | 16 be two modules called vpif.ko and vpif_display.ko
31 be two modules called vpif.ko and vpif_capture.ko
41 with decoder modules such as TVP5146 over BT656 or
47 be three modules called vpfe_capture.ko, vpss.ko and dm644x_ccdc.ko
57 with decoder modules such as TVP5146 over BT656 or
63 be three modules called vpfe_capture.ko, vpss.ko and dm355_ccdc.ko
77 be three modules called vpfe_capture.ko, vpss.ko and isif.ko
91 be five modules created called vpss.ko, vpbe.ko, vpbe_osd.ko,
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/LSM/ |
| D | index.rst | 8 loadable kernel modules. Instead, they are selectable at build-time via
20 The Linux capabilities modules will always be included. This may be
21 followed by any number of "minor" modules and at most one "major" module.
25 A list of the active security modules can be found by reading
29 be first, followed by any "minor" modules (e.g. Yama) and then
32 Process attributes associated with "major" security modules should
37 in ``/proc/.../attr`` remain as legacy interfaces for modules that provide
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/LSM/ |
| D | index.rst | 8 loadable kernel modules. Instead, they are selectable at build-time via
20 The Linux capabilities modules will always be included. This may be
21 followed by any number of "minor" modules and at most one "major" module.
25 A list of the active security modules can be found by reading
29 be first, followed by any "minor" modules (e.g. Yama) and then
32 Process attributes associated with "major" security modules should
37 in ``/proc/.../attr`` remain as legacy interfaces for modules that provide
|