| /Documentation/filesystems/nfs/ |
| D | fault_injection.txt | 7 production system. Injecting an error on the Linux NFS server will allow us to
20 <debug_dir>/nfsd. This will show a list of files that will be used for
22 corresponding to the action you want the server to take. The server will then
24 to <debug_dir>/nfsd/forget_locks. A value of 0 will tell the server to forget
25 all corresponding items. A log message will be created containing the number
36 this list is cleared, the server will have no knowledge of who the client
41 they were opened by. Clearing this list will force the client to reopen
46 Clearing this list will force the client to reclaim its locks (files are
51 has not changed since the delegation was awarded. Clearing this list will
57 access a file. This test will notify the client that its delegation has
[all …]
|
| D | idmapper.txt | 11 NFS will attempt to call /sbin/request-key first. If this succeeds, the
12 result will be cached using the generic request-key cache. This call should
18 configured with the id_resolver key type), then the idmapper will ask the
19 legacy rpc.idmap daemon for the id mapping. This result will be stored
26 The file /etc/request-key.conf will need to be modified so /sbin/request-key can
33 This will direct all id_resolver requests to the program /usr/sbin/nfs.idmap.
34 The last parameter, 600, defines how many seconds into the future the key will
36 is not specified, nfs.idmap will default to 600 seconds.
54 request-key will find the first matching line and corresponding program. In
55 this case, /some/other/program will handle all uid lookups and
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
10 This will be one of the following strings:
32 Some regulator directories will contain a field called
36 This will be one of the following strings:
72 Each regulator directory will contain a field called
75 This will be one of the following strings:
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
[all …]
|
| D | sysfs-power | 5 The /sys/power directory will contain files that will
31 supported). The mode that will be used on subsequent attempts
48 the name of the method by which the system will be put to
50 'firmware' - means that the memory image will be saved to disk
52 firmware will handle the system suspend.
53 'platform' - the memory image will be saved by the kernel and
54 the system will be put to sleep by the platform driver (e.g.
56 'shutdown' - the memory image will be saved by the kernel and
57 the system will be powered off.
58 'reboot' - the memory image will be saved by the kernel and
[all …]
|
| D | sysfs-bus-pci-drivers-xhci_hcd | 13 When the DbC is enabled, the root port will be assigned
14 to the Debug Capability. Otherwise, it will be assigned
17 Writing "enable" to this attribute will enable the DbC
18 functionality and the shared root port will be assigned
20 will disable the DbC functionality and the shared root
21 port will roll back to the xHCI.
|
| D | sysfs-class-rc | 27 Writing "+proto" will add a protocol to the list of enabled
29 Writing "-proto" will remove a protocol from the list of enabled
31 Writing "proto" will enable only "proto".
32 Writing "none" will disable all protocols.
45 the filter will be ignored. Otherwise the write will fail with
60 the filter will be ignored. Otherwise the write will fail with
77 Writing "proto" will use "proto" for wakeup events.
78 Writing "none" will disable wakeup.
93 scancodes which match the filter will wake the system from e.g.
95 Otherwise the write will fail with an error.
[all …]
|
| /Documentation/s390/ |
| D | common_io.rst | 19 The given devices will be ignored by the common I/O-layer; no detection
20 and device sensing will be done on any of those devices. The subchannel to
21 which the device in question is attached will be treated as if no device was
29 give a device number 0xabcd, it will be interpreted as 0.0.abcd.
34 operator). The '!' operator will cause the I/O-layer to _not_ ignore a device.
42 will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device
49 will ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02.
62 "free all" will un-ignore all ignored devices,
63 "free <device range>, <device range>, ..." will un-ignore the specified
69 will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
[all …]
|
| /Documentation/powerpc/ |
| D | dawr-power9.rst | 29 h_set_mode(DAWR) and h_set_dabr() will now return an error to the
31 they will silently not get the DAWR.
33 kvmppc_set_one_reg() will store the value in the vcpu but won't
38 For xmon, the 'bd' command will return an error on P9.
44 will accept the command. Unfortunately since there is no hardware
45 support for the watchpoint, GDB will software emulate the watchpoint
48 The same will also be true for any guests started on a POWER9
49 host. The watchpoint will fail and GDB will fall back to software
52 If a guest is started on a POWER8 host, GDB will accept the watchpoint
53 and configure the hardware to use the DAWR. This will run at full
[all …]
|
| D | transactional_memory.rst | 48 references will complete in one go if there are no conflicts with other
54 lwarx/stwcx), either *both* SAVINGS_ACCT(r3) and CURRENT_ACCT(r3) will be
55 updated, or neither will be updated.
58 transaction, the transaction will be aborted by the CPU. Register and memory
59 state will roll back to that at the 'tbegin', and control will continue from
60 'tbegin+4'. The branch to abort_handler will be taken this second time; the
72 - See the ISA for full documentation of everything that will abort transactions.
78 Syscalls made from within an active transaction will not be performed and the
79 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
86 effects will be persistent, independent of transaction success or failure. No
[all …]
|
| /Documentation/filesystems/ |
| D | fiemap.txt | 37 flags, it will return EBADR and the contents of fm_flags will contain
39 with all flags passed, the contents of fm_flags will be unmodified.
47 fm_extents[] array is ignored (no extents will be returned), and the
48 fm_mapped_extents count will hold the number of extents needed in
55 If this flag is set, the kernel will sync the file before mapping extents.
58 If this flag is set, the extents returned will describe the inodes
68 fm_extent_count. The number of extents mapped by kernel will be
72 array will be returned and fm_mapped_extents will be equal to
73 fm_extent_count. In that case, the last extent in the array will not
74 complete the requested range and will not have the FIEMAP_EXTENT_LAST
[all …]
|
| D | ocfs2.txt | 54 atime_quantum=60(*) OCFS2 will not update atime unless this number
66 will be chosen. Invalid values will be ignored.
69 This means that if you lose your power, you will lose
71 filesystem will not be damaged though, thanks to the
73 will hurt performance, but it's good for data-safety.
74 Setting it to 0 will have the same effect as leaving
76 Setting it to very large values will improve
79 large, the fs will silently revert it to the default.
83 will result in inode numbers occupying more than 32
89 resv_level=2 (*) Set how aggressive allocation reservations will be.
[all …]
|
| D | automount-support.txt | 50 with a pointer to this list. This will process the list, marking every
54 (it's only referenced by its parent vfsmount), then it will be deleted
61 will only happen on the second expiration request after the last time the
65 mount is made on an expirable mount, the new vfsmount will not be on the
66 expiration list and will not expire.
68 If a namespace is copied, all mountpoints contained therein will be copied,
69 and the copies of those that are on an expiration list will be added to the
78 mountpoint (though some will be rejected - the current process's idea of the
83 umount() or its parent mountpoint, an EBUSY error will be returned and the
84 mountpoint will not be marked for expiration or unmounted.
[all …]
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 11 Once the Kconfig option I2C_GPIO_FAULT_INJECTOR is enabled, there will be an
13 mounted at /sys/kernel/debug. There will be a separate subdirectory per GPIO
14 driven I2C bus. Each subdirectory will contain files to trigger the fault
15 injection. They will be described now along with their intended use-cases.
25 "echo 0 > scl" you force SCL low and thus, no communication will be possible
26 because the bus master under test will not be able to clock. It should detect
38 core (see 'struct bus_recovery_info'). However, the bus recovery will not
46 The following fault injectors create situations where SDA will be held low by a
51 and will init a bus recovery on its own. If you want to implement bus recovery
59 client device to it. Then, a read transfer to this device will be started, but
[all …]
|
| /Documentation/userspace-api/ |
| D | seccomp_filter.rst | 53 The BPF program will be executed over struct seccomp_data
64 will contain the filter program. If the program is invalid, the
65 call will return -1 and set errno to ``EINVAL``.
68 processes will be constrained to the same filters and system
73 true, ``-EACCES`` will be returned. This requirement ensures that filter
78 additional filters may be layered on which will increase evaluation
89 call will always use the highest precedent value. (For example,
90 ``SECCOMP_RET_KILL_PROCESS`` will always take precedence.)
97 will be ``SIGSYS``, not ``SIGKILL``.
101 system call. The exit status of the task (``status & 0x7f``) will
[all …]
|
| /Documentation/hwmon/ |
| D | acpi_power_meter.rst | 30 Both `power[1-*]_average_{min,max}` must be set before the trip points will work.
31 When both of them are set, an ACPI event will be broadcast on the ACPI netlink
32 socket and a poll notification will be sent to the appropriate
40 the case, the `power[1-*]_cap` and related sysfs files will appear. When the
41 average power consumption exceeds the cap, an ACPI event will be broadcast on
42 the netlink event socket and a poll notification will be sent to the
44 hardware has taken action to reduce power consumption. Most likely this will
48 all cases the ACPI event will be broadcast on the ACPI netlink event socket as
52 `power[1-*]_cap` will be notified if the firmware changes the power cap.
53 `power[1-*]_interval` will be notified if the firmware changes the averaging
|
| /Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 47 discovers that the current descr is not empty, it will signal an
51 hardware is ahead, the tail pointer will be pointing at a "full"
52 descr. The OS will process this descr, and then mark it "not-in-use",
57 The OS will then note that the current tail is "empty", and halt
61 When traffic is flowing, then the head pointer will be pointing at
62 a "not-in-use" descr. The OS will perform various housekeeping duties
64 dma-mapping it so as to make it visible to the hardware. The OS will
69 pointer, at which point the OS will notice that the head descr is
70 "empty", and it will halt processing.
72 Thus, in an idle system, the GDACTDPA, tail and head pointers will
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 43 Otherwise, writing an integer value to this file will take the heads
47 normal operation will be resumed. The maximal value accepted for a
48 timeout is 30000 milliseconds. Exceeding this limit will return
49 -EOVERFLOW, but heads will be parked anyway and the timeout will be
58 reading from `/sys/block/*/device/unload_heads` will report the number
59 of milliseconds remaining until normal operation will be resumed;
60 otherwise, reading the unload_heads attribute will return 0.
71 will show you how many milliseconds are left before normal operation
72 will be resumed.
78 that this will typically be within 500 milliseconds apparently has
[all …]
|
| /Documentation/media/uapi/cec/ |
| D | cec-ioc-g-mode.rst | 51 When a CEC message is received, then the CEC framework will decide how
52 it will be processed. If the message is a reply to an earlier
54 is waiting for it. In addition the CEC framework will process it.
56 If the message is not a reply, then the CEC framework will process it
60 follower who will use :ref:`ioctl CEC_RECEIVE <CEC_RECEIVE>` to dequeue
64 The CEC framework will process core messages unless requested otherwise
66 case, the CEC framework will pass on most core messages without
67 processing them and the follower will have to implement those messages.
68 There are some messages that the core will always process, regardless of
108 then an attempt to become one will return the ``EBUSY`` error code
[all …]
|
| /Documentation/driver-api/ |
| D | switchtec.rst | 25 identifier and up to 1KB of command specific data. The firmware will
33 The MRPC interface will be exposed to userspace through a simple char
39 The first 4 bytes will be interpreted as the Command ID and the
40 remainder will be used as the input data. A write will send the
43 * Each write must be followed by exactly one read. Any double write will
44 produce an error and any read that doesn't follow a write will
47 * A read will block until the firmware completes the command and return
49 data. (The length will be specified by the size parameter of the read
50 call -- reading less than 4 bytes will produce an error.)
52 * The poll call will also be supported for userspace applications that
[all …]
|
| /Documentation/infiniband/ |
| D | user_mad.rst | 9 "issm" device attached. For example, a two-port HCA will have two
10 umad devices and two issm devices, while a switch will have one
19 request succeeds, a 32-bit id will be returned in the structure.
30 ioctl. Also, all agents registered through a file descriptor will
77 fields will be filled in with information on the received MAD. For
78 example, the remote LID will be in mad.lid.
80 If a send times out, a receive will be generated with mad.status set
82 mad.status will be 0.
115 the kernel and will be overwritten before a MAD is sent.
124 compatibility with older applications, this new layout will not be used
[all …]
|
| /Documentation/trace/ |
| D | stm.rst | 29 are consistent with what decoder expects, it will be able to properly
50 with "user" identification string will be allocated a master and
54 under "user" directory from the example above and this new rule will
67 stm core will try to find a policy node with the name matching the
68 task's name (e.g., "syslogd") and if one exists, it will be used.
70 catch-all entry "default" will be used, if it exists. This entry also
74 will return a error (EINVAL).
80 will help programmers and sysadmins identify gaps in configuration
85 mmu) will usually contain multiple channels' mmios, so the user will
109 Each stm_source device will need to assume a master and a range of
[all …]
|
| /Documentation/core-api/ |
| D | xarray.rst | 22 clustered; hashing the object and using the hash as the index will not
58 the range will return the same entry as looking up any other index in
59 the range. Setting a mark on one index will set it on all of them.
60 Storing to any index will store to all of them. Multi-index entries can
62 entry will cause the XArray to forget about the range.
73 using xa_load(). xa_store will overwrite any entry with the
81 xa_cmpxchg(). Like cmpxchg(), it will only succeed if
103 of indices. If you do this, some of the other operations will behave
110 will not need to allocate memory. The xa_reserve() function
111 will store a reserved entry at the indicated index. Users of the
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | cafe_ccic.rst | 16 RGB565, and RGB444 formats. (Anybody looking at the code will see RGB32 as
17 well, but that is a debugging aid which will be removed shortly). VGA and
21 To try it out: either of these commands will work:
36 - alloc_bufs_at_load: Normally, the driver will not allocate any DMA
38 then worst-case-sized buffers will be allocated at module load time.
44 allocated at run time, they will be sized appropriately for the current
49 systems, however, it will work well with only two.
52 will consent to work with. Default is one, but, on slower systems,
60 - flip: If this boolean parameter is set, the sensor will be instructed to
|
| /Documentation/filesystems/caching/ |
| D | netfs-api.txt | 59 will be filled in by the registration function; any other fields should just be
67 entire in-cache hierarchy for this netfs will be scrapped and begun
70 (3) The cookie representing the primary index will be allocated according to
106 cache. Any such objects created within an index will be created in the
111 400 bytes at present. At least 400 bytes will be available.
114 function is recursive. Too many layers will run the kernel out of stack.
171 parent for the non-index object will be queried. Any indices above that
173 need to be supplied for any non-index object or any index that will only
177 cache in the parent's list will be chosen, or failing that, the first
182 This function will be called to check that a match found in the cache for
[all …]
|
| /Documentation/driver-api/usb/ |
| D | typec.rst | 15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
30 Every port will be presented as its own device under /sys/class/typec/. The
31 first port will be named "port0", the second "port1" and so on.
33 When connected, the partner will be presented also as its own device under
34 /sys/class/typec/. The parent of the partner device will always be the port it
35 is attached to. The partner attached to port "port0" will be named
41 will be named port0-cable and the plug on the SOP Prime end (see USB Power
42 Delivery Specification ch. 2.4) will be named "port0-plug0" and on the SOP
43 Double Prime end "port0-plug1". The parent of a cable will always be the port,
44 and the parent of the cable plugs will always be the cable.
[all …]
|