Home
last modified time | relevance | path

Searched refs:scenario (Results 1 – 25 of 86) sorted by relevance

1234

/linux/arch/arm/probes/kprobes/
H A Dtest-core.c1021 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/Documentation/translations/it_IT/RCU/
H A Dtorture.rst188 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/Documentation/crypto/
H A Ddevel-algos.rst183 ^ | | 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/Documentation/driver-api/memory-devices/
H A Dti-gpmc.rst35 in time or in cycles, provision to handle this scenario has been
38 in timing structure, in this scenario, try to correlate peripheral
/linux/Documentation/driver-api/mmc/
H A Dmmc-async-req.rst70 request. The host driver may optimize for this scenario to minimize
75 Pseudocode to handle is_first_req scenario with minimal prepare overhead::
/linux/arch/arm64/boot/dts/rockchip/
H A Drk3588-jaguar-pre-ict-tester.dtso106 * the worst case scenario and the pass scenario expect
/linux/Documentation/networking/
H A Dipsec.rst45 above scenario. The consequence of doing so is small packet(uncompressed)
/linux/Documentation/admin-guide/mm/
H A Dsoft-dirty.rst34 there is still a scenario when we can lose soft dirty bits -- a task
/linux/Documentation/i2c/busses/
H A Di2c-sis96x.rst58 scenario is found where they're needed.
/linux/Documentation/locking/
H A Dlockdep-design.rst129 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/tools/perf/Documentation/
H A Dintel-acr.txt15 For example, if the user desires to measure a scenario when IPC > 2,
/linux/Documentation/driver-api/
H A Dntb.rst55 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/Documentation/sound/hd-audio/
H A Ddp-mst.rst44 - MST must be dyn_pcm_assign, and it is acomp (for Intel scenario);
/linux/Documentation/kbuild/
H A DKconfig.recursion-issue-0241 # For an example real world scenario issue refer to the attempt to remove
/linux/Documentation/admin-guide/device-mapper/
H A Dera.rst72 The scenario of invalidating a cache when rolling back a vendor
/linux/Documentation/userspace-api/media/v4l/
H A Dpixfmt-v4l2-mplane.rst31 codec to support the worst-case compression scenario.
/linux/Documentation/admin-guide/hw-vuln/
H A Dl1tf.rst111 deployment scenario. The mitigations, their protection scope and impact
200 workload scenario and the resulting number of VMEXITs.
238 scenario. Disabling SMT might be a viable alternative for particular
280 the impact depends on the hosting scenario and the type of workloads.
522 the scenario still trigger soft interrupts and schedule kernel threads
/linux/Documentation/driver-api/nvdimm/
H A Dfirmware-activate.rst37 activation. In that scenario the potential for firmware activation to
/linux/Documentation/mm/
H A Dmmu_notifier.rst31 Consider the following scenario (device use a feature similar to ATS/PASID):
/linux/Documentation/usb/
H A Draw-gadget.rst51 A typical usage scenario of Raw Gadget:
/linux/tools/testing/selftests/rcutorture/bin/
H A Dkvm-test-1-run.sh176 echo To run this scenario on bare metal: >> $resdir/bare-metal
/linux/Documentation/RCU/
H A Drcuref.rst52 in this scenario as follows:
/linux/Documentation/bpf/
H A Dmap_cpumap.rst22 multiple CPUs. For example, a scenario where the initial CPU (that sees/receives
/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
H A Doverview.rst77 A simple scenario is described illustrating the objects involved
285 scenario and the objects bound to each driver. A brief description
/linux/Documentation/security/
H A Dipe.rst324 And, like the first option, falls short with the execution scenario,
335 scenario and explicitly state it::
396 scenario all current trust properties will also evaluate to false.

1234