Home
last modified time | relevance | path

Searched refs:hotplug (Results 1 – 20 of 20) sorted by relevance

/third_party/ltp/testcases/kernel/controllers/cpuset/cpuset_load_balance_test/
Dcpuset_sched_domains_test.sh233 local hotplug=
235 while read isbalance level hotplug
237 base_test $isbalance $hotplug
284 local hotplug=
286 while read g1_cpus g1_isbalance g2_cpus g2_isbalance hotplug
288 base_test $g1_cpus $g1_isbalance $g2_cpus $g2_isbalance $hotplug
Dcpuset_load_balance_test.sh345 local hotplug=
347 while read g1_cpus g1_isbalance g2_cpus g2_isbalance hotplug
349 base_test $g1_cpus $g1_isbalance $g2_cpus $g2_isbalance $hotplug
/third_party/ltp/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/
Dcpuset_hotplug_test.sh240 while read hotplug cpus_expect task_expect
242 base_test "$hotplug" "$cpus_expect" "$task_expect"
256 while read hotplug cpus cpus_expect task_expect
258 base_test "$hotplug" "$cpus" "$cpus_expect" "$task_expect"
/third_party/ltp/testcases/kernel/hotplug/cpu_hotplug/
DREADME5 This package is a collection of test cases for validating CPU hotplug
25 The logic used to operate the hotplug features in Linux are implemented
/third_party/ltp/testcases/kernel/
DMakefile27 hotplug \
/third_party/ltp/testcases/kernel/hotplug/cpu_hotplug/functional/
Dcpuhotplug06.sh17 Desc: Does top work properly when CPU hotplug events occur?
Dcpuhotplug05.sh18 Desc: Does sar behave properly during CPU hotplug events?
/third_party/ltp/testcases/kernel/controllers/cpuset/
DREADME46 cpu hotplug whether they collide with cpuset.
/third_party/libusb/
DBUILD.gn31 "${SRC_PATH}/libusb/hotplug.c",
Dadd_config_h.patch147 +/* UMockdev hotplug code is not racy */
474 +/* UMockdev hotplug code is not racy */
/third_party/ltp/testcases/kernel/device-drivers/base/tbase/
Dtbase.c163 .hotplug = test_class_hotplug,
/third_party/wpa_supplicant/wpa_supplicant-2.9/wpa_supplicant/
DREADME963 can be started when an interface is added (hotplug/udev/etc. scripts).
DChangeLog1371 external mechanism (e.g., hotplug scripts) that start wpa_supplicant
/third_party/wpa_supplicant/wpa_supplicant-2.9_standard/wpa_supplicant/
DREADME963 can be started when an interface is added (hotplug/udev/etc. scripts).
DChangeLog1424 external mechanism (e.g., hotplug scripts) that start wpa_supplicant
/third_party/selinux/libsepol/tests/policies/test-cond/
Drefpolicy-base.conf1737 genfscon proc /sys/kernel/hotplug system_u:object_r:sysctl_hotplug_t:s0
/third_party/libbpf/.github/actions/build-selftests/
Dvmlinux.h17574 struct hotplug_slot *hotplug; member
60315 struct acpi_hotplug_profile hotplug; member
/third_party/libabigail/tests/data/test-diff-filter/
Dtest-PR27569-v1.abi22630 …<var-decl name="hotplug" type-id="b47b0d41" visibility="default" filepath="include/linux/pci.h" li…
36046 …<var-decl name="hotplug" type-id="c6e1b58c" visibility="default" filepath="include/drm/drm_client.…
39919 …<var-decl name="hotplug" type-id="c6e1b58c" visibility="default" filepath="include/drm/drm_client.…
41402 …<var-decl name="hotplug" type-id="7a134fac" visibility="default" filepath="include/drm/drm_dp_mst_…
45784 …<var-decl name="hotplug" type-id="b47b0d41" visibility="default" filepath="include/linux/pci.h" li…
Dtest-PR27569-v0.abi22622 …<var-decl name="hotplug" type-id="b47b0d41" visibility="default" filepath="include/linux/pci.h" li…
36017 …<var-decl name="hotplug" type-id="c6e1b58c" visibility="default" filepath="include/drm/drm_client.…
39890 …<var-decl name="hotplug" type-id="c6e1b58c" visibility="default" filepath="include/drm/drm_client.…
41373 …<var-decl name="hotplug" type-id="7a134fac" visibility="default" filepath="include/drm/drm_dp_mst_…
45755 …<var-decl name="hotplug" type-id="b47b0d41" visibility="default" filepath="include/linux/pci.h" li…
/third_party/gstreamer/gstplugins_bad/
DChangeLog24114 when hotplug display, wayland client will call this listener