| /openbmc/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 …]
|
| /openbmc/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 …]
|
| /openbmc/linux/drivers/base/firmware_loader/ |
| H A 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 …]
|
| H A 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
|
| 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
|
| /openbmc/docs/designs/ |
| H A D | firmware-update-via-blobs.md | 9 The BMC needs a mechanism for receiving a new firmware image from the host
19 update mechanism that can be done in-band between the host and the BMC.
39 - Any update mechanism must provide support for UBI tarballs and legacy (static
41 support for any image type simply by implementing a mechanism for handling it.
43 - Any update mechanism must allow for triggering an image verification step
46 - Any update mechanism must allow implementing the data staging via different
49 - Any update mechanism must provide a handshake or equivalent protocol for
54 - Any update mechanism must attempt to maintain security, insomuch as not
82 layout) or the UBI mechanism, or both. The flags provided to the open command
83 identify the mechanism selected by the client-side. The stat command will return
[all …]
|
| H A D | bmc-service-failure-debug-and-recovery.md | 112 | Condition | Mechanism |
131 | Condition | Mechanism |
163 | Severity | BMC Recovery Mechanism | Used for …
180 The need to escalate above mechanism 1 should come with data that captures why
184 in the reset. Therefore, mechanism 2 should exist in the system design and its
193 mechanism, support for 2 can be implemented in BMC userspace.
195 Mechanism 1 is typically initiated by the usual in-band interfaces, either IPMI
196 or PLDM. In order to avoid these in the implementation of mechanism 2, the host
202 #### Behavioural Requirements for Recovery Mechanism 2
204 The system behaviour requirement for the mechanism is:
[all …]
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/qemu/docs/system/ |
| H A D | vnc-security.rst | 121 strength of the authentication depends on the exact mechanism
122 configured. If the chosen mechanism also provides a SSF layer, then it
125 Refer to the later docs on how to choose the exact SASL mechanism used
138 If the desired SASL authentication mechanism does not supported SSF
158 implementation or host. When SASL is enabled, the mechanism
165 encryption, otherwise the SASL mechanism will have to provide
167 used is drastically reduced. In fact only the GSSAPI SASL mechanism
169 versions of QEMU referred to the DIGEST-MD5 mechanism, however, it has
171 never be used any more. The SCRAM-SHA-256 mechanism provides a simple
182 This says to use the 'GSSAPI' mechanism with the Kerberos v5 protocol,
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-printing/cups/cups-pk-helper/ |
| H A D | dont-localize-org.opensuse.CupsPkHelper.Mechanism.service.patch | 10 - input: 'org.opensuse.cupspkhelper.mechanism.policy.in',
11 - output: 'org.opensuse.cupspkhelper.mechanism.policy',
19 +# input: 'org.opensuse.cupspkhelper.mechanism.policy.in',
20 +# output: 'org.opensuse.cupspkhelper.mechanism.policy',
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | README.md | 1 # Secure Flash Update Mechanism
4 update mechanism.
96 …ipmipci`, `ipminet`, `ipmipci-skip-bridge-disable` | The data transport mechanism, typically `ipmi…
101 If you're using an LPC data transfer mechanism, you'll need two additional
105 If you're using a net data transfer mechanism, you'll also need two additional
131 The image flashing mechanism itself is the initramfs stage during reboot. It
163 transfer the data. By default, the data-in-IPMI mechanism is enabled.
188 If a platform enables p2a as the transport mechanism, a specific vendor must be
196 If a platform enables lpc as the transport mechanism, a specific vendor must be
205 A platform may also enable the network transport mechanism.
[all …]
|
| /openbmc/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. */
|
| /openbmc/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
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
| H A D | data_handler.hpp | 11 * Each data transport mechanism must implement the DataInterface.
19 * Initialize data transport mechanism. Calling this should be idempotent
27 * Close the data transport mechanism.
53 * the mechanism.
|
| /openbmc/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
|
| /openbmc/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"
|
| /openbmc/qemu/include/hw/riscv/ |
| H A D | boot_opensbi.h | 48 * lottery mechanism can potentially overwrite the previous booting
56 * to use the relocation lottery mechanism.
78 * lottery mechanism can potentially overwrite the previous booting
86 * to use the relocation lottery mechanism.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-printing/cups/ |
| H A D | cups-pk-helper_0.2.7.bb | 14 file://dont-localize-org.opensuse.CupsPkHelper.Mechanism.service.patch \
20 …S}/src/org.opensuse.cupspkhelper.mechanism.policy.in ${D}${datadir}/polkit-1/actions/org.opensuse.…
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | kvm-pv.rst | 45 Enable asynchronous page fault mechanism. Supported since Linux v2.6.38.
61 Enable paravirtualized TLB flush mechanism. Supported since Linux v4.16.
64 Enable paravirtualized IPI mechanism. Supported since Linux v4.19.
74 Enable interrupt based asynchronous page fault mechanism. Supported since Linux
|
| /openbmc/qemu/docs/devel/ |
| H A D | rcu.rst | 4 Read-copy update (RCU) is a synchronization mechanism that is used to
17 RCU is fundamentally a "wait-to-finish" mechanism. The read side marks
27 the system will have a single instance of the RCU mechanism; a single
28 mechanism can be used for an arbitrary number of "things", without
142 synchronization mechanism.
162 synchronization mechanism to coordinate the accesses.
167 Mark a thread as taking part in the RCU mechanism. Such a thread
172 Mark a thread as not taking part anymore in the RCU mechanism.
244 may be used as a restricted reference-counting mechanism. For example,
325 ``foo_unref`` could use a mechanism such as bottom halves to move deallocation
|
| /openbmc/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 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
|
| /openbmc/u-boot/drivers/i2c/muxes/ |
| H A D | Kconfig | 6 one of several buses using some sort of control mechanism. The
15 one of several buses using some sort of control mechanism. The
25 response mechanism where masters have to claim the bus by asserting
|
| /openbmc/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…
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…
|