| /linux-4.4.14/arch/arm/probes/kprobes/ |
| D | test-core.c | 1074 static unsigned long test_context_cpsr(int scenario) in test_context_cpsr() argument
1081 cpsr = (scenario & 0xf) << 28; /* N,Z,C,V flags */ in test_context_cpsr()
1082 cpsr |= (scenario & 0xf) << 16; /* GE flags */ in test_context_cpsr()
1083 cpsr |= (scenario & 0x1) << 27; /* Toggle Q flag */ in test_context_cpsr()
1090 if (scenario == 15) in test_context_cpsr()
1100 if (scenario == 15) in test_context_cpsr()
1105 unsigned x = (scenario >> 4); in test_context_cpsr()
1113 if ((scenario & 0xf) == 0xf) in test_context_cpsr()
1128 switch (scenario) { in test_context_cpsr()
1152 int scenario = test_case_run_count>>1; in setup_test_context() local
[all …]
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-async-req.txt | 59 request. The host driver may optimize for this scenario to minimize
64 Pseudocode to handle is_first_req scenario with minimal prepare overhead:
|
| /linux-4.4.14/Documentation/bus-devices/ |
| D | ti-gpmc.txt | 31 in time or in cycles, provision to handle this scenario has been
34 in timing structure, in this scenario, try to correlate peripheral
|
| /linux-4.4.14/Documentation/networking/ |
| D | ipsec.txt | 37 above scenario. The consequence of doing so is small packet(uncompressed)
|
| D | rds.txt | 54 a active-active HA scenario), but only as long as the address
|
| D | bonding.txt | 1676 a likely scenario, one could avoid this possibility by simply configuring
|
| /linux-4.4.14/Documentation/vm/ |
| D | soft-dirty.txt | 32 there is still a scenario when we can lose soft dirty bits -- a task
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-sis96x | 53 scenario is found where they're needed.
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 41 # For an example real world scenario issue refer to the attempt to remove
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide-tape.txt | 33 following scenario:
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcuref.txt | 45 in this scenario as follows:
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | era.txt | 64 The scenario of invalidating a cache when rolling back a vendor
|
| D | log-writes.txt | 25 simulate the worst case scenario with regard to power failures. Consider the
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockdep-design.txt | 127 could lead to a lock inversion deadlock - even if that lock scenario did
196 every possible hardirq and softirq nesting scenario (which is impossible
216 This problem is solved by checking any given 'locking scenario' (unique
|
| D | lglock.txt | 63 On -RT this deadlock scenario is resolved by the arch_spin_locks in the
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.txt | 97 reinitialization of the device driver. In a worst-case scenario,
105 kernel/device driver should assume the worst-case scenario, that the
316 succeed. Both have been only lightly tested in this scenario.
|
| D | cxlflash.txt | 269 and playback required by a user in such a scenario. When a process
|
| /linux-4.4.14/drivers/staging/fsl-mc/ |
| D | README.txt | 81 in the DPAA2 hardware. A simple scenario is described illustrating
263 scenario and the objects bound to each driver. A brief description
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-block-zram | 46 scenario it may account a) the number of pages freed because
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 123 in a simple scenario.
|
| D | cgroups.txt | 107 As an example of a scenario (originally proposed by vatsa@in.ibm.com)
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-block-zram | 81 scenario it may account a) the number of pages freed because
|
| /linux-4.4.14/arch/arc/kernel/ |
| D | entry-compact.S | 171 ; This is to avoid a potential L1-L2-L1 scenario
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | of_unittest.txt | 129 According to the scenario above, the live tree is already present so it isn't
|
| /linux-4.4.14/Documentation/ |
| D | pi-futex.txt | 66 [this is a quite common scenario for most non-trivial RT applications],
|
| D | initrd.txt | 288 A second scenario is for installations where Linux runs on systems with
296 A third scenario is more convenient recovery disks, because information
|
| D | this_cpu_ops.txt | 304 the following scenario that occurs because two per cpu variables
|
| D | DMA-API-HOWTO.txt | 219 Another common scenario is a 64-bit capable device. The approach here
|
| D | pinctrl.txt | 749 "GPIO mode pitfalls" for more details on this scenario.
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | completion.txt | 107 A typical usage scenario is:
|
| /linux-4.4.14/Documentation/dvb/ |
| D | README.dvb-usb | 161 long-term test scenario.
|
| /linux-4.4.14/Documentation/power/ |
| D | suspend-and-cpuhotplug.txt | 225 This is the usual scenario encountered during a resume after a suspend.
|
| D | freezing-of-tasks.txt | 220 However, the [un]lock_system_sleep() APIs are safe to use in this scenario,
|
| /linux-4.4.14/Documentation/virtual/kvm/arm/ |
| D | vgic-mapped-irqs.txt | 145 However, this means that a scenario like the following is entirely
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | btt.txt | 16 and new data. Applications may not be prepared to handle such a scenario.
|
| /linux-4.4.14/Documentation/x86/ |
| D | intel_mpx.txt | 132 even if we clean them up aggressively. In the worst-case scenario, the
|
| /linux-4.4.14/Documentation/block/ |
| D | cfq-iosched.txt | 210 request queue at a time. In such scenario, it is not possible to measure time
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 5.Posting | 102 scenario when the "git bisect" tool is used to find regressions; if the
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 565 i. Added FW tranistion state for Hotplug scenario
|
| /linux-4.4.14/mm/ |
| D | Kconfig | 239 scenario aforementioned and helps improving memory defragmentation.
|
| /linux-4.4.14/Documentation/trace/ |
| D | ring-buffer-design.txt | 301 Possible scenario:
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 999 deadlock scenario would be to trigger: how many
1003 theoretically (no matter how unlikely the race scenario
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 312 workload/scenario before using this option. Currently, local
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1026 instructions. This sensitivity can result in a CPU hang scenario.
|