| /linux/Documentation/driver-api/firmware/ |
| H A 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 …]
|
| H A D | firmware_cache.rst | 32 userspace for the firmware request through the sysfs fallback mechanism
43 * The timeout for the fallback mechanism is temporarily reduced to 10 seconds
50 cache mechanism but must not use the firmware API on suspend.
|
| /linux/Documentation/filesystems/nfs/ |
| H A 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 …]
|
| /linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 97 bool "Enable the firmware sysfs fallback mechanism"
102 loading to the kernel through userspace as a fallback mechanism
107 built-in. For details on how to work with the sysfs fallback mechanism
116 this is known as the driver using the custom fallback mechanism.
117 If the custom fallback mechanism is used userspace must always
119 mechanism is disabled, and failed requests will linger forever.
124 can no longer be relied upon as a fallback mechanism. Linux no longer
125 relies on or uses a fallback mechanism in userspace. If you need to
132 mechanism can never be removed from the kernel.
135 require a fallback mechanism and have a userspace mechanism ready to
[all …]
|
| H A D | fallback.c | 15 * firmware fallback mechanism
68 * fw_load_sysfs_fallback() - load a firmware via the sysfs fallback mechanism
203 * firmware_fallback_sysfs() - use the fallback mechanism to find firmware
209 * @ret: return value from direct lookup which triggered the fallback mechanism
212 * a fallback mechanism through userspace by exposing a sysfs loading
214 * loading interface. This sysfs fallback mechanism may be disabled completely
218 * mechanism. A system may want to enforce the sysfs fallback mechanism at all
|
| H A 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
|
| H A D | firmware.h | 15 * @FW_OPT_UEVENT: Enables the fallback mechanism to send a kobject uevent
19 * @FW_OPT_USERHELPER: Enable the fallback mechanism, in case the direct
27 * firmware caching mechanism.
28 * @FW_OPT_NOFALLBACK_SYSFS: Disable the sysfs fallback mechanism. Takes
|
| /linux/Documentation/admin-guide/ |
| H A 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
|
| H A 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
|
| H A D | dell_rbu.rst | 54 The driver supports two types of update mechanism; monolithic and packetized.
55 These update mechanism depends upon the BIOS currently running on the system.
59 In case of packet mechanism the single memory can be broken in smaller chunks
73 In the packet update mechanism, the user needs to create a new file having
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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
|
| H A D | special-register-buffer-data-sampling.rst | 14 to the core through the special register mechanism that is susceptible
62 Mitigation mechanism
86 The microcode updates provide an opt-out mechanism (RNGDS_MITG_DIS) to disable
89 disable the mitigation using this opt-out mechanism, RDRAND and RDSEED do not
91 processors memory accesses. The opt-out mechanism does not affect Intel SGX
|
| /linux/include/linux/sunrpc/ |
| H A 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. */
|
| /linux/Documentation/driver-api/soundwire/ |
| H A 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
|
| /linux/Documentation/locking/ |
| H A 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
|
| /linux/tools/testing/selftests/firmware/ |
| H A 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"
|
| /linux/drivers/platform/x86/amd/ |
| H A D | Kconfig | 26 WBRF(Wifi Band RFI mitigation) mechanism allows Wifi drivers
30 AMD provides an ACPI based mechanism to support WBRF on platform with
33 This mechanism will only be activated on platforms that advertise a
|
| /linux/Documentation/driver-api/i3c/ |
| H A 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 Provisioned 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
|
| /linux/net/sunrpc/auth_gss/ |
| H A D | gss_mech_switch.c | 89 * gss_mech_register - register a GSS mechanism
90 * @gm: GSS mechanism handle
104 dprintk("RPC: registered gss mechanism %s\n", gm->gm_name); in gss_mech_register()
110 * gss_mech_unregister - release a GSS mechanism
111 * @gm: GSS mechanism handle
119 dprintk("RPC: unregistered gss mechanism %s\n", gm->gm_name); in gss_mech_unregister()
230 * @gm: GSS mechanism handle
278 * supported mechanism. Otherwise a negative errno is returned.
|
| /linux/drivers/media/pci/intel/ipu6/ |
| H A D | ipu6.h | 122 * IPU6 must configure correct arbitration mechanism related to the IOSF VC
129 /* Currently chosen arbitration mechanism for VC0 */
133 /* Currently chosen arbitration mechanism for VC1 */
138 * MMU Invalidation HW bug workaround by ZLW mechanism
140 * Old IPU6 MMUV2 has a bug in the invalidation mechanism which might result in
147 * or Zero length write, is pre-fetch mechanism to pre-fetch the pages in
191 * ZLW(Zero Length Write) is a mechanism to enable VT-d pre-fetching on IOMMU.
|
| /linux/tools/perf/pmu-events/arch/x86/knightslanding/ |
| H A D | frontend.json | 3 …ront end resteers for any branch as a result of another branch handling mechanism in the front end…
11 …esteers for conditional branches as a result of another branch handling mechanism in the front end…
19 …nt end resteers for RET branches as a result of another branch handling mechanism in the front end…
|
| /linux/arch/arm64/include/asm/ |
| H A D | cpu_ops.h | 21 * mechanism for doing so, tests whether it is possible to boot
27 * mechanism-specific information.
28 * @cpu_disable: Prepares a cpu to die. May fail for some mechanism-specific
|
| /linux/kernel/irq/ |
| H A D | Kconfig | 13 # Enable the generic irq autoprobe mechanism
38 # Alpha specific irq affinity mechanism
42 # Interrupt injection mechanism
|
| /linux/drivers/platform/x86/hp/hp-bioscfg/ |
| H A D | spmobj-attributes.c | 121 bioscfg_drv.spm_data.mechanism = data.state; in update_spm_state()
122 if (bioscfg_drv.spm_data.mechanism) in update_spm_state()
216 spm_mechanism_types[bioscfg_drv.spm_data.mechanism]); in key_mechanism_show()
244 bioscfg_drv.spm_data.mechanism = SIGNING_KEY; in sk_store()
280 bioscfg_drv.spm_data.mechanism = ENDORSEMENT_KEY; in kek_store()
371 bioscfg_drv.spm_data.mechanism = 0; in hp_populate_secure_platform_data()
|
| /linux/include/linux/ |
| H A D | seqlock_types.h | 12 * This is the raw counting mechanism, without any writer protection.
20 * This mechanism can't be used if the protected data contains pointers,
23 * If the write serialization mechanism is one of the common kernel
|