Lines Matching refs:debugfs

6 debugfs has no rules at all.  Developers can put any information they want
7 there.  The debugfs filesystem is also intended to not serve as a stable
10 even debugfs interfaces are best designed with the idea that they will need
15     mount -t debugfs none /sys/kernel/debug
18 The debugfs root directory is accessible only to the root user by
22 Note that the debugfs API is exported GPL-only to modules.
24 Code using debugfs should include <linux/debugfs.h>.  Then, the first order
26 debugfs files:
32 created in the debugfs root.  On success, the return value is a struct
36 kernel has been built without debugfs support and none of the functions
39 The most general way to create a file within a debugfs directory is with:
52 error, or ERR_PTR(-ENODEV) if debugfs support is missing.
66 actually necessary; the debugfs code provides a number of helper functions
102 As might be expected, this function will create a debugfs file to represent
105 Boolean values can be placed in debugfs with:
114 Also, atomic_t values can be placed in debugfs with:
169 If you want to dump an u32 array in debugfs, you can create file with:
187 The "dev" argument is the device related to this debugfs file, and
202 A call to debugfs_rename() will give a new name to an existing debugfs
207 There is one important thing that all debugfs users must take into account:
208 there is no automatic cleanup of any directories created in debugfs.  If a
209 module is unloaded without explicitly removing debugfs entries, the result
211 So all debugfs users - at least those which can be built as modules - must
219 Once upon a time, debugfs users were required to remember the dentry
220 pointer for every debugfs file they created so that all files could be
221 cleaned up.  We live in more civilized times now, though, and debugfs users