| /Linux-v5.4/security/smack/ |
| D | smack_access.c | 84 int may = -ENOENT; in smk_access_entry() local
90 may = srp->smk_access; in smk_access_entry()
98 if ((may & MAY_WRITE) == MAY_WRITE) in smk_access_entry()
99 may |= MAY_LOCK; in smk_access_entry()
100 return may; in smk_access_entry()
119 int may = MAY_NOT; in smk_access() local
169 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access()
173 if (may <= 0 || (request & may) != request) { in smk_access()
183 if (may & MAY_BRINGUP) in smk_access()
223 int may; in smk_tskacc() local
[all …]
|
| D | smack_lsm.c | 991 int may; in smack_inode_init_security() local
998 may = smk_access_entry(skp->smk_known, dsp->smk_known, in smack_inode_init_security()
1008 if (may > 0 && ((may & MAY_TRANSMUTE) != 0) && in smack_inode_init_security()
1669 int may; in smack_mmap_file() local
1710 may = smk_access_entry(srp->smk_subject->smk_known, in smack_mmap_file()
1713 if (may == -ENOENT) in smack_mmap_file()
1714 may = srp->smk_access; in smack_mmap_file()
1716 may &= srp->smk_access; in smack_mmap_file()
1721 if (may == 0) in smack_mmap_file()
1749 if ((may | mmay) != mmay) { in smack_mmap_file()
[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/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-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
39 PCI device using ERR_FATAL. Note that since multiple errors may
41 TOTAL_ERR_FATAL at the end of the file may not match the actual
71 may be reported using a single ERR_FATAL message, thus
72 TOTAL_ERR_NONFATAL at the end of the file may not match the
|
| /Linux-v5.4/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.
|
| /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
|
| D | cdns,xtensa-pic.txt | 7 It may be either 1 or 2.
12 core variants it may be mapped to different internal IRQ.
13 IRQ sensitivity and priority are fixed for each core variant and may not be
|
| /Linux-v5.4/Documentation/ |
| D | speculation.txt | 10 work which may be discarded at a later stage.
15 absence of data in caches. Such state may form side-channels which can be
30 Which, on arm64, may be compiled to an assembly sequence such as::
42 value will subsequently be discarded, but the speculated load may affect
45 More complex sequences involving multiple dependent memory accesses may
59 Under speculation, the first call to load_array() may return the value
61 microarchitectural state dependent on this value. This may provide an
|
| /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/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/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/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
47 In the future there may be additional types.
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | syscall64-abi.rst | 12 .. [1] Some syscalls (typically low-level management functions) may have
61 to the usual transactional memory semantics. A syscall may or may not result
83 following differences. Some vsyscalls may have different calling sequences.
91 The vsyscall may or may not use the caller's stack frame save areas.
110 may or may not result in the transaction being doomed by hardware.
|
| /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/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/driver-api/firmware/ |
| D | built-in-fw.rst | 21 Even if you have these needs there are a few reasons why you may not be
25 * Some firmware may be optional
28 * Some firmware files may be really large in size. The remote-proc subsystem
30 * The firmware may need to be scraped out from some device specific location
|
| /Linux-v5.4/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-v5.4/Documentation/infiniband/ |
| D | core_locking.rst | 14 all of the methods in struct ib_device may sleep. The exceptions
27 which may not sleep and must be callable from any context.
63 some serialization may be required to get sensible results. For
64 example, a consumer may safely call ib_poll_cq() on multiple CPUs
97 may be process context, softirq context, or interrupt context.
98 Upper level protocol consumers may not sleep in a callback.
113 An upper level protocol consumer may begin using an IB device as
|
| /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/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/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/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/Documentation/networking/device_drivers/intel/ |
| D | ixgb.rst | 147 dropped receives, this value may be set too high, causing the driver to
224 behavior after modifying this register may be undefined (possibly errors of
226 back to 22 (setpci -d 8086:1a48 e6.b=22) may be required to get back to a
252 # some of the defaults may be different for your kernel
255 # several network benchmark tests, your mileage may vary
384 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4
387 The CRC errors may be received either by the Intel(R) PRO/10GbE CX4
389 cable assembly may resolve the issue.
393 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4 Server
395 (1 m or shorter). If this situation occurs, using a longer cable may resolve
[all …]
|
