Searched full:mechanism (Results 1 – 25 of 2757) sorted by relevance
12345678910>>...111
| /kernel/linux/linux-6.6/Documentation/driver-api/firmware/ |
| D | fallback-mechanisms.rst | 5 A fallback mechanism is supported to allow to overcome failures to do a direct
8 configuration options related to supporting the firmware fallback mechanism are:
11 mechanism. Most distributions enable this option today. If enabled but
13 mechanism is available and for the request_firmware_nowait() call.
15 enable the kobject uevent fallback mechanism on all firmware API calls
18 fallback mechanism: if this kconfig option is enabled and your second
20 informing the kernel that you have a custom fallback mechanism and it will
28 the kobject uevent fallback mechanism will never take effect even
31 Justifying the firmware fallback mechanism
36 fallback mechanism:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/firmware/ |
| D | fallback-mechanisms.rst | 5 A fallback mechanism is supported to allow to overcome failures to do a direct
8 configuration options related to supporting the firmware fallback mechanism are:
11 mechanism. Most distributions enable this option today. If enabled but
13 mechanism is available and for the request_firmware_nowait() call.
15 enable the kobject uevent fallback mechanism on all firmware API calls
18 fallback mechanism: if this kconfig option is enabled and your second
20 informing the kernel that you have a custom fallback mechanism and it will
28 the kobject uevent fallback mechanism will never take effect even
31 Justifying the firmware fallback mechanism
36 fallback mechanism:
[all …]
|
| /kernel/linux/linux-5.10/drivers/base/firmware_loader/ |
| D | Kconfig | 72 bool "Enable the firmware sysfs fallback mechanism"
76 loading to the kernel through userspace as a fallback mechanism
81 built-in. For details on how to work with the sysfs fallback mechanism
90 this is known as the driver using the custom fallback mechanism.
91 If the custom fallback mechanism is used userspace must always
93 mechanism is disabled, and failed requests will linger forever.
98 can no longer be relied upon as a fallback mechanism. Linux no longer
99 relies on or uses a fallback mechanism in userspace. If you need to
106 mechanism can never be removed from the kernel.
109 require a fallback mechanism and have a userspace mechanism ready to
[all …]
|
| D | fallback.h | 13 * Helps describe and fine tune the fallback mechanism.
15 * @force_sysfs_fallback: force the sysfs fallback mechanism to be used
19 * @ignore_sysfs_fallback: force to disable the sysfs fallback mechanism.
23 * @loading_timeout: the timeout to wait for the fallback mechanism before
|
| /kernel/linux/linux-5.10/Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 24 Authentication for NFS. Although GSSAPI is itself completely mechanism
25 agnostic, in many cases only the KRB5 mechanism is supported by NFS
28 The Linux kernel, at the moment, supports only the KRB5 mechanism, and
46 NFS Server Legacy Upcall Mechanism
49 The classic upcall mechanism uses a custom text based upcall mechanism
53 This upcall mechanism has 2 limitations:
67 NFS Server New RPC Upcall Mechanism
70 The newer upcall mechanism uses RPC over a unix socket to a daemon
76 This upcall mechanism uses the kernel rpc client and connects to the gssproxy
84 legacy mechanism. To switch to the new mechanism, gss-proxy must bind
[all …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 24 Authentication for NFS. Although GSSAPI is itself completely mechanism
25 agnostic, in many cases only the KRB5 mechanism is supported by NFS
28 The Linux kernel, at the moment, supports only the KRB5 mechanism, and
46 NFS Server Legacy Upcall Mechanism
49 The classic upcall mechanism uses a custom text based upcall mechanism
53 This upcall mechanism has 2 limitations:
67 NFS Server New RPC Upcall Mechanism
70 The newer upcall mechanism uses RPC over a unix socket to a daemon
76 This upcall mechanism uses the kernel rpc client and connects to the gssproxy
84 legacy mechanism. To switch to the new mechanism, gss-proxy must bind
[all …]
|
| /kernel/linux/linux-6.6/drivers/base/firmware_loader/ |
| D | Kconfig | 90 bool "Enable the firmware sysfs fallback mechanism"
95 loading to the kernel through userspace as a fallback mechanism
100 built-in. For details on how to work with the sysfs fallback mechanism
109 this is known as the driver using the custom fallback mechanism.
110 If the custom fallback mechanism is used userspace must always
112 mechanism is disabled, and failed requests will linger forever.
117 can no longer be relied upon as a fallback mechanism. Linux no longer
118 relies on or uses a fallback mechanism in userspace. If you need to
125 mechanism can never be removed from the kernel.
128 require a fallback mechanism and have a userspace mechanism ready to
[all …]
|
| D | fallback.c | 15 * firmware fallback mechanism
64 * fw_load_sysfs_fallback() - load a firmware via the sysfs fallback mechanism
199 * firmware_fallback_sysfs() - use the fallback mechanism to find firmware
205 * @ret: return value from direct lookup which triggered the fallback mechanism
208 * a fallback mechanism through userspace by exposing a sysfs loading
210 * loading interface. This sysfs fallback mechanism may be disabled completely
214 * mechanism. A system may want to enforce the sysfs fallback mechanism at all
|
| D | sysfs.h | 18 * Helps describe and fine tune the fallback mechanism.
20 * @force_sysfs_fallback: force the sysfs fallback mechanism to be used
24 * @ignore_sysfs_fallback: force to disable the sysfs fallback mechanism.
28 * @loading_timeout: the timeout to wait for the fallback mechanism before
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | syscall-user-dispatch.rst | 16 filters. Therefore a new mechanism is necessary.
32 configure the mechanism.
39 Since this mechanism is designed to capture syscalls issued by
51 A thread can setup this mechanism on supported kernels by executing the
57 disable the mechanism globally for that thread. When
86 process. It is not a mechanism for sandboxing system calls, and it
87 should not be seen as a security mechanism, since it is trivial for a
88 malicious application to subvert the mechanism by jumping to an allowed
93 Any fork or exec of the existing process resets the mechanism to
|
| D | initrd.rst | 32 mechanism" section below.
180 with an older mechanism, the following boot command line parameters
325 Obsolete root change mechanism
328 The following mechanism was used before the introduction of pivot_root.
338 In order to use this mechanism, you do not have to specify the boot
348 Note that the mechanism is incompatible with NFS and similar file
351 This old, deprecated mechanism is commonly called ``change_root``, while
352 the new, supported mechanism is called ``pivot_root``.
355 Mixed change_root and pivot_root mechanism
359 mechanism, you may create both ``/linuxrc`` and ``/sbin/init`` in your initrd
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/ |
| D | l1d_flush.rst | 6 mechanism to flush the L1D cache on context switch.
8 This mechanism can be used to address e.g. CVE-2020-0550. For applications
9 the mechanism keeps them safe from vulnerabilities, related to leaks
16 mechanism
39 mechanism is used, software fallback for the mitigation, is not supported.
53 By default the mechanism is disabled.
58 The mechanism does not mitigate L1D data leaks between tasks belonging to
|
| /kernel/linux/linux-6.6/include/linux/sunrpc/ |
| D | gss_api.h | 20 /* The mechanism-independent gss-api context: */
94 /* Each mechanism is described by the following struct: */
101 /* pseudoflavors supported by this mechanism: */
141 /* returns a mechanism descriptor given an OID, and increments the mechanism's
151 /* Returns a reference to a mechanism, given a name like "krb5" etc. */
|
| /kernel/linux/linux-5.10/include/linux/sunrpc/ |
| D | gss_api.h | 20 /* The mechanism-independent gss-api context: */
94 /* Each mechanism is described by the following struct: */
101 /* pseudoflavors supported by this mechanism: */
141 /* returns a mechanism descriptor given an OID, and increments the mechanism's
151 /* Returns a reference to a mechanism, given a name like "krb5" etc. */
|
| /kernel/linux/linux-6.6/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 8 mechanism (sync loss after two errors) and short CRCs used for the Bulk
13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
25 indication of a bus allocation issue. The interrupt mechanism can also help
60 Note that SoundWire does not provide a mechanism to detect illegal values
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /kernel/linux/linux-5.10/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 8 mechanism (sync loss after two errors) and short CRCs used for the Bulk
13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
25 indication of a bus allocation issue. The interrupt mechanism can also help
60 Note that SoundWire does not provide a mechanism to detect illegal values
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /kernel/linux/linux-6.6/Documentation/locking/ |
| D | robust-futex-ABI.rst | 8 Robust_futexes provide a mechanism that is used in addition to normal
23 mechanism, which handles uncontested locking without needing a system
80 lock variable used by the futex mechanism, in conjunction with
83 mechanism to register the address of that 'lock word' with the kernel.
91 that lock using the futex mechanism.
104 robust_futex mechanism doesn't care what else is in that structure, so
118 existing futex mechanism to wait for, and wakeup, locks. The kernels
164 used to the futex mechanism to wait on that address, and
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | robust-futex-ABI.rst | 8 Robust_futexes provide a mechanism that is used in addition to normal
23 mechanism, which handles uncontested locking without needing a system
80 lock variable used by the futex mechanism, in conjunction with
83 mechanism to register the address of that 'lock word' with the kernel.
91 that lock using the futex mechanism.
104 robust_futex mechanism doesn't care what else is in that structure, so
118 existing futex mechanism to wait for, and wakeup, locks. The kernels
164 used to the futex mechanism to wait on that address, and
|
| /kernel/linux/linux-5.10/tools/testing/selftests/firmware/ |
| D | fw_fallback.sh | 3 # This validates that the kernel will fall back to using the fallback mechanism
170 echo "$0: fallback mechanism immediately cancelled"
217 echo "$0: fallback mechanism works"
225 echo "$0: cancelling fallback mechanism works"
248 echo "$0: custom fallback loading mechanism works"
259 echo "$0: custom fallback loading mechanism works"
272 echo "$0: cancelling custom fallback mechanism works"
|
| /kernel/linux/linux-6.6/tools/testing/selftests/firmware/ |
| D | fw_fallback.sh | 3 # This validates that the kernel will fall back to using the fallback mechanism
170 echo "$0: fallback mechanism immediately cancelled"
217 echo "$0: fallback mechanism works"
225 echo "$0: cancelling fallback mechanism works"
248 echo "$0: custom fallback loading mechanism works"
259 echo "$0: custom fallback loading mechanism works"
272 echo "$0: cancelling custom fallback mechanism works"
|
| /kernel/linux/linux-5.10/Documentation/driver-api/i3c/ |
| D | protocol.rst | 61 The I3C protocol defines a mechanism to automatically discover devices present
65 The discovery mechanism is called DAA (Dynamic Address Assignment), because it
75 Provisional ID collision, otherwise the discovery mechanism may fail.
83 This mechanism is called IBI for In Band Interrupts, and as stated in the name,
98 The Hot-Join mechanism is similar to USB hotplug. This mechanism allows
106 This mechanism is relying on slave events to inform the master that a new
|
| /kernel/linux/linux-6.6/Documentation/driver-api/i3c/ |
| D | protocol.rst | 61 The I3C protocol defines a mechanism to automatically discover devices present
65 The discovery mechanism is called DAA (Dynamic Address Assignment), because it
75 Provisional ID collision, otherwise the discovery mechanism may fail.
83 This mechanism is called IBI for In Band Interrupts, and as stated in the name,
98 The Hot-Join mechanism is similar to USB hotplug. This mechanism allows
106 This mechanism is relying on slave events to inform the master that a new
|
| /kernel/linux/linux-5.10/drivers/hwspinlock/ |
| D | Kconfig | 26 provides a synchronisation mechanism for the various processors on
36 provides a synchronisation mechanism for the various processors
63 provides a synchronisation mechanism for the various processor on the
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | frontend.json | 3 …ront end resteers for any branch as a result of another branch handling mechanism in the front end…
10 …esteers for conditional branches as a result of another branch handling mechanism in the front end…
17 …nt end resteers for RET branches as a result of another branch handling mechanism in the front end…
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | initrd.rst | 32 mechanism" section below.
180 with an older mechanism, the following boot command line parameters
325 Obsolete root change mechanism
328 The following mechanism was used before the introduction of pivot_root.
338 In order to use this mechanism, you do not have to specify the boot
348 Note that the mechanism is incompatible with NFS and similar file
351 This old, deprecated mechanism is commonly called ``change_root``, while
352 the new, supported mechanism is called ``pivot_root``.
355 Mixed change_root and pivot_root mechanism
359 mechanism, you may create both ``/linuxrc`` and ``/sbin/init`` in your initrd
|
12345678910>>...111