Searched refs:scenario (Results 1 - 6 of 6) sorted by relevance
/linux-master/tools/testing/selftests/rcutorture/bin/ |
H A D | kvm-test-1-run-batch.sh | 26 echo Bad scenario name: \"$i\" 1>&2 48 # Start up jitter, start each scenario, wait, end jitter. 65 print "echo " scenario ": Bogus number of CPUs (old qemu-cmd?), so no taskset command."; 69 print "echo " scenario ": Bogus CPU-affinity information, so no taskset command."; 71 print "echo " scenario ": Could not dump state, so no taskset command."; 78 affinity_export="`awk -f $T/cpubatches.awk -v cpu_count="$cpu_count" -v scenario=$i < /dev/null`"
|
H A D | kvm-test-1-run.sh | 174 echo To run this scenario on bare metal: >> $resdir/bare-metal
|
/linux-master/arch/arm/probes/kprobes/ |
H A D | test-core.c | 1021 static unsigned long test_context_cpsr(int scenario) argument 1028 cpsr = (scenario & 0xf) << 28; /* N,Z,C,V flags */ 1029 cpsr |= (scenario & 0xf) << 16; /* GE flags */ 1030 cpsr |= (scenario & 0x1) << 27; /* Toggle Q flag */ 1037 if (scenario == 15) 1047 if (scenario == 15) 1052 unsigned x = (scenario >> 4); 1060 if ((scenario & 0xf) == 0xf) 1075 switch (scenario) { 1099 int scenario local [all...] |
/linux-master/arch/arc/kernel/ |
H A D | entry-compact.S | 29 * -In a rare scenario, Process gets a Priv-V exception and gets scheduled 33 * Instr Error could also cause similar scenario, so same there as well. 154 ; This is to avoid a potential L1-L2-L1 scenario
|
/linux-master/drivers/net/wireless/ath/wcn36xx/ |
H A D | hal.h | 5038 u32 scenario; member in struct:wcn36xx_hal_print_reg_info_ind
|
H A D | smd.c | 2869 "reginfo indication, scenario: 0x%x reason: 0x%x\n", 2870 rsp->scenario, rsp->reason);
|
Completed in 229 milliseconds