| /linux-6.12.1/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run-batch.sh | 7 # Usage: kvm-test-1-run-batch.sh SCENARIO [ SCENARIO ... ]
9 # Each SCENARIO is the name of a directory in the current directory
26 echo Bad scenario name: \"$i\" 1>&2
31 echo Scenario name not a directory: \"$i\" 1>&2
36 echo Scenario lacks a command file: \"$i/qemu-cmd\" 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`"
|
| D | config2csv.sh | 5 # parameters. Run this in the directory containing the scenario files.
11 # specified on the command line. It will examine each scenario's file
|
| D | kvm-test-1-run-qemu.sh | 10 # This is assumed to be of the form prefix/ds/scenario, where
11 # "ds" is the top-level date-stamped directory and "scenario"
12 # is the scenario name. Any required adjustments to this file
|
| /linux-6.12.1/Documentation/RCU/ |
| D | torture.rst | 195 eight-CPU scenario::
211 Note that --gdb limits you to one scenario per kvm.sh run and requires
253 directory (2020.01.20-15.54.23 in the example above), while per-scenario
254 files reside in a subdirectory named after the scenario (for example,
255 "TREE04"). If a given scenario ran more than once (as in "--configs
257 subsequent runs of that scenario include a sequence number, for example,
264 The most frequently used files in each per-scenario-run directory are:
270 This contains build output for a specific scenario.
273 This contains the console output for a specific scenario.
357 This will build each default scenario's kernel on the local system, then
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/ |
| D | common-properties.txt | 33 Scenario 1 : CPU in LE mode & device in LE mode.
41 Scenario 2 : CPU in LE mode & device in BE mode.
49 Scenario 3 : CPU in BE mode & device in BE mode.
57 Scenario 4 : CPU in BE mode & device in LE mode.
|
| /linux-6.12.1/Documentation/translations/it_IT/RCU/ |
| D | torture.rst | 188 scenario su otto processori::
192 O ancora 28 istanze per ogni scenario su otto processori::
204 kcsan. Da notare che --gdb vi limiterà all'uso di un solo scenario per
247 specifici per scenario si trovano in sotto cartelle che prendono il nome dello
248 scenario stesso (per esempio, "TREE04"). Se un dato scenario viene eseguito più
258 I file solitamente più usati nelle cartelle di scenario sono:
264 Questo file contiene il risultato di compilazione per uno specifico scenario
267 Questo file contiene il risultato d'esecuzione per uno specifico scenario.
351 Questo compilerà lo scenario di base sul sistema locale, poi lo distribuirà agli
352 altri cinque sistemi elencati fra i parametri, ed eseguirà ogni scenario per
|
| /linux-6.12.1/include/uapi/sound/ |
| D | snd_ar_tokens.h | 12 /** Scenario ID Audio Playback */
14 /* Scenario ID Audio Record */
16 /* Scenario ID Voice call. */
70 * %AR_TKN_U32_SUB_GRAPH_SCENARIO_ID: Scenario ID for subgraph
|
| /linux-6.12.1/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | sf.h | 19 /* Smart Fifo possible scenario */
71 * @long_delay_timeouts: aging and idle timer values for each scenario
73 * @full_on_timeouts: timer values for each scenario in full on state.
|
| /linux-6.12.1/Documentation/crypto/ |
| D | devel-algos.rst | 183 ^ | | at all in this scenario.
189 ^ | | at all in this scenario.
206 .setkey() -> .init() -> .update() -> .export() at all in this scenario.
215 ^ | | at all in this scenario.
|
| /linux-6.12.1/arch/arm/probes/kprobes/ |
| D | test-core.c | 1021 static unsigned long test_context_cpsr(int scenario) in test_context_cpsr() argument
1028 cpsr = (scenario & 0xf) << 28; /* N,Z,C,V flags */ in test_context_cpsr()
1029 cpsr |= (scenario & 0xf) << 16; /* GE flags */ in test_context_cpsr()
1030 cpsr |= (scenario & 0x1) << 27; /* Toggle Q flag */ in test_context_cpsr()
1037 if (scenario == 15) in test_context_cpsr()
1047 if (scenario == 15) in test_context_cpsr()
1052 unsigned x = (scenario >> 4); in test_context_cpsr()
1060 if ((scenario & 0xf) == 0xf) in test_context_cpsr()
1075 switch (scenario) { in test_context_cpsr()
1099 int scenario = test_case_run_count>>1; in setup_test_context() local
[all …]
|
| /linux-6.12.1/tools/testing/selftests/bpf/prog_tests/ |
| D | cgroup_tcp_skb.c | 257 /* Scenario 1 */ in test_cgroup_tcp_skb()
278 /* Scenario 2 */ in test_cgroup_tcp_skb()
297 /* Scenario 3 */ in test_cgroup_tcp_skb()
316 /* Scenario 4 */ in test_cgroup_tcp_skb()
|
| /linux-6.12.1/kernel/sched/ |
| D | membarrier.c | 93 * Using the scenario from (A), we can show that (a) needs to be paired
94 * with (e). Using the scenario from (B), we can show that (c) needs to
114 * Using scenario (B), we can show that (c) needs to be paired with (d).
131 * Using the scenario from (A), we can show that (a) needs to be paired
132 * with (g). Using the scenario from (B), we can show that (c) needs to
178 * become visible to membarrier()'s caller -- see scenario B in in ipi_sync_core()
|
| /linux-6.12.1/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6358.txt | 34 Scenario 1 : BCM6358
63 Scenario 2 : BCM6368
|
| /linux-6.12.1/Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 35 in time or in cycles, provision to handle this scenario has been
38 in timing structure, in this scenario, try to correlate peripheral
|
| /linux-6.12.1/Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 70 request. The host driver may optimize for this scenario to minimize
75 Pseudocode to handle is_first_req scenario with minimal prepare overhead::
|
| /linux-6.12.1/drivers/gpu/drm/i915/display/ |
| D | intel_drrs.c | 20 * dynamically, based on the usage scenario. This feature is applicable
28 * (may appear as a blink on screen) and is used in dock-undock scenario.
48 * the scenario of video playback wherein RR is set based on the rate
|
| /linux-6.12.1/Documentation/locking/ |
| D | lockdep-design.rst | 129 deadlock may happen. For example, in the scenario that after this lock
189 could lead to a lock inversion deadlock - even if that lock scenario did
305 every possible hardirq and softirq nesting scenario (which is impossible
327 This problem is solved by checking any given 'locking scenario' (unique
634 waiting scenario and nobody can get progress, therefore a deadlock.
638 Lemma 2 is equivalent to: If there is a deadlock scenario, then there must be a
642 waiting scenario, means there are N CPU/tasks, where CPU/task P1 is waiting for
|
| /linux-6.12.1/arch/x86/realmode/rm/ |
| D | trampoline_common.S | 9 * extends to 8-bytes. Reserve enough space for either scenario.
|
| /linux-6.12.1/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 23 Scenario 1 : a register set in big-endian mode.
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | ntb.rst | 55 So typical scenario of the first type memory window initialization looks:
73 Typical scenario of the second type interface initialization would be:
93 In accordance with this scenario, the NTB Memory Window API can be used as
|
| /linux-6.12.1/drivers/gpu/drm/amd/include/ivsrcid/vmc/ |
| D | irqsrcs_vmc_1_0.h | 34 …D__FAULT 0 /* UTC L2 has encountered a fault or retry scenario */
|
| /linux-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | richtek,rt4831-regulator.yaml | 22 voltage drop from the heavy loading scenario. But it also make the power
|
| /linux-6.12.1/drivers/infiniband/hw/mlx5/ |
| D | fs.h | 38 * itself is kept to deal with the above scenario. The remaining in mlx5_ib_fs_cleanup()
|
| /linux-6.12.1/Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 8 known scenario of poisoning CPU functional units - the Branch Target
102 Mitigation addressing the cloud provider scenario - the Guest->Host
|
| /linux-6.12.1/drivers/gpu/drm/i915/pxp/ |
| D | intel_pxp_pm.c | 46 * re-bound after we come out, so in that scenario we can defer the in _pxp_resume()
|