| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/pstl/ |
| H A D | glue_execution_defs.h | 20 using __pstl::execution::is_execution_policy; 26 using __pstl::execution::is_execution_policy_v; 30 namespace execution 33 using __pstl::execution::parallel_policy; 34 using __pstl::execution::parallel_unsequenced_policy; 35 using __pstl::execution::sequenced_policy; 38 using __pstl::execution::par; 39 using __pstl::execution::par_unseq; 40 using __pstl::execution::seq; 45 using __pstl::execution::unseq; [all …]
|
| H A D | execution_defs.h | 17 namespace execution 122 struct is_execution_policy<__pstl::execution::sequenced_policy> : std::true_type 126 struct is_execution_policy<__pstl::execution::parallel_policy> : std::true_type 130 struct is_execution_policy<__pstl::execution::parallel_unsequenced_policy> : std::true_type 134 struct is_execution_policy<__pstl::execution::unsequenced_policy> : std::true_type 140 constexpr bool is_execution_policy_v = __pstl::execution::is_execution_policy<_Tp>::value; 151 …typename std::enable_if<__pstl::execution::is_execution_policy<std::__remove_cvref_t<_ExecPolicy>>… 155 …typename std::enable_if<__pstl::execution::is_execution_policy<typename std::decay<_ExecPolicy>::t…
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/pstl/ |
| H A D | glue_execution_defs.h | 20 using __pstl::execution::is_execution_policy; 26 using __pstl::execution::is_execution_policy_v; 30 namespace execution 33 using __pstl::execution::parallel_policy; 34 using __pstl::execution::parallel_unsequenced_policy; 35 using __pstl::execution::sequenced_policy; 38 using __pstl::execution::par; 39 using __pstl::execution::par_unseq; 40 using __pstl::execution::seq; 45 using __pstl::execution::unseq; [all …]
|
| H A D | execution_defs.h | 17 namespace execution 122 struct is_execution_policy<__pstl::execution::sequenced_policy> : std::true_type 126 struct is_execution_policy<__pstl::execution::parallel_policy> : std::true_type 130 struct is_execution_policy<__pstl::execution::parallel_unsequenced_policy> : std::true_type 134 struct is_execution_policy<__pstl::execution::unsequenced_policy> : std::true_type 140 constexpr bool is_execution_policy_v = __pstl::execution::is_execution_policy<_Tp>::value; 151 …typename std::enable_if<__pstl::execution::is_execution_policy<std::__remove_cvref_t<_ExecPolicy>>… 155 …typename std::enable_if<__pstl::execution::is_execution_policy<typename std::decay<_ExecPolicy>::t…
|
| /OK3568_Linux_fs/kernel/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 85 …27] exdebug-0398 ex_trace_point : Method Begin [0xf58394d8:\_SB.PCI0.LPCB.ECOK] execution. 86 [ 0.186630] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905c88:If] execution. 87 [ 0.186820] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905cc0:LEqual] execution. 88 … 0.187010] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905a20:-NamePath-] execution. 89 …[ 0.187214] exdebug-0398 ex_trace_point : Opcode End [0xf5905a20:-NamePath-] execution. 90 [ 0.187407] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution. 91 [ 0.187594] exdebug-0398 ex_trace_point : Opcode End [0xf5905f60:One] execution. 92 [ 0.187789] exdebug-0398 ex_trace_point : Opcode End [0xf5905cc0:LEqual] execution. 93 [ 0.187980] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905cc0:Return] execution. 94 [ 0.188146] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution. [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | workqueue.rst | 13 There are many cases where an asynchronous process execution context 17 When such an asynchronous execution context is needed, a work item 19 independent thread serves as the asynchronous execution context. The 42 worker pool. An MT wq could provide only one execution context per CPU 44 those very limited execution contexts leading to various problems 45 including proneness to deadlocks around the single execution context. 71 In order to ease the asynchronous execution of functions a new 110 (how many execution contexts are active) is an important issue. cmwq 122 workers on the CPU, the worker-pool doesn't start execution of a new 126 without losing execution bandwidth. [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/arm64/ |
| H A D | legacy_instructions.rst | 9 the instruction execution in hardware. 12 (/proc/sys/abi). The following explains the different execution 33 enabling/disabling of hardware support for the execution of these 34 instructions. Using hardware execution generally provides better
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 7 and speculative execution on modern CPUs to read memory, possibly 8 bypassing access controls. Speculative execution side channel exploits 16 Speculative execution side channel methods affect a wide range of modern 18 use branch prediction and speculative execution. 56 influence the speculative execution paths, and then use the side effects 57 of the speculative execution in the CPUs' caches and buffers to infer 58 privileged data touched during the speculative execution. 60 Spectre variant 1 attacks take advantage of speculative execution of 62 execution of indirect branches to leak privileged memory. 70 of speculative execution that bypasses conditional branch instructions [all …]
|
| H A D | special-register-buffer-data-sampling.rst | 68 During execution of the RDRAND, RDSEED, or EGETKEY instructions, off-core 91 enclaves (including execution of RDRAND or RDSEED inside an enclave, as well 92 as EGETKEY execution). 146 This new microcode serializes processor access during execution of RDRAND,
|
| /OK3568_Linux_fs/u-boot/arch/arm/mach-sunxi/ |
| H A D | rmr_switch.S | 9 @ into a different execution state (AArch32 or AArch64). 10 @ The address at which execution starts after the reset is held in the 14 @ This code below switches to AArch64 and starts execution at the specified
|
| /OK3568_Linux_fs/yocto/poky/meta/classes/ |
| H A D | scons.bbclass | 22 die "scons build execution failed." 27 die "scons install execution failed."
|
| H A D | setuptools3_legacy.bbclass | 37 bbfatal_log "'${PYTHON_PN} setup.py build ${SETUPTOOLS_BUILD_ARGS}' execution failed." 49 bbfatal_log "'${PYTHON_PN} setup.py install ${SETUPTOOLS_INSTALL_ARGS}' execution failed."
|
| /OK3568_Linux_fs/buildroot/package/uftrace/ |
| H A D | Config.in | 17 The uftrace tool is to trace and analyze execution of a 22 analysis of the program execution and performance.
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.mpc85xx | 40 TLB Entries during u-boot execution 43 Note: Sequence number is in order of execution 65 4) TLB entry for CCSRBAR during AS1 execution 121 4) TLB entry for CCSRBAR during AS1 execution
|
| /OK3568_Linux_fs/kernel/Documentation/ia64/ |
| H A D | fsys.rst | 13 execution to the ia64 linux kernel. We call this mode the 14 "fsys-mode". To recap, the normal states of execution are: 28 interruption-handlers start execution in. The user-level 34 - execution is at privilege level 0 (most-privileged) 41 - execution is interruptible and preemptible (an fsys-mode handler 147 execution may be pre-empted and resumed on another CPU at any given 169 fast system call execution (while fully preserving system call 221 such that execution resumes in the gate page at 240 state such that execution resumes in the gate page at
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-python/classes/ |
| H A D | distutils3.bbclass | 32 bbfatal_log "'${PYTHON_PN} setup.py build ${DISTUTILS_BUILD_ARGS}' execution failed." 44 bbfatal_log "'${PYTHON_PN} setup.py install ${DISTUTILS_INSTALL_ARGS}' execution failed."
|
| /OK3568_Linux_fs/external/xserver/hw/xfree86/int10/ |
| H A D | INT10.HOWTO | 25 int10 execution is disabled by an option in the device section NULL 32 To allocate memory in the real mode execution environment 84 1. It must trap calls to intXX instructions and pass execution to an 87 emulator for continuing execution. When the external function is 121 virtual address space just prior to execution may be found in 205 just above the BIOS variable area. Before entering real mode execution 276 set up the non-static real mode execution environment. On return from 280 It should start execution by calling 285 continue execution until a 'hlt' instruction is encountered. To copy
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/ |
| H A D | mali-coresight-source.txt | 99 - "ceu-execution": Cannot share the channel with other types 127 sg2 = "ceu-execution"; 150 sg1 = "ceu-execution";
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/nfc/ |
| H A D | nfc-hci.rst | 28 HCI uses 2 execution contexts: 198 The execution contexts are the following: 211 Serializes execution of HCI commands. 213 Completes execution in case of response timeout. 236 Internally, execution is asynchronous. So all this API does is to enqueue the 253 waiting command execution. Response processing involves invoking the completion 282 Errors that occur synchronously with the execution of an NFC Core request are 283 simply returned as the execution result of the request. These are easy.
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 96 alternate execution of each batch to ensure forward progress of 99 concurrent execution in order for them to proceed, e.g. they 101 is scheduled for execution for the timeslice duration, before
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/ |
| H A D | unshare.rst | 29 as multiple execution contexts within a process. These kernels provide 126 unshare - disassociate parts of the process execution context 134 unshare() allows a process to disassociate parts of its execution 136 of execution context, such as the namespace, is shared by default 143 shared execution context without creating a new process. 315 4) Concurrent execution: Use shared memory segments and futex on 316 an address in the shm segment to synchronize execution of
|
| /OK3568_Linux_fs/kernel/fs/fscache/ |
| H A D | Kconfig | 23 execution as there are a quite a few stats gathered, and on a 40 execution as there are a number of points at which data is gathered,
|
| /OK3568_Linux_fs/kernel/Documentation/staging/ |
| H A D | speculation.rst | 11 employ speculative execution techniques such as branch prediction, performing 14 Typically speculative execution cannot be observed from architectural state,
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | init.rst | 7 (listed roughly in order of execution) to load the init binary. 35 execution. To find out more, add code ``to init/main.c`` to display
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/patch/patch/ |
| H A D | 0001-Don-t-leak-temporary-file-on-failed-ed-style-patch.patch | 18 Fixes: 123eaff0d5d1 ("Fix arbitrary command execution in ed-style patches (CVE-2018-1000156)") 59 can lead to arbitrary command execution. */
|