| /external/OpenCSD/decoder/tests/snapshots/juno_r1_1/ds-5-dumps/ |
| D | Trace_Report_0x11_cpu_1_2015Sep17_104748.txt | 4 EL1N:0xFFFFFFC000781E8C ? Cannot access target memory
7 EL1N:0xFFFFFFC000781E8C ? Cannot access target memory
8 EL1N:0xFFFFFFC000781E8C ? Cannot access target memory
9 EL1N:0xFFFFFFC0000F3698 ? Cannot access target memory
11 EL1N:0xFFFFFFC0000F408C ? Cannot access target memory
59 EL1N:0xFFFFFFC0001124D8 ? Cannot access target memory
62 EL1N:? ? Cannot access target memory
63 EL1N:? ? Cannot access target memory
64 EL1N:? ? Cannot access target memory
65 EL1N:? ? Cannot access target memory
[all …]
|
| D | Trace_Report_0x13_cpu_3_2015Sep17_104147.txt | 8 EL1N:0xFFFFFFC000594AC0 ? Cannot access target memory
9 EL1N:0xFFFFFFC000592B58 ? Cannot access target memory
11 EL1N:? ? Cannot access target memory
12 EL1N:? ? Cannot access target memory
13 EL1N:0xFFFFFFC0005AC4C8 ? Cannot access target memory
15 EL1N:0xFFFFFFC0000EA588 ? Cannot access target memory
16 EL1N:0xFFFFFFC0000EA588 ? Cannot access target memory
17 EL1N:0xFFFFFFC0000EA588 ? Cannot access target memory
66 EL1N:0xFFFFFFC000117CF0 ? Cannot access target memory
67 EL1N:0xFFFFFFC000117CF0 ? Cannot access target memory
[all …]
|
| D | Trace_Report_0x10_cpu_0_2015Sep17_104900.txt | 8 EL1N:0xFFFFFFC000594AC0 ? Cannot access target memory
9 EL1N:0xFFFFFFC000592B58 ? Cannot access target memory
11 EL1N:? ? Cannot access target memory
12 EL1N:? ? Cannot access target memory
13 EL1N:0xFFFFFFC0005AC4C8 ? Cannot access target memory
15 EL1N:0xFFFFFFC0000EA588 ? Cannot access target memory
16 EL1N:0xFFFFFFC0000EA588 ? Cannot access target memory
17 EL1N:0xFFFFFFC0000EA588 ? Cannot access target memory
66 EL1N:0xFFFFFFC000117CF0 ? Cannot access target memory
67 EL1N:0xFFFFFFC000117CF0 ? Cannot access target memory
[all …]
|
| D | Trace_Report_0x15_cpu_5_2015Sep17_105126.txt | 3 EL1N:0xFFFFFFC0000F3CC0 ? Cannot access target memory
5 EL1N:? ? Cannot access target memory
6 EL1N:? ? Cannot access target memory
7 EL1N:? ? Cannot access target memory
8 EL1N:? ? Cannot access target memory
9 EL1N:? ? Cannot access target memory
10 EL1N:? ? Cannot access target memory
11 EL1N:? ? Cannot access target memory
17 EL1N:0xFFFFFFC0000F9494 ? Cannot access target memory
18 EL1N:0xFFFFFFC0000F9494 ? Cannot access target memory
[all …]
|
| /external/linux-kselftest/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | 25 if ! ls $SYSFS/devices/system/memory/memory* > /dev/null 2>&1; then
26 echo $msg memory hotplug is not supported >&2
30 if ! grep -q 1 $SYSFS/devices/system/memory/memory*/removable; then
31 echo $msg no hot-pluggable memory >&2
37 # list all hot-pluggable memory
43 for memory in $SYSFS/devices/system/memory/memory*; do
44 if grep -q 1 $memory/removable &&
45 grep -q $state $memory/state; then
46 echo ${memory##/*/memory}
63 grep -q online $SYSFS/devices/system/memory/memory$1/state
[all …]
|
| /external/tensorflow/tensorflow/core/profiler/protobuf/ |
| D | memory_profile.proto | 1 // This proto is used for analysis of TensorFlow runtime memory profile.
6 // The memory activity that causes change of memory state.
9 // Memory allocation in heap.
11 // Memory deallocation in heap.
13 // Memory reservation for stack.
15 // Expansion of existing memory allocation.
19 // The aggregated memory stats including heap, stack, free memory and
22 // Memory usage by stack reservation, in bytes.
24 // Memory usage by heap allocation, in bytes.
26 // Free memory available for allocation or reservation, in bytes.
[all …]
|
| /external/llvm/unittests/Support/ |
| D | MemoryTest.cpp | 10 #include "llvm/Support/Memory.h"
28 // Adds RW flags to permit testing of the resulting memory
31 case Memory::MF_READ: in getTestableEquivalent()
32 case Memory::MF_WRITE: in getTestableEquivalent()
33 case Memory::MF_READ|Memory::MF_WRITE: in getTestableEquivalent()
34 return Memory::MF_READ|Memory::MF_WRITE; in getTestableEquivalent()
35 case Memory::MF_READ|Memory::MF_EXEC: in getTestableEquivalent()
36 case Memory::MF_READ|Memory::MF_WRITE|Memory::MF_EXEC: in getTestableEquivalent()
37 case Memory::MF_EXEC: in getTestableEquivalent()
38 return Memory::MF_READ|Memory::MF_WRITE|Memory::MF_EXEC; in getTestableEquivalent()
[all …]
|
| /external/llvm-project/llvm/unittests/Support/ |
| D | MemoryTest.cpp | 9 #include "llvm/Support/Memory.h"
57 // Adds RW flags to permit testing of the resulting memory
60 case Memory::MF_READ: in getTestableEquivalent()
61 case Memory::MF_WRITE: in getTestableEquivalent()
62 case Memory::MF_READ|Memory::MF_WRITE: in getTestableEquivalent()
63 return Memory::MF_READ|Memory::MF_WRITE; in getTestableEquivalent()
64 case Memory::MF_READ|Memory::MF_EXEC: in getTestableEquivalent()
65 case Memory::MF_READ|Memory::MF_WRITE|Memory::MF_EXEC: in getTestableEquivalent()
66 case Memory::MF_EXEC: in getTestableEquivalent()
67 return Memory::MF_READ|Memory::MF_WRITE|Memory::MF_EXEC; in getTestableEquivalent()
[all …]
|
| /external/linux-kselftest/tools/testing/selftests/cgroup/ |
| D | test_memcontrol.c | 25 * the memory controller.
33 /* Create two nested cgroups with the memory controller enabled */ in test_memcg_subtree_control()
42 if (cg_write(parent, "cgroup.subtree_control", "+memory")) in test_memcg_subtree_control()
48 if (cg_read_strstr(child, "cgroup.controllers", "memory")) in test_memcg_subtree_control()
51 /* Create two nested cgroups without enabling memory controller */ in test_memcg_subtree_control()
66 if (!cg_read_strstr(child2, "cgroup.controllers", "memory")) in test_memcg_subtree_control()
100 current = cg_read_long(cgroup, "memory.current"); in alloc_anon_50M_check()
107 anon = cg_read_key_long(cgroup, "memory.stat", "anon "); in alloc_anon_50M_check()
134 current = cg_read_long(cgroup, "memory.current"); in alloc_pagecache_50M_check()
138 file = cg_read_key_long(cgroup, "memory.stat", "file "); in alloc_pagecache_50M_check()
[all …]
|
| /external/llvm-project/clang/test/Sema/ |
| D | atomic-implicit-seq_cst.c | 4 // want to force explicit usage of memory order instead.
10 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_pre_inc()
14 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_pre_dec()
18 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_post_inc()
22 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_post_dec()
26 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_call()
30 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_plus()
34 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_minus()
38 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_logical_not()
42 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_bitwise_not()
[all …]
|
| /external/llvm-project/llvm/test/tools/llvm-rc/ |
| D | memoryflags.test | 7 ; CHECK-NEXT: Memory flags: 0x1050
11 ; CHECK-NEXT: Memory flags: 0x1050
15 ; CHECK-NEXT: Memory flags: 0x1010
19 ; CHECK-NEXT: Memory flags: 0x1030
23 ; CHECK-NEXT: Memory flags: 0x0
27 ; CHECK-NEXT: Memory flags: 0x1030
31 ; CHECK-NEXT: Memory flags: 0x1010
35 ; CHECK-NEXT: Memory flags: 0x1030
39 ; CHECK-NEXT: Memory flags: 0x1030
43 ; CHECK-NEXT: Memory flags: 0x1030
[all …]
|
| /external/autotest/client/common_lib/cros/ |
| D | memory_eater.py | 14 """A util class which run programs to consume memory in the background.
18 # Allocate mlocked memory.
21 # Allocate memory and sequentially traverse them over and over.
25 allocated memory are released.
28 memory_eater_locked = 'memory-eater-locked'
29 memory_eater = 'memory-eater'
54 """Releases all allocated memory."""
56 logging.info('Cleaning hanging memory consuming processes...')
70 """Consume non-swappable memory."""
71 logging.info('Consuming locked memory %d MB', mb)
[all …]
|
| /external/libchrome/base/memory/ |
| D | shared_memory_unittest.cc | 5 #include "base/memory/shared_memory.h"
10 #include <memory>
18 #include "base/memory/shared_memory_handle.h"
64 // Each thread will open the shared memory. Each thread will take a different 4
66 // Verify that each thread's value in the shared memory is always correct.
73 SharedMemory memory; in CleanUp() local
74 memory.Delete(s_test_name_); in CleanUp()
80 SharedMemory memory; in ThreadMain() local
81 bool rv = memory.CreateNamedDeprecated(s_test_name_, true, kDataSize); in ThreadMain()
83 rv = memory.Map(kDataSize); in ThreadMain()
[all …]
|
| /external/perfetto/docs/case-studies/ |
| D | memory.md | 1 # Debugging memory usage on Android
18 A good place to get started investigating memory usage of a process is
20 types of memory are being used by a process.
25 Applications Memory Usage (in Kilobytes):
39 Native Heap, we can see that SystemUI's memory usage on the Java heap
42 ## Linux memory management
45 this question, we need to delve into Linux memory management a bit.
47 From the kernel's point of view, memory is split into equally sized blocks
51 (Virtual Memory Area).
53 VMAs are created when a process requests a new pool of memory pages through
[all …]
|
| /external/llvm/test/MC/Mips/eva/ |
| D | invalid-noeva-wrong-error.s | 22 …cachee 31, 255($7) # CHECK: :[[@LINE]]:23: error: expected memory with 9-bit signed of…
23 …cachee 0, -256($4) # CHECK: :[[@LINE]]:22: error: expected memory with 9-bit signed of…
24 …cachee 5, -140($4) # CHECK: :[[@LINE]]:22: error: expected memory with 9-bit signed of…
25 …lbe $10,-256($25) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
26 …lbe $13,255($15) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
27 …lbe $11,146($14) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
28 …lbue $13,-256($v1) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
29 …lbue $13,255($v0) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
30 …lbue $13,-190($v1) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
31 …lhe $13,-256($s5) # CHECK: :[[@LINE]]:{{[0-9]+}}: error: expected memory with 9-bit s…
[all …]
|
| /external/deqp/doc/testspecs/VK/ |
| D | sparse_resources.txt | 14 6. Test memory aliasing for fully resident buffer objects
15 7. Test memory aliasing for partially resident images
23 of the test parameters. The memory requirements of the buffer are being checked. Device memory is a…
24 in chunks equal to the alignment parameter of buffer's memory requirements. The number of allocatio…
29 First queue is used to perform binding of device memory to sparse buffer. The binding operation sig…
37 The validation part retrieves data back from output buffer to host memory. The data is then compare…
43 The memory requirements of the image are being checked. Device memory is allocated in chunks equal …
44 of the image memory requirements. The number of allocations is equal to imageRequirements.size / im…
48 First queue is used to perform binding of device memory to sparse image. The binding operation sign…
56 The validation part retrieves data back from output buffer to host memory. The data is then compare…
[all …]
|
| /external/llvm-project/libcxx/test/libcxx/atomics/ |
| D | diagnose_invalid_memory_order.verify.cpp | 18 // Test that invalid memory order arguments are diagnosed where possible.
29 …x.load(std::memory_order_release); // expected-warning {{memory order argument to atomic operation… in main()
30 …x.load(std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operation… in main()
31 …vx.load(std::memory_order_release); // expected-warning {{memory order argument to atomic operatio… in main()
32 …vx.load(std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operatio… in main()
33 // valid memory orders in main()
40 …std::atomic_load_explicit(&x, std::memory_order_release); // expected-warning {{memory order argum… in main()
41 …std::atomic_load_explicit(&x, std::memory_order_acq_rel); // expected-warning {{memory order argum… in main()
42 …std::atomic_load_explicit(&vx, std::memory_order_release); // expected-warning {{memory order argu… in main()
43 …std::atomic_load_explicit(&vx, std::memory_order_acq_rel); // expected-warning {{memory order argu… in main()
[all …]
|
| /external/libcxx/test/libcxx/atomics/ |
| D | diagnose_invalid_memory_order.fail.cpp | 19 // Test that invalid memory order arguments are diagnosed where possible.
30 …x.load(std::memory_order_release); // expected-warning {{memory order argument to atomic operation… in main()
31 …x.load(std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operation… in main()
32 …vx.load(std::memory_order_release); // expected-warning {{memory order argument to atomic operatio… in main()
33 …vx.load(std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operatio… in main()
34 // valid memory orders in main()
41 …std::atomic_load_explicit(&x, std::memory_order_release); // expected-warning {{memory order argum… in main()
42 …std::atomic_load_explicit(&x, std::memory_order_acq_rel); // expected-warning {{memory order argum… in main()
43 …std::atomic_load_explicit(&vx, std::memory_order_release); // expected-warning {{memory order argu… in main()
44 …std::atomic_load_explicit(&vx, std::memory_order_acq_rel); // expected-warning {{memory order argu… in main()
[all …]
|
| /external/python/cpython3/Doc/library/ |
| D | multiprocessing.shared_memory.rst | 1 :mod:`multiprocessing.shared_memory` --- Provides shared memory for direct access across processes
5 :synopsis: Provides shared memory for direct access across processes.
12 single: Shared Memory
13 single: POSIX Shared Memory
14 single: Named Shared Memory
19 and management of shared memory to be accessed by one or more processes
21 the life-cycle management of shared memory especially across distinct
26 In this module, shared memory refers to "System V style" shared memory blocks
28 to "distributed shared memory". This style of shared memory permits distinct
30 volatile memory. Processes are conventionally limited to only have access to
[all …]
|
| /external/compiler-rt/test/msan/ |
| D | chained_origin_limits.cc | 4 // RUN: %clangxx_msan -fsanitize-memory-track-origins=2 -O3 %s -o %t
19 // RUN: %clangxx_msan -DSTACK -fsanitize-memory-track-origins=2 -O3 %s -o %t
35 // RUN: %clangxx_msan -mllvm -msan-instrumentation-with-call-threshold=0 -fsanitize-memory-track-or…
51 // RUN: %clangxx_msan -DSTACK -mllvm -msan-instrumentation-with-call-threshold=0 -fsanitize-memory-…
129 // CHECK7-NOT: Uninitialized value was stored to memory at
130 // CHECK7: Uninitialized value was stored to memory at
131 // CHECK7-NOT: Uninitialized value was stored to memory at
132 // CHECK7: Uninitialized value was stored to memory at
133 // CHECK7-NOT: Uninitialized value was stored to memory at
134 // CHECK7: Uninitialized value was stored to memory at
[all …]
|
| /external/python/cpython2/Doc/c-api/ |
| D | memory.rst | 7 Memory Management
19 Memory management in Python involves a private heap containing all Python
21 internally by the *Python memory manager*. The Python memory manager has
25 At the lowest level, a raw memory allocator ensures that there is enough room in
27 memory manager of the operating system. On top of the raw memory allocator,
29 distinct memory management policies adapted to the peculiarities of every object
32 requirements and speed/space tradeoffs. The Python memory manager thus delegates
38 even if they regularly manipulate object pointers to memory blocks inside that
40 buffers is performed on demand by the Python memory manager through the Python/C
49 To avoid memory corruption, extension writers should never try to operate on
[all …]
|
| /external/llvm-project/compiler-rt/test/msan/ |
| D | chained_origin_limits.cpp | 4 // RUN: %clangxx_msan -fsanitize-memory-track-origins=2 -O3 %s -o %t
19 // RUN: %clangxx_msan -DSTACK -fsanitize-memory-track-origins=2 -O3 %s -o %t
35 // RUN: %clangxx_msan -mllvm -msan-instrumentation-with-call-threshold=0 -fsanitize-memory-track-or…
51 // RUN: %clangxx_msan -DSTACK -mllvm -msan-instrumentation-with-call-threshold=0 -fsanitize-memory-…
129 // CHECK7-NOT: Uninitialized value was stored to memory at
130 // CHECK7: Uninitialized value was stored to memory at
131 // CHECK7-NOT: Uninitialized value was stored to memory at
132 // CHECK7: Uninitialized value was stored to memory at
133 // CHECK7-NOT: Uninitialized value was stored to memory at
134 // CHECK7: Uninitialized value was stored to memory at
[all …]
|
| /external/llvm-project/lld/test/wasm/ |
| D | import-memory.test | 2 # RUN: wasm-ld --import-memory -o %t.wasm %t.start.o
5 # Verify the --import-memory flag creates a memory import
10 # CHECK-NEXT: Field: memory
11 # CHECK-NEXT: Kind: MEMORY
12 # CHECK-NEXT: Memory:
18 # RUN: wasm-ld --import-memory --initial-memory=262144 \
19 # RUN: --max-memory=327680 -o %t.max.wasm %t.start.o
22 # Verify the --initial-memory and --max-memory arguments work with imports
27 # CHECK-MAX-NEXT: Field: memory
28 # CHECK-MAX-NEXT: Kind: MEMORY
[all …]
|
| /external/OpenCSD/decoder/include/common/ |
| D | ocsd_dcd_tree.h | 202 * Set a target memory access interface - used to access program image memory for instruction
212 /** @name Memory Access Mapper
214 A memory mapper is used to organise a collection of memory accessor objects that contain the
215 … memory images for different areas of traced instruction memory. These areas could be the executed
217 different memory locations.
219 … A memory accessor represents a snapshot of an area of memory as it appeared during trace capture,
220 for a given memory space. Memory spaces are described by the ocsd_mem_space_acc_t enum. The most
221 …general memory space is OCSD_MEM_SPACE_ANY. This represents memory that can be secure or none-secu…
224 The memory mapper will not allow two accessors to overlap in the same memory space.
226 …The trace decdoer will access memory with a memory space parameter that represents the current core
[all …]
|
| /external/llvm-project/lldb/test/Shell/Minidump/ |
| D | memory-region-from-module.yaml | 1 # Check that memory region parsing works correctly, with a particular emphasis
6 # RUN: yaml2obj %S/Inputs/basic-elf.yaml -o %T/memory-region-from-module.exe
8 # RUN: %lldb -b -c %t1.dmp %T/memory-region-from-module.exe \
9 # RUN: -o "memory region 0" -o "memory region 0x4000" \
10 # RUN: -o "memory region 0x5000" -o "memory region 0x6000" \
13 # RUN: %lldb -b -c %t2.dmp %T/memory-region-from-module.exe \
14 # RUN: -o "memory region 0" -o "memory region 0x4000" \
15 # RUN: -o "memory region 0x5000" -o "memory region 0x6000" \
18 # ALL-LABEL: (lldb) memory region 0
20 # ALL-LABEL: (lldb) memory region 0x4000
[all …]
|