| 1 | The /sys/module tree consists of the following structure: |
| 2 | |
| 3 | What: /sys/module/<MODULENAME> |
| 4 | Description: |
| 5 | The name of the module that is in the kernel. This |
| 6 | module name will always show up if the module is loaded as a |
| 7 | dynamic module. If it is built directly into the kernel, it |
| 8 | will only show up if it has a version or at least one |
| 9 | parameter. |
| 10 | |
| 11 | Note: The conditions of creation in the built-in case are not |
| 12 | by design and may be removed in the future. |
| 13 | |
| 14 | What: /sys/module/<MODULENAME>/parameters |
| 15 | Description: |
| 16 | This directory contains individual files that are each |
| 17 | individual parameters of the module that are able to be |
| 18 | changed at runtime. See the individual module |
| 19 | documentation as to the contents of these parameters and |
| 20 | what they accomplish. |
| 21 | |
| 22 | Note: The individual parameter names and values are not |
| 23 | considered stable, only the fact that they will be |
| 24 | placed in this location within sysfs. See the |
| 25 | individual driver documentation for details as to the |
| 26 | stability of the different parameters. |
| 27 | |
| 28 | What: /sys/module/<MODULENAME>/refcnt |
| 29 | Description: |
| 30 | If the module is able to be unloaded from the kernel, this file |
| 31 | will contain the current reference count of the module. |
| 32 | |
| 33 | Note: If the module is built into the kernel, or if the |
| 34 | CONFIG_MODULE_UNLOAD kernel configuration value is not enabled, |
| 35 | this file will not be present. |
| 36 | |
| 37 | What: /sys/module/<MODULENAME>/srcversion |
| 38 | Date: Jun 2005 |
| 39 | Description: |
| 40 | If the module source has MODULE_VERSION, this file will contain |
| 41 | the checksum of the source code. |
| 42 | |
| 43 | What: /sys/module/<MODULENAME>/version |
| 44 | Date: Jun 2005 |
| 45 | Description: |
| 46 | If the module source has MODULE_VERSION, this file will contain |
| 47 | the version of the source code. |