| /linux/Documentation/virt/kvm/ |
| A D | timekeeping.rst | 31 timekeeping which may be difficult to find elsewhere, specifically,
283 functionality that may be more computationally expensive to implement.
383 small, may be exposed to the OS and any virtualization environment.
393 exact clock and bus design, the drift may or may not be fixed in absolute
394 error, and may accumulate over time.
398 clock frequency and harmonics of it, which may be required to pass FCC
408 states may be problematic for TSC as well. The TSC may stop advancing in such
420 may or may not run the TSC at the same rate, and because the frequency change
421 may be staggered or slewed, at some points in time, the TSC rate may not be
488 it may very well make that assumption. It may expect it to remain true to very
[all …]
|
| /linux/arch/m68k/ifpsp060/ |
| A 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/security/smack/ |
| A 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
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()
237 if (may < 0) in smk_tskacc()
[all …]
|
| A D | smack_lsm.c | 964 int may; in smack_inode_init_security() local
981 if (may > 0 && ((may & MAY_TRANSMUTE) != 0) && in smack_inode_init_security()
1648 int may; in smack_mmap_file() local
2965 int may; in smack_shm_associate() local
2980 int may; in smack_shm_shmctl() local
3017 int may; in smack_shm_shmat() local
3054 int may; in smack_sem_associate() local
3069 int may; in smack_sem_semctl() local
3149 int may; in smack_msg_queue_associate() local
3164 int may; in smack_msg_queue_msgctl() local
[all …]
|
| /linux/Documentation/admin-guide/sysctl/ |
| A 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/Documentation/livepatch/ |
| A 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:
103 conventions and may require special handling in the unwinder, e.g.
140 For some architectures this may change at runtime as a result of dynamic
150 boundaries. Note that it may be reliable to unwind across certain
[all …]
|
| /linux/Documentation/ABI/testing/ |
| A 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/Documentation/security/ |
| A 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
98 file may supply more than one ACL.
232 this may include one or more of the following:
258 1. its reference count may be changed;
283 process as the instantiating process may need to create them.
292 1. The reference count may be altered.
394 ``get_cred()`` as this may race with ``commit_cred()``.
423 magic. This may not be used for pointer members as what they point to may
430 As previously mentioned, a task may only alter its own credentials, and may not
[all …]
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| A 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/Documentation/firmware-guide/acpi/ |
| A 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/Documentation/staging/ |
| A 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/drivers/atm/ |
| A D | Kconfig | 61 Note that extended debugging may create certain race conditions
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
108 may or may not improve throughput.
116 are also set may or may not improve throughput.
138 default setting. Enabling 4W if 8W is also set may or may not
147 8W are also set may or may not improve throughput.
176 Note that extended debugging may create certain race conditions
318 messages is controlled by a bitmap. This may be specified as a
351 may improve the responsive of the host.
[all …]
|
| /linux/Documentation/driver-api/ |
| A 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/Documentation/admin-guide/mm/ |
| A 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/Documentation/userspace-api/media/v4l/ |
| A D | dev-encoder.rst | 25 2. The meaning of words "must", "may", "should", etc. is as per `RFC
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
140 6. Any additional encoder capabilities may be discovered by querying
245 the desired frame interval; the encoder may adjust it to
259 ``OUTPUT`` queue is just a hint, the application may provide raw
296 the desired coded frame interval; the encoder may adjust it to
376 :c:func:`VIDIOC_REQBUFS`. This may be performed in any order.
437 on the coded format, but may include the following implications:
471 order; however, there may be other reasons for this as well),
[all …]
|
| A 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
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
425 YUV format may be preferred over an RGB format if an additional
511 ``CAPTURE`` queue. The client may choose a different format than
556 The decoder may adjust the compose rectangle to the nearest
687 The format obtained in the query may be then used with
793 it may be affected as per normal decoder operation.
852 A seek may result in the `Dynamic Resolution Change` sequence being
[all …]
|
| /linux/LICENSES/deprecated/ |
| A D | GFDL-1.2 | 76 textbook of mathematics, a Secondary Section may not explain any
144 You may copy and distribute the Document in any medium, either
148 conditions whatsoever to those of this License. You may not use
155 you may publicly display copies.
168 visible. You may add other material on the covers in addition.
248 may not be included in the Modified Version.
269 Front-Cover Text and one of Back-Cover Text may be added by (or
273 you may not add another; but you may replace the old one, on explicit
342 Translation is considered a kind of modification, so you may
345 permission from their copyright holders, but you may include
[all …]
|
| A 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
130 you may publicly display copies.
142 visible. You may add other material on the covers in addition.
222 may not be included in the Modified Version.
242 Front-Cover Text and one of Back-Cover Text may be added by (or
246 you may not add another; but you may replace the old one, on explicit
313 Translation is considered a kind of modification, so you may
316 permission from their copyright holders, but you may include
[all …]
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| A 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/Documentation/ABI/stable/ |
| A 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/drivers/gpu/drm/i915/ |
| A 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
194 and may trigger unintended HW side-effects as they break strict
[all …]
|
| /linux/Documentation/userspace-api/media/ |
| A D | fdl-appendix.rst | 127 You may copy and distribute the :ref:`Document <fdl-document>` in any
139 you may publicly display copies.
259 versions it was based on. These may be placed in the "History"
260 section. You may omit a network location for a work that was
293 You may add a section entitled "Endorsements", provided it contains
299 You may add a passage of up to five words as a
308 entity you are acting on behalf of, you may not add another; but you may
323 You may combine the :ref:`Document <fdl-document>` with other
352 You may make a collection consisting of the
397 original versions of these Invariant Sections. You may include a
[all …]
|
| /linux/Documentation/powerpc/ |
| A 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.
|
| /linux/Documentation/devicetree/bindings/powerpc/ |
| A 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/Documentation/devicetree/bindings/pinctrl/ |
| A 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.
137 device; they may be grandchildren, for example. Whether this is legal, and
|