/openbmc/linux/tools/perf/scripts/perl/ |
H A D | rwtop.pl | 96 $sa->safe(1);
|
/openbmc/linux/Documentation/networking/ |
H A D | sctp.rst | 30 module removal of lksctp is not yet a safe activity.
|
H A D | msg_zerocopy.rst | 33 The kernel returns a notification when it is safe to modify data. 95 feature is implemented as a flag. It is safe to mix calls with the flag 102 The kernel has to notify the process when it is safe to reuse a
|
/openbmc/linux/Documentation/devicetree/bindings/cpufreq/ |
H A D | cpufreq-st.txt | 18 Example [safe]
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/dovecot/dovecot/ |
H A D | 0001-configure.ac-convert-AC_TRY_RUN-to-AC_TRY_LINK-state.patch | 6 This is not completely safe, but it's the least invasive fix.
|
/openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/ |
H A D | 0018-test-bus-error-strerror-is-assumed-to-be-GNU-specifi.patch | 40 /* Just check that strerror really is not thread-safe. */
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/sdbus-c++/sdbus-c++-libsystemd/ |
H A D | 0018-test-bus-error-strerror-is-assumed-to-be-GNU-specifi.patch | 40 /* Just check that strerror really is not thread-safe. */
|
/openbmc/qemu/docs/devel/ |
H A D | multiple-iothreads.txt | 35 because a lot of QEMU's code historically was not thread-safe. 91 AioContext is not thread-safe so some rules must be followed when using file 107 AioContexts simultaneously. Therefore, it is only safe for code holding the
|
H A D | multi-thread-tcg.rst | 64 DESIGN REQUIREMENT: Make access to lookup structures safe with 163 which is designed for concurrent safe lookup. 186 we need to ensure it is done in a safe way so no inconsistent state is 214 work as "safe work" and exiting the cpu run loop. This ensure by the 277 by themselves to provide safe lockless access by ensuring for example
|
H A D | lockcnt.txt | 6 callbacks like this is not safe: 63 - reference counting is often applied to code that is not thread-safe 74 counting in code that has to be both thread-safe and reentrant.
|
/openbmc/linux/Documentation/devicetree/bindings/regulator/ |
H A D | maxim,max8997.yaml | 42 specify at least one voltage level (which would be a safe operating 54 specify at least one voltage level (which would be a safe operating 66 specify at least one voltage level (which would be a safe operating
|
/openbmc/linux/Documentation/arch/arm/ |
H A D | cluster-pm-race-avoidance.rst | 29 cluster-level operations are only performed when it is truly safe to do 37 methods of coordination are required in order to guarantee safe 177 When a CPU reaches the CPU_UP state, it is safe for the CPU to 184 CPU is coherent yet, but it does mean that it is safe to resume 225 In order to enable safe coordination in such situations, it is important 507 is needed for safe transitions at the cluster level.
|
/openbmc/linux/Documentation/powerpc/ |
H A D | kaslr-booke32.rst | 21 build and boot. This not so much safe so additionally the bootloader may
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lcov/ |
H A D | lcov_1.16.bb | 38 perl-module-safe \
|
/openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
H A D | battery.yaml | 111 description: safe range of ambient temperature 117 description: safe range of battery temperature
|
/openbmc/linux/arch/arm/boot/dts/qcom/ |
H A D | qcom-apq8026-huawei-sturgeon.dts | 332 qcom,fast-charge-safe-voltage = <4370000>; 336 qcom,fast-charge-safe-current = <600000>;
|
/openbmc/linux/fs/crypto/ |
H A D | Kconfig | 27 # strongly recommended to enable optimized implementations too. It is safe to
|
/openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
H A D | fsl,vf610-adc.yaml | 59 operating requirements. A safe default across a wide range of R_as and
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | cpu-feature-registers.rst | 44 The infrastructure exports a value that is safe across all the 107 c) The value of a 'visible' field holds the system wide safe value 206 wide safe value.
|
/openbmc/linux/drivers/net/ethernet/alteon/ |
H A D | Kconfig | 45 The safe and default value for this is N.
|
/openbmc/linux/drivers/net/wireless/broadcom/b43/ |
H A D | Kconfig | 23 It is safe to include both b43 and b43legacy as the underlying glue 89 It's safe to select Y here, even if you don't have a B43 SDIO device.
|
/openbmc/linux/Documentation/livepatch/ |
H A D | callbacks.rst | 78 safe and to stop the current patching request. (When no pre-patch 79 callback is provided, the transition is assumed to be safe.) If a
|
H A D | system-state.rst | 10 add, and even remove fixes. And it is typically safe to replace any version 14 change the system behavior or state so that it is no longer safe to
|
/openbmc/linux/fs/overlayfs/ |
H A D | Kconfig | 38 If backward compatibility is not an issue, then it is safe and 104 issue, then it is safe and recommended to say Y here.
|
/openbmc/linux/Documentation/security/ |
H A D | landlock.rst | 15 backdoored (i.e. untrusted), Landlock's features must be safe to use from the 31 Guiding principles for safe access controls
|