| /Linux-v5.4/Documentation/virt/kvm/ |
| D | timekeeping.txt | 27 timekeeping which may be difficult to find elsewhere, specifically,
267 the APIC CPU-local memory-mapped hardware. Beware that CPU errata may affect
268 the use of the APIC and that workarounds may be required. In addition, some of
271 functionality that may be more computationally expensive to implement.
284 systems designated as legacy free may support only the HPET as a hardware timer
303 timing chips built into the cards which may have registers which are accessible
346 platforms, the TSCs of different CPUs may start at different times depending
350 The BIOS may attempt to resynchronize the TSCs during the poweron process and
351 the operating system or other system software may attempt to do this as well.
353 write the full 64-bits of the TSC, it may be impossible to match the TSC in
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-net-cdc_ncm | 2 Date: May 2014
42 Date: May 2014
58 Date: May 2014
70 Date: May 2014
90 Date: May 2014
99 Date: May 2014
106 Date: May 2014
113 Date: May 2014
122 Date: May 2014
130 Date: May 2014
[all …]
|
| D | sysfs-class-pwm | 2 Date: May 2013
11 Date: May 2013
20 Date: May 2013
27 Date: May 2013
35 Date: May 2013
42 Date: May 2013
51 Date: May 2013
58 Date: May 2013
65 Date: May 2013
73 Date: May 2013
|
| D | sysfs-kernel-slab | 2 Date: May 2007
9 files may be modified to change the behavior of the cache (and
14 Date: May 2007
23 Date: May 2007
32 Date: May 2007
100 Date: May 2007
110 Date: May 2007
132 Date: May 2007
195 Date: May 2007
215 Date: May 2007
[all …]
|
| D | sysfs-block | 83 Storage devices may report a physical block size that is
94 Storage devices may report a physical block size that is
102 Date: May 2009
109 Date: May 2009
114 block size but may be bigger. One example is SATA
124 Storage devices may report a granularity or preferred
138 Storage devices may report an optimal I/O size, which is
162 Date: May 2011
165 Devices that support discard functionality may
173 Date: May 2011
[all …]
|
| D | sysfs-driver-hid-ntrig | 2 Date: May, 2010
11 Date: May, 2010
21 sensor may mistakenly not detect a finger that is still present.
26 Date: May, 2010
41 Date: May, 2010
56 Date: May, 2010
66 Date: May, 2010
|
| /Linux-v5.4/Documentation/security/ |
| D | credentials.rst | 17 Objects are things in the system that may be acted upon directly by
43 indicates the 'objective context' of that object. This may or may not be
58 Objects other than tasks may under some circumstances also be subjects.
59 For instance an open file may send SIGIO to a task using the UID and EUID
77 Linux has a number of actions available that a subject may perform upon an
98 file may supply more than one ACL.
102 'group' and 'other'), each of which may be granted certain privileges
112 The system as a whole may have one or more sets of rules that get
166 The inheritable capabilities are the ones that may get passed across
169 The bounding set limits the capabilities that may be inherited across
[all …]
|
| /Linux-v5.4/drivers/atm/ |
| D | Kconfig | 61 Note that extended debugging may create certain race conditions
73 chipsets. However, in some cases, large bursts may overrun buffers
80 may increase the cost of setting up a transfer such that the
92 Burst sixteen words at once in the send direction. This may work
106 Burst four words at once in the send direction. You may want to try
108 may or may not improve throughput.
114 Burst two words at once in the send direction. You may want to try
116 are also set may or may not improve throughput.
122 Burst sixteen words at once in the receive direction. This may work
129 Burst eight words at once in the receive direction. This may work
[all …]
|
| /Linux-v5.4/drivers/block/drbd/ |
| D | drbd_req.h | 31 * There are quite a few things that may happen to a drbd request
42 * It may be identified as a concurrent (write) request
45 * It may me handed over to the local disk subsystem.
46 * It may be completed by the local disk subsystem,
49 * it may be retried remotely.
51 * It may be queued for sending.
52 * It may be handed over to the network stack,
53 * which may fail.
54 * It may be acknowledged by the "peer" according to the wire_protocol in use.
55 * this may be a negative ack.
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | dev-decoder.rst | 25 2. The meaning of words "must", "may", "should", etc. is as per `RFC
30 4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
76 the order in which frames are decoded; may differ from display order if the
123 a point in the bytestream from which decoding may start/continue, without
211 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
220 2. To enumerate the set of supported raw formats, the client may call
230 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
244 ``OUTPUT``, if applicable, may be queried using their respective controls
267 desired size of ``OUTPUT`` buffers; the decoder may adjust it to
[all …]
|
| /Linux-v5.4/drivers/block/paride/ |
| D | Kconfig | 18 support into your kernel, you may answer Y here to build in the
34 support into your kernel, you may answer Y here to build in the
50 support into your kernel, you may answer Y here to build in the
64 support into your kernel, you may answer Y here to build in the
80 If you chose to build PARIDE support into your kernel, you may
105 support into your kernel, you may answer Y here to build in the
123 If you chose to build PARIDE support into your kernel, you may
142 If you chose to build PARIDE support into your kernel, you may
154 into your kernel, you may answer Y here to build in the protocol
165 into your kernel, you may answer Y here to build in the protocol
[all …]
|
| /Linux-v5.4/arch/m68k/ifpsp060/ |
| D | fpsp.doc | 206 may exit through _060_real_inex <---|
208 may exit through _060_real_ovfl <---|
210 may exit through _060_fpsp_done <---|
218 may exit through _060_real_inex <---|
220 may exit through _060_real_unfl <---|
222 may exit through _060_fpsp_done <---|
253 |----> may exit through _060_real_trace
255 |----> may exit through _060_real_trap
257 |----> may exit through _060_real_bsun
259 |----> may exit through _060_fpsp_done
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/ |
| D | fdl-appendix.rst | 74 may not explain any mathematics.) The relationship could be a matter of
134 You may copy and distribute the :ref:`Document <fdl-document>` in any
138 you add no other conditions whatsoever to those of this License. You may
140 copying of the copies you make or distribute. However, you may accept
145 You may also lend copies, under the same conditions stated above, and
146 you may publicly display copies.
161 with all words of the title equally prominent and visible. You may add
198 You may copy and distribute a :ref:`Modified Version <fdl-modified>`
212 the Document). You may use the same title as a previous version if
266 versions it was based on. These may be placed in the “History”
[all …]
|
| /Linux-v5.4/include/linux/ |
| D | async.h | 49 * Returns an async_cookie_t that may be used for checkpointing later.
50 * Note: This function may be called from atomic or non-atomic contexts.
63 * Returns an async_cookie_t that may be used for checkpointing later.
64 * @domain may be used in the async_synchronize_*_domain() functions to
66 * Note: This function may be called from atomic or non-atomic contexts.
80 * Returns an async_cookie_t that may be used for checkpointing later.
85 * Note: This function may be called from atomic or non-atomic contexts.
99 * Returns an async_cookie_t that may be used for checkpointing later.
104 * @domain may be used in the async_synchronize_*_domain() functions to
106 * Note: This function may be called from atomic or non-atomic contexts.
|
| /Linux-v5.4/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 4 # As this may inadvertently break the build, only allow the user
41 Choose this option to turn on extra driver debugging that may affect
67 paths that may slow the system down and if hit hang the machine.
78 Enable additional logging that may help track down the cause of
92 ordinary tests, but may be vital for post-mortem debugging when
106 ordinary tests, but may be vital for post-mortem debugging when
119 Choose this option to turn on extra driver debugging that may affect
131 Choose this option to turn on extra driver debugging that may affect
143 Choose this option to turn on extra driver debugging that may affect
173 and may trigger unintended HW side-effects as they break strict
[all …]
|
| /Linux-v5.4/Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 14 …These APIs may only be provided by certain platforms, and may not be available to all virtual mach…
15 …even on supported platforms. Restrictions on the use of these APIs may be imposed in order to supp…
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
22 functionality offered may vary by virtual machine implementation.
32 …Guest software may implement a software timeout on CCB operations, and if the timeout is exceeded,…
33 …operation may be cancelled or killed via the ccb_kill API function. It is recommended for guest so…
34 …to implement a software timeout to account for certain RAS errors which may result in lost CCBs. I…
36 …killing it in order to determine if the CCB is still in queue, or may have been lost due to a RAS …
38 …There is no fixed limit on the number of outstanding CCBs guest software may have queued in the vi…
49 The query functionality may vary based on the compatibility property of the virtual device:
[all …]
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 12 namespace. In principle, the format of the data may be arbitrary, but it has to
26 It also may be regarded as the definition of a key and the associated data type
41 Property sets may be hierarchical. That is, a property set may contain
42 multiple property subsets that each may contain property subsets of its
62 principle, the property set may still not be regarded as a valid one.
64 For example, that applies to device properties which may cause kernel code
67 particular, that may happen if the kernel code uses device properties to
73 In all cases in which kernel code may do something that will confuse AML as a
86 avoided. For this reason, it may not be possible to make _DSD return a property
88 sake of code re-use, it may make sense to provide as much of the configuration
|
| /Linux-v5.4/Documentation/driver-api/pm/ |
| D | devices.rst | 55 leave the low-power state. This feature may be enabled or disabled
57 Ethernet drivers the ioctl interface used by ethtool may also be used
58 for this purpose); enabling it may cost some power usage, but let the
63 Devices may also be put into low-power states while the system is
68 device is on, it may be necessary to carry out some bus-specific
70 states at run time may require special handling during system-wide power
82 have been put into low-power states (at runtime), the effect may be very similar
89 drivers are no longer accepted. A given bus or platform may have different
193 wakeup" used by runtime power management, although it may be supported by the
196 they should be put into the full-power state. Those interrupts may or may not
[all …]
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | regulator.rst | 32 The regulator API uses a number of terms which may not be familiar:
43 may either be static, requiring only a fixed supply, or dynamic,
83 Note that since multiple consumers may be using a regulator and machine
84 constraints may not allow the regulator to be disabled there is no
87 drivers should assume that the regulator may be enabled at all times.
92 Some consumer devices may need to be able to dynamically configure their
93 supplies. For example, MMC drivers may need to select the correct
94 operating voltage for their cards. This may be done while the regulator
109 Callbacks may also be registered for events such as regulation failures.
141 and the parameters that may be set. This is required since generally
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | numaperf.rst | 7 Some platforms may have multiple types of memory attached to a compute
8 node. These disparate memory ranges may share some characteristics, such
9 as CPU cache coherence, but may have different performance. For example,
14 characteristics. Some memory may share the same node as a CPU, and others
16 CPUs, they may still be local to one or more compute nodes relative to
34 When multiple memory initiators exist, they may not all have the same
36 pair may be organized into different ranked access classes to represent
39 the highest access class, 0. Any given target may have one or more
40 local initiators, and any given initiator may have multiple local
53 A memory initiator may have multiple memory targets in the same access
[all …]
|
| /Linux-v5.4/LICENSES/deprecated/ |
| D | GPL-1.0 | 66 contains a notice placed by the copyright holder saying it may be
73 1. You may copy and distribute verbatim copies of the Program's source
79 along with the Program. You may charge a fee for the physical act of
82 2. You may modify your copy or copies of the Program or any portion of
93 that you may choose to grant warranty protection to some or all
101 warranty) and that users may redistribute the program under these
105 d) You may charge a fee for the physical act of transferring a
106 copy, and you may at your option offer warranty protection in
113 3. You may copy and distribute the Program (or a portion or derivative of
128 corresponding source code may be obtained. (This alternative is
[all …]
|
| /Linux-v5.4/Documentation/networking/device_drivers/chelsio/ |
| D | cxgb.txt | 51 You may set the timer latency after disabling adaptive-rx:
59 You may also provide a timer latency value while disabling adaptive-rx:
100 parameters for "performance tuning" an what value to use. You may or may not
106 Your distribution may have a different way of doing things, or you may prefer
111 your system. You may want to write a script that runs at boot-up which
159 receiver. Due to the variations of RTT, you may want to increase the buffer
170 The receive buffer (RX_WINDOW) size may be calculated the same as single
174 not supported on the machine. Experimentation may be necessary to attain
185 may be found in /var/log/messages.
211 controller may be bound to more than one CPU. This will cause TCP
[all …]
|
| /Linux-v5.4/include/xen/interface/ |
| D | event_channel.h | 24 * 2. <rdom> may be DOMID_SELF, allowing loopback connections.
41 * 2. <remote_dom> may be DOMID_SELF, allowing loopback connections.
56 * 1. A virtual IRQ may be bound to at most one event channel per vcpu.
58 * may not be changed.
72 * 1. A physical IRQ may be bound to at most one event channel per domain.
73 * 2. Only a sufficiently-privileged domain may bind to a physical IRQ.
89 * may not be changed.
123 * 1. <dom> may be specified as DOMID_SELF.
124 * 2. Only a sufficiently-privileged domain may obtain the status of an event
184 * 1. <dom> may be specified as DOMID_SELF.
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 7 MSIs were originally specified by PCI (and are used with PCIe), but may also be
16 Devices may be configured by software to write to arbitrary doorbells which
17 they can address. An MSI controller may feature a number of doorbells.
21 Devices may be configured to write an arbitrary payload chosen by software.
22 MSI controllers may have restrictions on permitted payloads.
35 address by some master. An MSI controller may feature a number of doorbells.
58 generate, the doorbell and payload may be configured, though sideband
59 information may not be configurable.
67 This property is unordered, and MSIs may be allocated from any combination of
|
| /Linux-v5.4/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 18 Groups. Note that other groups may also distribute working documents as
22 Internet Drafts may be updated, replaced, or obsoleted by other documents
82 mapping to hosts within the authority's domain. These mappings may be
124 corresponding ASCII representations. Non-related groups of systems may
136 have their own unique mappings. For example, one group of systems may
137 use the number 5 to represent Unclassified while another group may use the
158 identifiers are greater than 127 are defined by the DOI authority and may
182 restrictions specified in this document may increase to use the full area
348 octets. Up to 15 categories may be represented by this tag. Valid values
413 label. This tag may contain a maximum of 7 category pairs. The bottom
[all …]
|
