| /Linux-v4.19/security/smack/ |
| D | smack_access.c | 88 int may = -ENOENT; in smk_access_entry() local
94 may = srp->smk_access; in smk_access_entry()
102 if ((may & MAY_WRITE) == MAY_WRITE) in smk_access_entry()
103 may |= MAY_LOCK; in smk_access_entry()
104 return may; in smk_access_entry()
123 int may = MAY_NOT; in smk_access() local
173 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access()
177 if (may <= 0 || (request & may) != request) { in smk_access()
187 if (may & MAY_BRINGUP) in smk_access()
227 int may; in smk_tskacc() local
[all …]
|
| D | smack_lsm.c | 1036 int may; in smack_inode_init_security() local
1043 may = smk_access_entry(skp->smk_known, dsp->smk_known, in smack_inode_init_security()
1053 if (may > 0 && ((may & MAY_TRANSMUTE) != 0) && in smack_inode_init_security()
1727 int may; in smack_mmap_file() local
1768 may = smk_access_entry(srp->smk_subject->smk_known, in smack_mmap_file()
1771 if (may == -ENOENT) in smack_mmap_file()
1772 may = srp->smk_access; in smack_mmap_file()
1774 may &= srp->smk_access; in smack_mmap_file()
1779 if (may == 0) in smack_mmap_file()
1807 if ((may | mmay) != mmay) { in smack_mmap_file()
[all …]
|
| /Linux-v4.19/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-v4.19/Documentation/virtual/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-v4.19/Documentation/isdn/ |
| D | README.diversion | 5 document. The diversion services may be used with all cards supported by
45 only supported by isdn phones. Incoming calls may be diverted
48 The diversions may be invoked statically in the providers exchange
51 forwarding reason is met. Activated static services may also be
56 In this case all incoming calls are checked by rules that may be
64 Actions that may be invoked by a rule are ignore, proceed, reject,
77 driver for passive isdn cards. All HiSax supported cards may be used for
80 CFU, CFNR, CFB activated on an MSN-line. The static services may not be
84 not supported but may use the tty devices for this purpose.
85 The dynamic diversion services may be used in all countries if the provider
[all …]
|
| D | README.hfc-pci | 1 The driver for the HFC-PCI and HFC-PCI-A chips from CCD may be used
5 may be logged.
23 If more than one HFC-PCI cards are installed, a specific card may be selected
32 0xd000 you may give the parameters type=35,35,35 io=0xdc00,0xd400,0xd00
36 invoked which may not give the wanted result.
|
| /Linux-v4.19/Documentation/sysctl/ |
| D | user.txt | 36 user namespace may create.
41 user namespace may create.
46 user namespace may create.
51 current user namespace may create.
56 user namespace may create.
61 user namespace may create.
66 user namespace may create.
|
| /Linux-v4.19/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-v4.19/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-v4.19/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-v4.19/Documentation/acpi/ |
| D | DSD-properties-rules.txt | 9 namespace. In principle, the format of the data may be arbitrary, but it has to
23 It also may be regarded as the definition of a key and the associated data type
38 Property sets may be hierarchical. That is, a property set may contain
39 multiple property subsets that each may contain property subsets of its
59 principle, the property set may still not be regarded as a valid one.
61 For example, that applies to device properties which may cause kernel code
64 particular, that may happen if the kernel code uses device properties to
70 In all cases in which kernel code may do something that will confuse AML as a
83 avoided. For this reason, it may not be possible to make _DSD return a property
85 sake of code re-use, it may make sense to provide as much of the configuration
|
| /Linux-v4.19/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-v4.19/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-v4.19/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-v4.19/Documentation/powerpc/ |
| D | syscall64-abi.txt | 12 [*] Some syscalls (typically low-level management functions) may have
59 to the usual transactional memory semantics. A syscall may or may not result
81 following differences. Some vsyscalls may have different calling sequences.
89 The vsyscall may or may not use the caller's stack frame save areas.
105 may or may not result in the transaction being doomed by hardware.
|
| /Linux-v4.19/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-v4.19/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 3 # As this may inadvertently break the build, only allow the user
35 Choose this option to turn on extra driver debugging that may affect
48 paths that may slow the system down and if hit hang the machine.
59 Enable additional logging that may help track down the cause of
73 ordinary tests, but may be vital for post-mortem debugging when
86 Choose this option to turn on extra driver debugging that may affect
98 Choose this option to turn on extra driver debugging that may affect
110 Choose this option to turn on extra driver debugging that may affect
140 and may trigger unintended HW side-effects as they break strict
|
| /Linux-v4.19/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-v4.19/Documentation/thermal/ |
| D | nouveau_thermal | 16 cannot access any of the i2c external monitoring chips it may find. If you
18 interface is likely not to work. This document may then not cover your situation
34 WARNING: Some of these thresholds may not be used by Nouveau depending
59 You may also have the following attribute:
72 [PWM_min, PWM_max] range, the reported fan speed (RPM) may not be accurate
78 Thermal management on Nouveau is new and may not work on all cards. If you have
|
| /Linux-v4.19/Documentation/infiniband/ |
| D | core_locking.txt | 11 all of the methods in struct ib_device may sleep. The exceptions
24 which may not sleep and must be callable from any context.
59 some serialization may be required to get sensible results. For
60 example, a consumer may safely call ib_poll_cq() on multiple CPUs
92 may be process context, softirq context, or interrupt context.
93 Upper level protocol consumers may not sleep in a callback.
107 An upper level protocol consumer may begin using an IB device as
|
| /Linux-v4.19/Documentation/media/uapi/ |
| D | fdl-appendix.rst | 67 may not explain any mathematics.) The relationship could be a matter of
127 You may copy and distribute the :ref:`Document <fdl-document>` in any
131 you add no other conditions whatsoever to those of this License. You may
133 copying of the copies you make or distribute. However, you may accept
138 You may also lend copies, under the same conditions stated above, and
139 you may publicly display copies.
154 with all words of the title equally prominent and visible. You may add
191 You may copy and distribute a :ref:`Modified Version <fdl-modified>`
205 the Document). You may use the same title as a previous version if
259 versions it was based on. These may be placed in the “History”
[all …]
|
| /Linux-v4.19/Documentation/networking/ |
| 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-v4.19/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-v4.19/Documentation/media/uapi/v4l/ |
| D | dev-touch.rst | 16 Sensors may be Optical, or Projected Capacitive touch (PCT).
19 some systems, this may be performed on the ASIC and the raw data is purely a
30 A touch input may be determined by comparing the raw capacitance measurement to
56 A touch device may support any I/O method.
|
