| /Linux-v5.4/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-v5.4/Documentation/crypto/ |
| D | devel-algos.rst | 198 ^ | | at all in this scenario.
204 ^ | | at all in this scenario.
221 .setkey() -> .init() -> .update() -> .export() at all in this scenario.
230 ^ | | at all in this scenario.
|
| D | architecture.rst | 114 selection. To accommodate this scenario, the kernel crypto API allows
248 complex scenario where all other scenarios form a logical subset.
|
| /Linux-v5.4/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-v5.4/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-v5.4/Documentation/networking/ |
| D | ipsec.txt | 37 above scenario. The consequence of doing so is small packet(uncompressed)
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-power | 55 battery discharging scenario where user-space needs to know the
69 battery discharging scenario where user-space needs to know the
252 battery charging scenario where user-space needs to know the
266 battery charging scenario where user-space needs to know the
447 charging scenario where user-space needs to know the supply
462 charging scenario where user-space needs to know the supply
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 36 there is still a scenario when we can lose soft dirty bits -- a task
|
| /Linux-v5.4/Documentation/sound/soc/ |
| D | codec-to-codec.rst | 41 a speaker and you have a below scenario:
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-sis96x.rst | 58 scenario is found where they're needed.
|
| /Linux-v5.4/Documentation/ide/ |
| D | ide-tape.rst | 35 following scenario:
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 41 # For an example real world scenario issue refer to the attempt to remove
|
| /Linux-v5.4/Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 44 - MST must be dyn_pcm_assign, and it is acomp (for Intel scenario);
|
| /Linux-v5.4/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-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 126 deadlock may happen. For example, in the scenario that after this lock
186 could lead to a lock inversion deadlock - even if that lock scenario did
302 every possible hardirq and softirq nesting scenario (which is impossible
324 This problem is solved by checking any given 'locking scenario' (unique
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | era.rst | 72 The scenario of invalidating a cache when rolling back a vendor
|
| D | log-writes.rst | 26 simulate the worst case scenario with regard to power failures. Consider the
|
| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 111 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-v5.4/Documentation/vm/ |
| D | mmu_notifier.rst | 33 Consider the following scenario (device use a feature similar to ATS/PASID):
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.rst | 97 reinitialization of the device driver. In a worst-case scenario,
105 kernel/device driver should assume the worst-case scenario, that the
320 succeed. Both have been only lightly tested in this scenario.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | pixfmt-v4l2-mplane.rst | 37 codec to support the worst-case compression scenario.
|
| /Linux-v5.4/Documentation/RCU/ |
| D | rcuref.txt | 47 in this scenario as follows:
|
| /Linux-v5.4/Documentation/networking/device_drivers/freescale/dpaa2/ |
| D | overview.rst | 77 A simple scenario is described illustrating the objects involved
284 scenario and the objects bound to each driver. A brief description
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 127 in a simple scenario.
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 176 scenario 3, Message and Flag, of [lwn-mb]_ and the kernel documentation
209 (scenario 10 of [lwn-mb]_). As the Dekker pattern requires two variables,
|
