| /Documentation/dev-tools/ |
| D | gcov.rst | 13 This will create source code files annotated with execution counts
54 To enable profiling for specific files or directories, add a line
61 - For all files in one directory::
65 To exclude files from being profiled even when CONFIG_GCOV_PROFILE_ALL
74 Only files which are linked to the main kernel image or are compiled as
78 Files chapter
81 The gcov kernel support creates the following files in debugfs:
84 Parent directory for all gcov-related files.
130 gcc version used for kernel build. Also the following files need to be
134 - all C source files + headers
[all …]
|
| /Documentation/filesystems/ |
| D | files.rst | 7 This document describes how locking for files (struct file)
8 and file descriptor table (struct files) works.
11 with a lock (files->file_lock) and reference count (files->count).
18 The files (struct file) themselves are protected using
33 and files->fdtab points to the new structure. The fdtable
46 fdt = files_fdtable(files);
61 3. For any update to the fd table, files->file_lock must
87 file = fcheck_files(files, fd);
110 holding files->file_lock. If ->file_lock is dropped, then
111 another thread expand the files thereby creating a new
[all …]
|
| D | hfs.rst | 26 used for creating new files. Default values: '????'.
29 Specifies the user/group that owns all files on the filesystems.
33 Specifies the umask used for all files , all directories or all
34 files and directories. Defaults to the umask of the mounting process.
58 and gid of files.
59 * You can't create hard- or symlinks, device files, sockets or FIFOs.
62 non-standard forks are represented as hidden additional files in the normal
66 * You can't create, delete or rename resource forks of files or the
70 * Copying files to a different filesystem will loose those attributes
|
| D | ecryptfs.rst | 8 For documentation, please see the files in the doc/ subdirectory. For
36 eCryptfs, you should copy the files to an unencrypted location and
37 then copy the files back into the new eCryptfs mount to migrate the
38 files.
45 files (i.e., /root/crypt). Then, create the mount point directory
77 or (2) directories containing files only created by eCryptfs. If you
78 mount a directory that has pre-existing files not created by eCryptfs,
|
| D | zonefs.rst | 13 constraint of zoned block devices to the user. Files representing sequential
60 Zonefs exposes the zones of a zoned block device as files. The files
85 Files representing zones of the same type are grouped together under the same
101 obtained with the stat() or fstat() system calls, indicates the number of files
104 Zone files
107 Zone files are named using the number of the zone they represent within the set
109 contain files named "0", "1", "2", ... The file numbers also represent
112 All read and write operations to zone files are not allowed beyond the file
116 Creating, deleting, renaming or modifying any attribute of files and
122 Conventional zone files
[all …]
|
| D | dax.txt | 1 Direct Access for files
7 The page cache is usually used to buffer reads and writes to files.
21 on it as usual. The DAX code currently only supports files with a block
32 add 'dax' to the options in /etc/fstab. This works to enable DAX on all files
47 files and directories. This advisory flag can be set or cleared at any
51 be inherited by all regular files and subdirectories that are subsequently
52 created in this directory. Files and subdirectories that exist at the time
77 a) Setting the parent directory FS_XFLAG_DAX as needed before files are
82 c) Changing the FS_XFLAG_DAX flag on existing regular files and
87 the change in behaviour for existing regular files may not occur
[all …]
|
| D | isofs.rst | 10 gid=nnn All files in the partition will be in group nnn.
11 uid=nnn All files in the partition will be owned by user id nnn.
39 mode=xxx Sets the permissions on files to xxx unless Rock Ridge
43 overriderockperm Set permissions on files and directories according to
48 hide Completely strip hidden files from the file system.
49 showassoc Show files marked with the 'associated' bit
50 unhide Deprecated; showing hidden files is now default;
|
| D | dnotify.rst | 10 to be notified when a directory, or any of the files in it, are changed.
46 The notification should work for any local access to files even if the
48 access to files served by local user mode servers should be notified.
49 Also, remote accesses to files served by a local kernel NFS server should
53 the problem of hard links to files has been ignored. So if a file (x)
59 Also, files that are unlinked, will still cause notifications in the
|
| D | fsverity.rst | 14 of read-only files. Currently, it is supported by the ext4 and f2fs
20 but works on files rather than block devices. On regular files on
58 (APK) files, for example. These typically contain many translations,
68 still be used on read-only filesystems. fs-verity is for files that
73 authenticating the files is up to userspace. However, to meet some
76 that all fs-verity files be signed by a key loaded into a keyring; see
131 take a long time to execute on large files, and it is interruptible by
312 opening the file, and opening verity files can be expensive.
314 Accessing verity files
320 - Verity files are readonly. They cannot be opened for writing or
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 8 The files are read only.
15 Description: These files show with which CPLD versions have been burned
18 The files are read only.
28 The files are read only.
34 Description: These files show with which CPLD versions have been burned
37 The files are read only.
43 Description: These files enable and disable the access to the JTAG domain.
66 Description: These files allow asserting system power cycling, switching
79 The files are write only.
93 Description: These files show the system reset cause, as following: power
[all …]
|
| D | sysfs-driver-usb-usbtmc | 6 These files show the various USB TMC capabilities as described
12 The files are read only.
20 These files show the various USB TMC capabilities as described
27 The files are read only.
|
| /Documentation/misc-devices/ |
| D | ad525x_dpot.rst | 13 Files chapter
16 Each dpot device will have a set of eeprom, rdac, and tolerance files. How
19 The eeprom files are used to program the startup value of the device.
21 The rdac files are used to program the immediate value of the device.
23 The tolerance files are the read-only factory programmed tolerance settings
43 You can use simple reads/writes to access these files::
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 25 set of files. These files can be used for manipulating the state of the
26 logical SPU. Users can change permissions on those files, but not actu-
27 ally add or remove files.
40 Files chapter
43 The files in spufs mostly follow the standard behavior for regular sys-
49 All files that support the read(2) operation also support readv(2) and
50 all files that support the write(2) operation also support writev(2).
51 All files support the access(2) and stat(2) family of operations, but
55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera-
59 The current set of files is:
[all …]
|
| /Documentation/process/ |
| D | license-rules.rst | 18 as a whole, though individual source files can have a different license
28 Aside from that, individual files can be provided under a dual license,
32 The User-space API (UAPI) header files, which describe the interface of
37 into any source files which create an executable running on the Linux
53 The Linux kernel requires the precise SPDX identifier in all source files.
63 The SPDX license identifier in kernel files shall be added at the first
65 of files this is the first line, except for scripts which require the
86 files. There was build breakage observed with generated .lds files where
109 For example, the linux kernel UAPI files use the expression::
125 to be selected. For example, some dtsi files are available under dual
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-ibft | 5 files that expose the iSCSI Boot Firmware Table initiator data.
12 files that expose the iSCSI Boot Firmware Table target data.
22 files that expose the iSCSI Boot Firmware Table NIC data.
28 Description: The /sys/firmware/ibft/acpi_header directory will contain files
|
| /Documentation/input/devices/ |
| D | edt-ft5x06.rst | 15 The driver allows configuration of the touch screen via a set of sysfs files:
31 For debugging purposes the driver provides a few files in the debug
33 you'll find the following files:
49 files triggers a new readout. It is recommended to provide a buffer
53 mode. The same happens when reading/writing to the parameter files when the
|
| /Documentation/kbuild/ |
| D | headers_install.rst | 5 The "make headers_install" command exports the kernel's header files in a
8 The linux kernel's exported header files describe the API for user space
9 programs attempting to use kernel services. These kernel header files are
12 system calls. The C library's header files include the kernel header files
|
| D | makefiles.rst | 11 === 3 The kbuild files
51 --- 7.10 Generic header files
80 (the resident kernel image) and modules (any module files).
104 any kernel Makefiles (or any other source files).
123 3 The kbuild files
129 The preferred name for the kbuild files are 'Makefile' but 'Kbuild' can
140 These lines define the files to be built, any special compilation
166 The kbuild Makefile specifies object files for vmlinux
170 Kbuild compiles all the $(obj-y) files. It then calls
171 "$(AR) rcSTP" to merge these files into one built-in.a file.
[all …]
|
| /Documentation/sound/designs/ |
| D | procfile.rst | 2 Proc Files of ALSA Drivers
12 check the files listed in the following sections.
15 card-specific files are stored in the ``card*`` subdirectories.
58 Card Specific Files
61 The card-specific files are found in ``/proc/asound/card*`` directories.
64 dump). These files would be really helpful for debugging.
69 the last ``p`` or ``c`` means playback or capture direction. The files in
72 The status of MIDI I/O is found in ``midi*`` files. It shows the device
85 PCM Proc Files
229 - AC97 proc files, ``codec97#*/*`` files
[all …]
|
| /Documentation/filesystems/caching/ |
| D | cachefiles.rst | 76 - bmap() support on files in the filesystem (FIBMAP ioctl).
154 Do not create, rename or unlink files and directories in the cache while the
157 Renaming files in the cache might make objects appear to be other objects (the
160 Do not change or remove the extended attributes attached to cache files by the
163 Do not create files or directories in the cache, lest the cache get confused or
166 Do not chmod files in the cache. The module creates things with minimal
179 percentage of files available in the underlying filesystem. There are six
183 If the amount of free space and the number of available files in the cache
187 If the amount of available space or the number of available files in the
191 If the amount of available space or the number of available files in the
[all …]
|
| /Documentation/ |
| D | Kconfig | 14 bool "Warn if there are errors at ABI files"
17 The files under Documentation/ABI should follow what's
19 written, it would be possible that some of those files would
|
| /Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 5 LoadPin is a Linux Security Module that ensures all kernel-loaded files
10 restrictions without needing to sign the files individually.
24 command line option "``loadpin.exclude``". By default, all files are
29 still use LoadPin to protect the integrity of other files kernel loads. The
|
| /Documentation/devicetree/ |
| D | writing-schema.rst | 6 Devicetree bindings are written using json-schema vocabulary. Schema files are
22 references to other files specified in schema "$ref" properties. A $ref value
25 of the current schema file's '$id' value. A URL is used even for local files,
26 but there may not actually be files present at those locations.
83 validation of DT files.
95 boilerplate. The tools process the schema files to produce the final schema for
115 binding documents and validate DTS files using the DT schema. The DT schema
145 In order to perform validation of DT source files, use the ``dtbs_check`` target::
149 Note that ``dtbs_check`` will skip any binding schema files with errors. It is
151 binding schema files.
|
| /Documentation/hwmon/ |
| D | lm93.rst | 83 sysfs files prochot1, prochot2, prochot1_avg, prochot2_avg, prochot1_max,
93 These intervals can be found in the sysfs files prochot1_interval and
94 prochot2_interval. The values in these files specify the intervals for
112 The sysfs files prochot1_override and prochot2_override contain boolean
123 sysfs files vrdhot1 and vrdhot2. There is one value per file: a boolean for
125 files are read-only.
145 15.10.6 of the datasheet for details.) The sysfs files pwm1_override
147 where 0 disables and 1 enables the manual control mode. The sysfs files pwm1
159 The sysfs files pwm1_freq and pwm2_freq are used to select the frequency. The
177 in the sysfs files pwm<n>_auto_channels, where a "1" enables the binding, and
[all …]
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 43 a way to create images with root-owned files even though the image was
47 CONFIG_INITRAMFS_SOURCE. Sources can be either directories or files -
62 When a combination of directories and files are specified then the
64 can create a 'root-image' directory and install all files into it.
65 Because device-special files cannot be created by a unprivileged user,
66 special files can be listed in a 'root-files' file. Both 'root-image'
67 and 'root-files' can be listed in CONFIG_INITRAMFS_SOURCE and a complete
70 As a technical note, when directories and files are specified, the
|