Home
last modified time | relevance | path

Searched refs:CPU (Results 1 – 25 of 51) sorted by relevance

123

/frameworks/av/include/cpustats/
DREADME.txt1 This is a static library of CPU usage statistics, originally written
5 * should be related to CPU usage statistics
/frameworks/compile/slang/
Dslang.cpp178 void Slang::createTarget(const std::string &Triple, const std::string &CPU, in createTarget() argument
185 if (!CPU.empty()) in createTarget()
186 mTargetOpts->CPU = CPU; in createTarget()
270 void Slang::init(const std::string &Triple, const std::string &CPU, in init() argument
283 createTarget(Triple, CPU, Features); in init()
Dslang.h97 void createTarget(std::string const &Triple, std::string const &CPU,
174 void init(const std::string &Triple, const std::string &CPU,
Dslang_backend.cpp157 if (mTargetOpts.CPU.size() || mTargetOpts.Features.size()) { in CreateCodeGenPasses()
170 TargetInfo->createTargetMachine(Triple, mTargetOpts.CPU, FeaturesStr, in CreateCodeGenPasses()
/frameworks/base/docs/html/tools/help/
Dsystrace.jd9 tool combines data from the Android kernel such as the CPU scheduler, disk activity and
84 <td>Trace CPU frequency changes. Only changes to the CPU frequency are logged, so the initial
85 frequency of the CPU when tracing starts is not shown.</td>
91 <td>Trace CPU idle events.</td>
97 <td>Trace CPU load. This value is a percentage determined by the interactive CPU frequency
104 <td>Prevent tracing of the CPU scheduler. This option allows for longer trace times by reducing
/frameworks/base/docs/html/tools/debugging/
Ddebugging-devtools.jd60 <dt><strong>Show CPU usage</strong></dt>
62 <dd>Displays CPU meters at the top of the screen, showing how much the CPU is being used. The
63 top red bar shows overall CPU usage, and the green bar underneath it shows the CPU time spent
Dindex.jd109 that provide useful information such as CPU usage and frame rate. You can also transfer the
127 <dd>The device can display useful information such as CPU usage or highlights
/frameworks/base/docs/html/training/scheduling/
Dindex.jd32 ultimately turn off the CPU. This prevents the device's battery from quickly getting
39 <li>Other applications may not need the screen to remain on, but they may require the CPU
55 Learn how to keep the screen or CPU awake as needed, while minimizing the impact
Dwakelock.jd14 <li><a href="#cpu">Keep the CPU On</a></li>
30 However, there are times when an application needs to wake up the screen or the CPU
55 Keep the CPU On</a>), it doesn't require special permission, and the platform correctly
85 <h2 id="cpu">Keep the CPU On</h2>
110 <p>If you need to keep the CPU running in order to complete some work before the device goes
123 that needs to grab a wake lock to keep the CPU running to do work while the screen is off.
146 claim to the CPU. It's important to release a wake lock as soon as your app is finished
210 // Do the work that requires your app to keep the CPU running.
/frameworks/av/media/libstagefright/codecs/on2/h264dec/source/arm11_asm/
Dwin_asm.bat2 set ASMFLAGS= -checkreglist -CPU ARM1136 -PreDefine "H264DEC_WINASM SETL {TRUE}"
/frameworks/native/cmds/flatland/
DREADME.txt16 that consume much CPU cycles, memory bandwidth, or might otherwise interfere
21 frequency when running flatland. At a minimum this includes the CPU, GPU, and
/frameworks/base/docs/html/training/articles/
Dsmp.jd16 <li style="margin:0"><a href="#cpu_cache">CPU cache behavior</a></li>
79 discussion on the subject. The focus is on the ARM CPU architecture.</p>
89 which two or more identical CPU cores share access to main memory. Until
122 model might guarantee that every CPU core sees those writes happen in that
137 memory, on a sequentially-consistent CPU architecture you know that the code
139 CPU is actually reordering instructions and delaying reads and writes, but there
140 is no way for code running on the device to tell that the CPU is doing anything
147 the order in which the CPU will execute them. We don’t want to consider
166 capital letters (A, B, C) and CPU registers start with “reg”. All memory is
173 <p>Thread 1 and thread 2 are assumed to execute on different CPU cores. You
[all …]
/frameworks/base/docs/html/tools/
Dindex.jd52 <li>Show CPU usage on screen.</li>
97 <li>Built-in memory analysis, performance/CPU profiling, OpenGL ES tracing.</li>
/frameworks/base/docs/html/training/multiple-threads/
Drun-code.jd131 immediately. However, it only stops threads that are waiting, and will not interrupt CPU or
144 // Decodes a byte array into a Bitmap (CPU-intensive)
Dindex.jd43 split it into smaller operations running on multiple threads. On a device that has a CPU with
Dcreate-threadpool.jd64 single control point for restricted CPU or network resources. If you have different
/frameworks/base/docs/html/google/play/publishing/
Dmultiple-apks.jd40 <li><a href="#CpuArchOptions">Supporting multiple CPU architectures</a></li>
86 <li>Support different CPU architectures with each APK (such as for ARM, x86, and MIPS, when your
289 <li><strong>CPU architecture (ABI)</strong>
375 distinguish each APK, but so is the CPU architecture. Because an APK with ARMv5TE libraries is
376 compatible with devices that have an ARMv7 CPU, the APKs overlap on this characteristic.
378 This ensures that a device with an ARMv7 CPU that receives a system update to API level 8
381 fully optimized for that device's CPU, you should provide an
383 the app performance on each CPU.
411 <p class="note"><strong>Note:</strong> If you're creating separate APKs for different CPU
673 <h3 id="CpuArchOptions">Supporting multiple CPU architectures</h3>
[all …]
/frameworks/base/docs/html/training/basics/activity-lifecycle/
Dpausing.jd74 <li>Stop animations or other ongoing actions that could consume CPU.</li>
103 However, you should avoid performing CPU-intensive work during {@link
/frameworks/base/docs/html/tools/sdk/ndk/
Dindex.jd272 <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't
407 <li>Fixed extra apostrophe in <code>CPU-ARCH-ABIS.html</code>. For more information, see
1034 <li>Fixed x86 CPU detection for the {@code ANDROID_CPU_X86_FEATURE_MOVBE} feature.
1256 <li>Backported fix for {@code cc1} compile process consuming 100% CPU.
1633 MIPS support, see {@code docs/CPU-MIPS.html} in the NDK package.
1658 is compiled for the device's CPU architecture.</p>
1831 x86 CPU features ({@code SSSE3}, {@code MOVBE} and {@code POPCNT}). See
1832 {@code docs/CPU-FEATURES.html} for more details.</li>
2211 see <code>docs/CPU-X86.html</code> in the NDK package.
2441 …of the CPU type (some devices previously reported ARMv7 CPU when the device really was an ARMv6). …
[all …]
/frameworks/base/docs/html/about/versions/
Dandroid-2.3-highlights.jd120 the device awake for too long or that are consuming CPU while running in the
217 events faster and more efficiently, minimizing CPU utilization during event
220 or other CPU-intensive operations. </li>
/frameworks/base/docs/html/google/play/
Dfilters.jd394 <td valign="top" style="white-space:nowrap;">CPU Architecture (ABI)</td>
396 libraries that target a specific CPU architecture (ARM EABI v7 or x86, for example) are
434 <li>CPU Architecture (ABI)
436 NDK</a> that target a specific CPU architecture (ARM EABI v7 or x86, for example).</p>
/frameworks/base/docs/html/tools/devices/
Demulator.jd123 <li>An ARMv5 CPU and the corresponding memory-management unit (MMU)</li>
314 this type of acceleration, you should first determine if your development system’s CPU supports one
322 <p>The specifications from the manufacturer of your CPU should indicate if it supports
323 virtualization extensions. If your CPU does not support one of these virtualization technologies,
330 <p>Once you have determined that your CPU supports virtualization extensions, make sure you can work
368 <strong>CPU/ABI</strong> field. You may need to select a specific <strong>Target</strong> value, or
369 select a <strong>Target</strong> value and then select a specific <strong>CPU/ABI</strong>
378 Accelerated Execution Manager (Intel HAXM). The software requires an Intel CPU with
439 Execution Manager (Intel HAXM) kernel extension to allow the Android emulator to make use of CPU
/frameworks/base/docs/html/guide/topics/connectivity/nfc/
Dhce.jd68 the host CPU on which Android applications are running directly, instead of routing the NFC
428 either be the host CPU (where Android apps are running), or a connected secure
450 4.4, the default route is required to be set to the host CPU. This
505 because the host CPU is not involved in the transaction and therefore cannot
/frameworks/base/docs/html/training/graphics/opengl/
Ddraw.jd120 in terms of CPU cycles and processing time, so you should avoid doing this more than once. If you do
/frameworks/native/opengl/specs/
DEGL_ANDROID_blob_cache.txt38 programming for a long time. It can consume seconds of CPU cycles during

123