| /Documentation/filesystems/ |
| D | debugfs.rst | 5 DebugFS title
10 Debugfs exists as a simple way for kernel developers to make information
13 debugfs has no rules at all. Developers can put any information they want
14 there. The debugfs filesystem is also intended to not serve as a stable
17 even debugfs interfaces are best designed with the idea that they will need
20 Debugfs is typically mounted with a command like::
22 mount -t debugfs none /sys/kernel/debug
25 The debugfs root directory is accessible only to the root user by
29 Note that the debugfs API is exported GPL-only to modules.
31 Code using debugfs should include <linux/debugfs.h>. Then, the first order
[all …]
|
| D | api-summary.rst | 137 The debugfs filesystem
140 debugfs interface
143 .. kernel-doc:: fs/debugfs/inode.c
146 .. kernel-doc:: fs/debugfs/file.c
|
| /Documentation/admin-guide/mm/ |
| D | cma_debugfs.rst | 2 CMA Debugfs Interface
5 The CMA debugfs interface is useful to retrieve basic information out of the
8 Each CMA area represents a directory under <debugfs>/cma/, represented by
11 <debugfs>/cma/<cma_name>
21 echo 5 > <debugfs>/cma/<cma_name>/alloc
|
| D | shrinker_debugfs.rst | 2 Shrinker Debugfs Interface
5 Shrinker debugfs interface provides a visibility into the kernel memory
9 For each shrinker registered in the system a directory in **<debugfs>/shrinker/**
38 sb-debugfs-7 sb-proc-46 sb-tmpfs-40
|
| /Documentation/fault-injection/ |
| D | provoke-crashes.rst | 12 support via debugfs.
16 inserting the module, or through the debugfs interface.
36 These are numerous, and best queried directly from debugfs. Some
46 You can also induce failures by mounting debugfs and writing the type to
47 <debugfs>/provoke-crash/<crashpoint>. E.g.::
49 mount -t debugfs debugfs /sys/kernel/debug
|
| D | notifier-error-inject.rst | 16 This feature is controlled through debugfs interface
35 This feature is controlled through debugfs interface
53 This feature is controlled through debugfs interface
66 This feature is controlled through debugfs interface
|
| /Documentation/dev-tools/kunit/ |
| D | run_manual.rst | 52 debugfs chapter
55 KUnit can be accessed from userspace via the debugfs filesystem (See more
56 information about debugfs at Documentation/filesystems/debugfs.rst).
58 If ``CONFIG_KUNIT_DEBUGFS`` is enabled, the KUnit debugfs filesystem is
65 You can use debugfs to retrieve KUnit test results. The test results are
66 accessible from the debugfs filesystem in the following read-only file:
78 You can use the debugfs filesystem to trigger built-in tests to run after
84 echo "any string" > /sys/kernel/debugfs/kunit/<test_suite>/run
|
| /Documentation/gpu/amdgpu/ |
| D | ras.rst | 6 debugfs (for error injection).
8 RAS debugfs/sysfs Control and Error Injection Interfaces
12 :doc: AMDGPU RAS debugfs control interface
26 RAS EEPROM debugfs Interface
30 :doc: AMDGPU RAS debugfs EEPROM table reset interface
48 The test verifies the RAS feature enabled status and makes sure the necessary sysfs and debugfs fil…
|
| /Documentation/ABI/testing/ |
| D | debugfs-vfio | 5 Description: This debugfs file directory is used for debugging
14 Description: This debugfs file directory is used for debugging
16 The debugfs of each vfio device that supports live migration
|
| D | debugfs-intel-iommu | 85 table entries in debugfs. For legacy mode, it doesn't
230 page table by the debugfs file in the debugfs device
235 page table of specified pasid by the debugfs file in
236 the debugfs pasid directory. e.g.
|
| D | ppc-memtrace | 5 Description: This folder contains the relevant debugfs files for the
17 debugfs files will be created. Once memory is successfully
|
| /Documentation/translations/zh_TW/admin-guide/mm/damon/ |
| D | usage.rst | 31 - *debugfs interface.*
348 ``rm_contexts`` under its debugfs directory, ``<debugfs>/damon/``.
358 # cd <debugfs>/damon
372 # cd <debugfs>/damon
380 # cd <debugfs>/damon
408 # cd <debugfs>/damon
513 # cd <debugfs>/damon
529 # cd <debugfs>/damon
545 # cd <debugfs>/damon
561 將新上下文的名稱寫入 ``mk_contexts`` 文件，在 ``DAMON debugfs`` 目錄上創建一個該名稱的目錄。
[all …]
|
| /Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| D | usage.rst | 31 - *debugfs interface.*
348 ``rm_contexts`` under its debugfs directory, ``<debugfs>/damon/``.
358 # cd <debugfs>/damon
372 # cd <debugfs>/damon
380 # cd <debugfs>/damon
408 # cd <debugfs>/damon
513 # cd <debugfs>/damon
529 # cd <debugfs>/damon
545 # cd <debugfs>/damon
561 将新上下文的名称写入 ``mk_contexts`` 文件，在 ``DAMON debugfs`` 目录上创建一个该名称的目录。
[all …]
|
| /Documentation/translations/zh_TW/filesystems/ |
| D | debugfs.rst | 5 :Original: Documentation/filesystems/debugfs.rst
8 Debugfs title
33 mount -t debugfs none /sys/kernel/debug
37 和“ mode”掛載選項。請注意，debugfs API僅按照GPL協議導出到模塊。
39 使用debugfs的代碼應包含<linux/debugfs.h>。然後，首先是創建至少一個目錄來保存
|
| /Documentation/translations/zh_CN/filesystems/ |
| D | debugfs.rst | 5 :Original: Documentation/filesystems/debugfs.rst
8 Debugfs title
32 mount -t debugfs none /sys/kernel/debug
36 和“ mode”挂载选项。请注意，debugfs API仅按照GPL协议导出到模块。
38 使用debugfs的代码应包含<linux/debugfs.h>。然后，首先是创建至少一个目录来保存
|
| /Documentation/sound/cards/ |
| D | pcmtest.rst | 48 by writing the pattern to the debugfs file. There are pattern buffer debugfs entries
106 debugfs file for each channel). If the playback buffer content represents the looped
107 pattern, 'pc_test' debugfs entry is set into '1'. Otherwise, the driver sets it to '0'.
113 this functionality, we can trigger the reset ioctl and check the 'ioctl_test' debugfs
|
| /Documentation/arch/s390/ |
| D | s390dbf.rst | 19 debugfs filesystem.
61 the debugfs-filesystem. Under the toplevel directory "``s390dbf``" there is
63 corresponding component. The debugfs normally should be mounted to
72 a view can be inspected simply by reading the corresponding debugfs file.
80 The actual debug level can be changed with the help of the debugfs-filesystem
81 through writing a number string "x" to the ``level`` debugfs file which is
83 by using "-" on the ``level`` debugfs file.
193 Debugfs Interface
196 debugfs-files:
231 area (0...n) to the debugfs file "flush". When using "-" all debug areas
[all …]
|
| /Documentation/driver-api/hte/ |
| D | hte.rst | 57 HTE subsystem debugfs attributes
59 HTE subsystem creates debugfs attributes at ``/sys/kernel/debug/hte/``.
60 It also creates line/signal-related debugfs attributes at
|
| /Documentation/trace/ |
| D | mmiotrace.rst | 38 $ mount -t debugfs debugfs /sys/kernel/debug
50 Make sure debugfs is mounted to /sys/kernel/debug.
53 $ mount -t debugfs debugfs /sys/kernel/debug
|
| /Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 29 - *debugfs interface. (DEPRECATED!)*
607 debugfs Interface (DEPRECATED!)
614 DAMON debugfs interface is deprecated, so users should move to the
621 ``mk_contexts`` and ``rm_contexts`` under its debugfs directory,
622 ``<debugfs>/damon/``.
625 ``DEPRECATED`` is a read-only file for the DAMON debugfs interface deprecation
629 …DAMON debugfs interface is deprecated, so users should move to DAMON_SYSFS. If you cannot, please …
642 # cd <debugfs>/damon
660 # cd <debugfs>/damon
670 # cd <debugfs>/damon
[all …]
|
| /Documentation/hwmon/ |
| D | gigabyte_waterforce.rst | 19 well as coolant temperature. Also available through debugfs is the firmware version.
42 Debugfs entries
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-emif.rst | 57 Debugfs chapter
59 The driver creates two debugfs entries per device.
|
| /Documentation/driver-api/ |
| D | ntb.rst | 167 The Tool provides access through debugfs for reading, setting, and clearing the
172 Debugfs Files:
174 * *debugfs*/ntb\_tool/*hw*/
175 A directory in debugfs will be created for each
208 test client is interacted with through the debugfs filesystem:
210 * *debugfs*/ntb\_msi\_test/*hw*/
211 A directory in debugfs will be created for each
|
| /Documentation/networking/devlink/ |
| D | netdevsim.rst | 43 ``take_snapshot`` debugfs file is written to.
70 Rate nodes and their parameters are exposed in ``netdevsim`` debugfs in RO mode.
|
| /Documentation/dev-tools/ |
| D | gcov.rst | 6 is exported in gcov-compatible format via the "gcov" debugfs directory.
45 Profiling data will only become accessible once debugfs has been
48 mount -t debugfs none /sys/kernel/debug
92 The gcov kernel support creates the following files in debugfs:
117 with the unloaded module. This data remains available through debugfs.
|