| /linux-6.1.9/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-6.1.9/Documentation/virt/kvm/x86/ |
| D | timekeeping.rst | 31 timekeeping which may be difficult to find elsewhere, specifically,
279 the APIC CPU-local memory-mapped hardware. Beware that CPU errata may affect
280 the use of the APIC and that workarounds may be required. In addition, some of
283 functionality that may be more computationally expensive to implement.
297 systems designated as legacy free may support only the HPET as a hardware timer
317 timing chips built into the cards which may have registers which are accessible
360 platforms, the TSCs of different CPUs may start at different times depending
364 The BIOS may attempt to resynchronize the TSCs during the poweron process and
365 the operating system or other system software may attempt to do this as well.
367 write the full 64-bits of the TSC, it may be impossible to match the TSC in
[all …]
|
| /linux-6.1.9/security/smack/ |
| D | smack_access.c | 89 int may = srp->smk_access; in smk_access_entry() local
93 if ((may & MAY_WRITE) == MAY_WRITE) in smk_access_entry()
94 may |= MAY_LOCK; in smk_access_entry()
95 return may; in smk_access_entry()
118 int may = MAY_NOT; in smk_access() local
168 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access()
172 if (may <= 0 || (request & may) != request) { in smk_access()
182 if (may & MAY_BRINGUP) in smk_access()
222 int may; in smk_tskacc() local
234 may = smk_access_entry(sbj_known->smk_known, in smk_tskacc()
[all …]
|
| /linux-6.1.9/Documentation/admin-guide/sysctl/ |
| D | user.rst | 42 user namespace may create.
48 user namespace may create.
54 user namespace may create.
60 current user namespace may create.
66 user namespace may create.
72 user namespace may create.
78 user namespace may create.
84 user namespace may create.
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 6 Note that this may mean that if an endpoint is causing problems, the AER
7 counters may increment at its link partner (e.g. root port) because the
8 errors may be "seen" / reported by the link partner and not the
9 problematic endpoint itself (which may report all counters as 0 as it never
17 PCI device using ERR_COR. Note that since multiple errors may
19 TOTAL_ERR_COR at the end of the file may not match the actual
38 PCI device using ERR_FATAL. Note that since multiple errors may
40 TOTAL_ERR_FATAL at the end of the file may not match the actual
69 may be reported using a single ERR_FATAL message, thus
70 TOTAL_ERR_NONFATAL at the end of the file may not match the
|
| /linux-6.1.9/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 15 functions may have live state and therefore may not be safe to patch. One way
18 Existing stacktrace code may not always give an accurate picture of all
35 * The trace includes all functions that the task may be returned to, and the
56 architectures may need to verify that code has been compiled in a manner
57 expected by the unwinder. For example, an unwinder may expect that
63 In some cases, an unwinder may require metadata to correctly unwind.
78 Unwinding may terminate early for a number of reasons, including:
102 manipulating a frame pointer), but there can be code which may not follow these
103 conventions and may require special handling in the unwinder, e.g.
124 There are several ways an architecture may identify kernel code which is deemed
[all …]
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/Documentation/staging/ |
| D | speculation.rst | 12 work which may be discarded at a later stage.
17 absence of data in caches. Such state may form side-channels which can be
32 Which, on arm64, may be compiled to an assembly sequence such as::
44 value will subsequently be discarded, but the speculated load may affect
47 More complex sequences involving multiple dependent memory accesses may
61 Under speculation, the first call to load_array() may return the value
63 microarchitectural state dependent on this value. This may provide an
|
| /linux-6.1.9/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
28 It also may be regarded as the definition of a key and the associated data type
45 Property sets may be hierarchical. That is, a property set may contain
46 multiple property subsets that each may contain property subsets of its
66 principle, the property set may still not be regarded as a valid one.
68 For example, that applies to device properties which may cause kernel code
71 particular, that may happen if the kernel code uses device properties to
77 In all cases in which kernel code may do something that will confuse AML as a
90 avoided. For this reason, it may not be possible to make _DSD return a property
92 sake of code re-use, it may make sense to provide as much of the configuration
|
| /linux-6.1.9/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-6.1.9/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 7 Different devices may be partitioned in a different ways. Some may use a fixed
8 flash layout set at production time. Some may use on-flash table that describes
18 format) it may also be described using above rules ('compatible' and optionally
33 string are not considered partitions, as they may be used for other bindings.
|
| /linux-6.1.9/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-6.1.9/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 13 Log entries may be purged by the service processor
20 the only remaining copy of a log message may be in
26 The service processor may be able to store more log
28 an event from Linux you may instantly get another one
33 user space to solve the problem. In future, we may
48 In the future there may be additional types.
|
| /linux-6.1.9/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-6.1.9/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 24 Note that pin controllers themselves may also be client devices of themselves.
25 For example, a pin controller may set up its own "active" state when the
37 property exists to define the pin configuration. Each state may also be
50 entries may exist in this list so that multiple pin
51 controllers may be configured, or so that a state may be built
57 In some cases, it may be useful to define a state, but for it
58 to be empty. This may be required when a common IP block is
62 exist, they must still be defined, but may be left empty.
|
| /linux-6.1.9/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 4 # As this may inadvertently break the build, only allow the user
45 Choose this option to turn on extra driver debugging that may affect
71 paths that may slow the system down and if hit hang the machine.
84 failures. However, more casual testers may not want to trigger
97 Enable additional logging that may help track down the cause of
111 ordinary tests, but may be vital for post-mortem debugging when
125 ordinary tests, but may be vital for post-mortem debugging when
138 Choose this option to turn on extra driver debugging that may affect
150 Choose this option to turn on extra driver debugging that may affect
162 Choose this option to turn on extra driver debugging that may affect
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/powerpc/ |
| D | sleep.yaml | 17 may contain a "sleep" property which describes these connections.
25 that may be supported are:
27 - Dynamic: The device may be disabled or enabled at any time.
28 - System Suspend: The device may request to be disabled or remain
33 Some devices may share a clock domain with each other, such that they should
|
| /linux-6.1.9/LICENSES/deprecated/ |
| D | GFDL-1.1 | 73 textbook of mathematics, a Secondary Section may not explain any
119 You may copy and distribute the Document in any medium, either
123 conditions whatsoever to those of this License. You may not use
125 copying of the copies you make or distribute. However, you may accept
129 You may also lend copies, under the same conditions stated above, and
130 you may publicly display copies.
142 visible. You may add other material on the covers in addition.
173 You may copy and distribute a Modified Version of the Document under
183 of the Document). You may use the same title as a previous version
210 it was based on. These may be placed in the "History" section.
[all …]
|
| D | GFDL-1.2 | 76 textbook of mathematics, a Secondary Section may not explain any
86 allowed to be designated as Invariant. The Document may contain zero
92 the Document is released under this License. A Front-Cover Text may
93 be at most 5 words, and a Back-Cover Text may be at most 25 words.
134 The Document may include Warranty Disclaimers next to the notice which
138 implication that these Warranty Disclaimers may have is void and has
144 You may copy and distribute the Document in any medium, either
148 conditions whatsoever to those of this License. You may not use
150 copying of the copies you make or distribute. However, you may accept
154 You may also lend copies, under the same conditions stated above, and
[all …]
|
| /linux-6.1.9/Documentation/userspace-api/media/v4l/ |
| D | dev-encoder.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
88 client may call :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
93 2. To enumerate the set of supported raw formats, the client may call
103 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
116 4. The client may use :c:func:`VIDIOC_ENUM_FRAMEINTERVALS` to detect supported
137 ``CAPTURE``, if applicable, may be queried using their respective controls
140 6. Any additional encoder capabilities may be discovered by querying
157 desired size of ``CAPTURE`` buffers; the encoder may adjust it to
[all …]
|
| 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
82 the order in which frames are decoded; may differ from display order if the
130 a point in the bytestream from which decoding may start/continue, without
218 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
227 2. To enumerate the set of supported raw formats, the client may call
237 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
251 ``OUTPUT``, if applicable, may be queried using their respective controls
274 desired size of ``OUTPUT`` buffers; the decoder may adjust it to
[all …]
|
| /linux-6.1.9/Documentation/x86/ |
| D | intel-hfi.rst | 25 separate capabilities. Even though on some systems these two metrics may be
28 These capabilities may change at runtime as a result of changes in the
32 capabilities may change every tens of milliseconds. For instance, a remote
33 mechanism may be used to lower Thermal Design Power. Such change can be
35 excessive heat, the HFI may reflect reduced performance on specific CPUs.
52 The thermal monitor may generate interrupts per CPU or per package. The HFI
66 that there may be many HFI updates every second, the updates relayed to
|
| /linux-6.1.9/Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 18 cannot access any of the i2c external monitoring chips it may find. If you
20 interface is likely not to work. This document may then not cover your situation
41 Some of these thresholds may not be used by Nouveau depending
70 You may also have the following attribute:
86 [PWM_min, PWM_max] range, the reported fan speed (RPM) may not be accurate
92 Thermal management on Nouveau is new and may not work on all cards. If you have
|
| /linux-6.1.9/Documentation/powerpc/ |
| D | syscall64-abi.rst | 14 scv 0 instruction is an alternative that may provide better performance,
21 .. [1] Some syscalls (typically low-level management functions) may have
93 to the usual transactional memory semantics. A syscall may or may not result
126 following differences. Some vsyscalls may have different calling sequences.
134 The vsyscall may or may not use the caller's stack frame save areas.
153 may or may not result in the transaction being doomed by hardware.
|