Searched full:potentially (Results 1 – 25 of 151) sorted by relevance
1234567
| /Documentation/ABI/stable/ |
| D | sysfs-class-rfkill | 62 transmitter is (potentially) active
76 The transmitter is (potentially) active.
90 The transmitter is (potentially) active.
|
| /Documentation/ABI/removed/ |
| D | net_dma | 7 coherency issues of the cpu potentially touching the buffers
|
| D | sysfs-mce | 22 risk of deadlock. Higher tolerant values trade potentially
|
| /Documentation/devicetree/bindings/firmware/ |
| D | cznic,turris-mox-rwtm.txt | 7 This device tree node should be used on Turris Mox, or potentially another A3700
|
| /Documentation/userspace-api/media/v4l/ |
| D | v4l2grab-example.rst | 10 libv4l handlers. The advantage is that this grabber can potentially work
|
| /Documentation/devicetree/bindings/fpga/ |
| D | lattice-ice40-fpga-mgr.txt | 11 clock signal potentially jamming other devices on the
|
| /Documentation/admin-guide/hw-vuln/ |
| D | vmscape.rst | 38 Kernel tracks when a CPU has run a potentially malicious guest and issues an
86 run a potentially malicious guest and issues an IBPB before the first
|
| D | srso.rst | 22 control the speculative target of a subsequent kernel RET, potentially
130 - potentially create and pin an additional workload on the sibling
168 function srso_alias_safe_ret() which results in evicting a potentially
|
| D | tsx_async_abort.rst | 30 allow an authenticated user to potentially enable
58 Because the buffers are potentially shared between Hyper-Threads cross
63 which in turn potentially leaks data stored in the buffers.
|
| D | l1tf.rst | 177 by a potentially malicious guest, it also flushes the guest
377 warning when the first VM is started in a potentially
390 warning when the first VM is started in a potentially
399 warning when the first VM is started in a potentially
404 started in a potentially insecure configuration.
|
| /Documentation/power/regulator/ |
| D | design.rst | 12 for the system, potentially including lasting hardware damage.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-atr.yaml | 17 called the "alias" and is (potentially) different from the physical
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 10 potentially including additional information.
75 and the set of MSIs they can potentially generate.
|
| /Documentation/core-api/ |
| D | protection-keys.rst | 26 Being a CPU register, PKRU is inherently thread-local, potentially giving each
44 Being a CPU register, POR_EL0 is inherently thread-local, potentially giving
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci-ep.yaml | 51 potentially conflicting domain numbers may be assigned to endpoint
|
| D | pci.txt | 18 host bridges in the system, otherwise potentially conflicting domain numbers
|
| /Documentation/admin-guide/device-mapper/ |
| D | striped.rst | 8 potentially provide improved I/O throughput by utilizing several physical
|
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 32 give a rough estimate of how memory can potentially be allocated.
|
| /Documentation/scheduler/ |
| D | sched-debug.rst | 36 trapped and potentially data must be migrated. However, the higher the scan
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 59 In the future, other potentially dangerous kernel features could become
|
| /Documentation/arch/arm/ |
| D | vlocks.rst | 127 of CPUs potentially contending the lock is small enough). This
147 This cuts down on the fast-path latency, as well as potentially
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 34 feature implemented introduces more code, more maintenance and potentially more
|
| /Documentation/virt/hyperv/ |
| D | coco.rst | 73 protect itself against a potentially malicious paravisor just like it
74 protects against a potentially malicious guest.
174 includes a compromised and potentially malicious host, the guest must guard
|
| /Documentation/arch/x86/ |
| D | tlb.rst | 15 time. This could potentially cost many more instructions, but
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 54 function ensures a potentially used bounce buffer is freed::
|
1234567