| /OK3568_Linux_fs/kernel/arch/arm/probes/kprobes/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | torture.rst | 195 eight-CPU scenario::
242 directory (2020.01.20-15.54.23 in the example above), while per-scenario
243 files reside in a subdirectory named after the scenario (for example,
244 "TREE04"). If a given scenario ran more than once (as in "--configs
246 subsequent runs of that scenario include a sequence number, for example,
253 The most frequently used files in each per-scenario-run directory are:
259 This contains build output for a specific scenario.
262 This contains the console output for a specific scenario.
|
| /OK3568_Linux_fs/kernel/Documentation/crypto/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/memory-devices/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/mmc/ |
| H A 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::
|
| /OK3568_Linux_fs/buildroot/package/postgresql/ |
| H A D | Config.in | 5 # fails to build in a pure static linking scenario, and
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.omap-ulpi-viewport | 22 Ex: scenario:
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/busybox/busybox/ |
| H A D | makefile-libbb-race.patch | 4 This patch avoids this scenario by building libbb as the last directory.
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-connectivity/ppp/ppp/ |
| H A D | CVE-2022-4603.patch | 14 automatically in any scenario that I am aware of.
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-bsp/alsa-state/ |
| H A D | alsa-state.bb | 7 SUMMARY = "Alsa scenario files to enable alsa state restoration"
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A D | ipsec.rst | 45 above scenario. The consequence of doing so is small packet(uncompressed)
|
| /OK3568_Linux_fs/yocto/meta-clang/recipes-devtools/clang/clang/ |
| H A D | 0017-clang-driver-Add-dyld-prefix-when-checking-sysroot-f.patch | 12 the usrmerge scenario.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/mm/ |
| H A D | soft-dirty.rst | 36 there is still a scenario when we can lose soft dirty bits -- a task
|
| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | extensible.rst | 230 Depending on your particular scenario, the arguments and options you use
252 - *Left*: The left scenario in the figure represents a common
267 - *Middle*: The middle scenario in the figure also represents a
292 - *Right*: The right scenario in the figure represents a situation
398 Depending on your particular scenario, the arguments and options you use
408 work on source files. Each scenario assumes the following:
421 - *Left*: The left scenario in the figure represents a common
425 location. The recipe, in this scenario, is in its own layer
439 With this scenario, there is no ``srctree`` argument. Consequently, the
458 - *Middle*: The middle scenario in the figure represents a situation
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/locking/ |
| H A 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
|
| /OK3568_Linux_fs/buildroot/boot/grub2/ |
| H A D | 0047-dl-Only-allow-unloading-modules-that-are-not-depende.patch | 10 This may lead to a use-after-free scenario allowing an attacker to execute
|
| /OK3568_Linux_fs/kernel/Documentation/i2c/busses/ |
| H A D | i2c-sis96x.rst | 58 scenario is found where they're needed.
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/sound/soc/ |
| H A D | codec-to-codec.rst | 41 a speaker and you have a below scenario:
|
| /OK3568_Linux_fs/buildroot/board/globalscale/espressobin/ |
| H A D | readme.txt | 86 A more advanced scenario is setting up switching between the ports using
|
| /OK3568_Linux_fs/kernel/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-02 | 41 # For an example real world scenario issue refer to the attempt to remove
|
| /OK3568_Linux_fs/kernel/Documentation/sound/hd-audio/ |
| H A D | dp-mst.rst | 44 - MST must be dyn_pcm_assign, and it is acomp (for Intel scenario);
|
| /OK3568_Linux_fs/kernel/Documentation/ide/ |
| H A D | ide-tape.rst | 35 following scenario:
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-class-power | 136 This is normally used for the charging scenario where
161 This is normally used for the charging scenario where user-space
279 battery discharging scenario where user-space needs to know the
294 battery discharging scenario where user-space needs to know the
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/ |
| H A 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
|