Home
last modified time | relevance | path

Searched refs:scenarios (Results 1 – 25 of 119) sorted by relevance

12345

/OK3568_Linux_fs/kernel/Documentation/RCU/
H A Dtorture.rst178 complete all the scenarios in two batches, reducing the time to complete
185 Not all changes require that all scenarios be run. For example, a change
186 to Tree SRCU might run only the SRCU-N and SRCU-P scenarios using the
188 Large systems can run multiple copies of of the full set of scenarios,
199 Or 28 concurrent instances of each of two eight-CPU scenarios::
241 Files pertaining to all scenarios in a run reside in the top-level
273 As of v5.4, a successful run with the default set of scenarios produces
/OK3568_Linux_fs/buildroot/package/zstd/
H A DConfig.in.host6 scenarios at zlib-level and better compression ratios
H A DConfig.in6 scenarios at zlib-level and better compression ratios
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/pinctrl/
H A Dpinctrl-palmas.txt43 scenarios. So for GPIO7 if ti,palmas-override-powerhold is set
46 power off scenarios the driver will over ride the mux value.
/OK3568_Linux_fs/kernel/Documentation/ABI/obsolete/
H A Dsysfs-class-dax15 what fault scenarios are supported.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/timer/
H A Dandestech,atcpit100-timer.txt10 multi-function timer and provide the following usage scenarios:
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/zstd/
H A Dzstd_1.5.2.bb3 real-time compression scenarios at zlib-level and better compression ratios. \
/OK3568_Linux_fs/u-boot/doc/uImage.FIT/
H A Dcommand_syntax_extensions.txt10 scenarios, and then introduces new argument syntax.
13 bootm usage scenarios
16 Below is a summary of bootm usage scenarios, focused on booting a PowerPC
/OK3568_Linux_fs/buildroot/package/smcroute/
H A D0001-Avoid-trying-to-delete-inactive-VIFs.patch9 This is for hanlding .conf reload scenarios where an interface has had
/OK3568_Linux_fs/kernel/Documentation/livepatch/
H A Dsystem-state.rst82 3. Supported scenarios
87 scenarios:
/OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/
H A Dl1tf.rst65 Attack scenarios
182 scenarios where guest VMEXIT/VMENTER are rare the performance impact is
185 application scenarios might still suffer from a high VMEXIT rate.
239 scenarios.
262 configuration and the scenarios which run on the system. While for some
611 analyze the risk for their scenarios and make the appropriate
615 kind of scenarios.
/OK3568_Linux_fs/buildroot/dl/qt5location/git/dist/
H A Dchanges-5.9.127 causing a crash in some scenarios
/OK3568_Linux_fs/buildroot/package/gstreamer1/gst1-vaapi/
H A DConfig.in39 more suited to remote transcode scenarios, with faster
/OK3568_Linux_fs/kernel/drivers/cpuidle/
H A DKconfig72 host via halt_poll_ns for some scenarios).
/OK3568_Linux_fs/kernel/drivers/pinctrl/
H A Dpinctrl-pistachio.c77 const int *scenarios; member
504 .scenarios = pistachio_##_name##_scenarios, \
969 if (pf->scenarios) { in pistachio_pinmux_enable()
971 if (pf->scenarios[i] == group) in pistachio_pinmux_enable()
/OK3568_Linux_fs/yocto/poky/meta/recipes-connectivity/kea/files/
H A Dfix-multilib-conflict.patch52 // // options and fields to uniquely identify a client. Those scenarios
/OK3568_Linux_fs/kernel/Documentation/networking/
H A Dtcp-thin.rst11 effective. In time-dependent scenarios (like online games, control
/OK3568_Linux_fs/kernel/fs/erofs/
H A DKconfig11 blocks, inline xattrs/data, etc.) for scenarios which need
/OK3568_Linux_fs/kernel/Documentation/powerpc/
H A Dvcpudispatch_stats.rst11 scenarios, vcpus may be dispatched on a different processor chip (away
/OK3568_Linux_fs/kernel/Documentation/sound/hd-audio/
H A Ddp-mst.rst47 So there are the following scenarios:
/OK3568_Linux_fs/kernel/lib/
H A DKconfig.kfence75 Test suite for KFENCE, testing various error detection scenarios with
/OK3568_Linux_fs/kernel/Documentation/fb/
H A Ddeferred_io.rst34 It may be the case that this is useful in other scenarios as well. Paul Mundt
/OK3568_Linux_fs/kernel/Documentation/x86/
H A Dmds.rst101 As a special quirk to address virtualization scenarios where the host has
124 scenarios where the host has the updated microcode but the
/OK3568_Linux_fs/kernel/Documentation/virt/kvm/
H A Drunning-nested-guests.rst54 There are several scenarios where nested KVM can be useful, to name a
201 scenarios should work even on AMD systems:
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.ubispl137 And you can do fallback scenarios:

12345