Home
last modified time | relevance | path

Searched refs:stack (Results 1 – 25 of 203) sorted by relevance

123456789

/system/core/libutils/include/utils/
DCallStack.h94 void operator()(CallStack* stack) { in operator()
95 deleteStack(stack); in operator()
121 static void ALWAYS_INLINE logStack(const char* logtag, CallStack* stack = getCurrent().get(),
123 if (reinterpret_cast<uintptr_t>(logStackInternal) != 0 && stack != nullptr) {
124 logStackInternal(logtag, stack, priority);
139 const CallStack* stack = getCurrent().get()) {
140 if (reinterpret_cast<uintptr_t>(stackToStringInternal) != 0 && stack != nullptr) {
141 return stackToStringInternal(prefix, stack);
156 static void CALLSTACK_WEAK logStackInternal(const char* logtag, const CallStack* stack,
158 static String8 CALLSTACK_WEAK stackToStringInternal(const char* prefix, const CallStack* stack);
[all …]
/system/core/libutils/
DCallStack.cpp84 CallStack::CallStackUPtr stack(new CallStack()); in getCurrentInternal() local
85 stack->update(ignoreDepth + 1); in getCurrentInternal()
86 return stack; in getCurrentInternal()
89 void CallStack::logStackInternal(const char* logtag, const CallStack* stack, in logStackInternal() argument
91 stack->log(logtag, priority); in logStackInternal()
94 String8 CallStack::stackToStringInternal(const char* prefix, const CallStack* stack) { in stackToStringInternal() argument
95 return stack->toString(prefix); in stackToStringInternal()
98 void CallStack::deleteStack(CallStack* stack) { in deleteStack() argument
99 delete stack; in deleteStack()
/system/bt/main/
DAndroid.bp30 "system/bt/stack/include",
31 "system/bt/stack/l2cap",
32 "system/bt/stack/a2dp",
33 "system/bt/stack/btm",
34 "system/bt/stack/avdt",
69 "system/bt/stack/include",
70 "system/bt/stack/l2cap",
71 "system/bt/stack/a2dp",
72 "system/bt/stack/btm",
73 "system/bt/stack/avdt",
[all …]
DBUILD.gn49 "//stack/include",
50 "//stack/l2cap",
51 "//stack/a2dp",
52 "//stack/btm",
53 "//stack/avdt",
78 "//stack",
/system/core/libprocinfo/testdata/
Dmaps351 704defa000-704defb000 ---p 00000000 00:00 0 [anon:thread stack guard]
355 704e455000-704e456000 ---p 00000000 00:00 0 [anon:thread stack guard]
362 704e69d000-704e69e000 ---p 00000000 00:00 0 [anon:thread stack guard]
365 704f79b000-704f79c000 ---p 00000000 00:00 0 [anon:thread stack guard]
367 704f899000-704f89a000 ---p 00000000 00:00 0 [anon:thread stack guard]
420 7051326000-7051327000 ---p 00000000 00:00 0 [anon:thread stack guard]
546 705ddf8000-705ddf9000 ---p 00000000 00:00 0 [anon:thread stack guard]
550 705f5ec000-705f5ed000 ---p 00000000 00:00 0 [anon:thread stack guard]
554 705f7e8000-705f7e9000 ---p 00000000 00:00 0 [anon:thread stack guard]
557 705f8ee000-705f8ef000 ---p 00000000 00:00 0 [anon:thread stack guard]
[all …]
/system/bt/doc/
Ddirectory_layout.md21 * main - *Main stack entrypoint* - Provides HAL for stack access.
22 * osi - *Operating System Interface* - General resource support for stack.
24 * stack - **Deprecated** - The Stack - Push to proper spot in *./profiles*
29 * vnd - *Vendor* - Vendor specific APIs - *to be integrated into rest of stack ?*.
Dpts_guide.md3 This document provides commands to enable PTS test mode for Fluoride stack. We
5 Fluoride stack.
27 ## PTS Helpers in stack config
29 Native stack also requires some special handling, and the config is stored in
Dbtsnoop_net.md7 Once it has been enabled and the stack restarted, the stack will listen for
/system/bt/gd/
DREADME.md7 Guidelines for developing the Gabeldorsche (GD) stack
15 tests are used in ensuring Gabeldorsche stack's stability, correctness and free
18 If you are verifying something is glued or hooked up correctly inside the stack,
25 so it applies to any stack.
/system/bt/stack/
DBUILD.gn33 static_library("stack") {
216 "//stack/a2dp",
217 "//stack/btm",
218 "//stack/include",
235 ":stack",
292 "//stack/a2dp",
293 "//stack/l2cap",
294 "//stack/btm",
295 "//stack/include",
333 "//stack/btm",
DAndroid.bp7 // Bluetooth stack static library for target
10 name: "libbt-stack",
186 // Bluetooth stack unit tests for target
231 "libbt-stack",
307 // Bluetooth stack smp unit tests for target
347 // Bluetooth stack multi-advertising unit tests for target
382 // Bluetooth stack advertise data parsing unit tests for target
401 // Bluetooth stack message loop tests for target
437 // Bluetooth stack connection multiplexing
479 "system/bt/stack/include",
/system/bt/gd/l2cap/classic/
Dfacade.proto10 // Testing Android Bluetooth stack only. Optional for other stack.
13 // Testing Android Bluetooth stack only. Optional for other stack.
/system/bt/profile/avrcp/
DAndroid.bp12 "system/bt/stack/include",
41 "system/bt/stack/include",
81 "system/bt/stack/include",
/system/bt/btif/
DBUILD.gn92 "//stack/a2dp",
93 "//stack/btm",
94 "//stack/l2cap",
95 "//stack/include",
DAndroid.bp11 "system/bt/stack/include",
12 "system/bt/stack/l2cap",
13 "system/bt/stack/a2dp",
14 "system/bt/stack/btm",
15 "system/bt/stack/avdt",
151 "libbt-stack",
/system/bt/audio_hal_interface/
DAndroid.bp11 "system/bt/stack/include",
40 "system/bt/stack/include",
/system/bt/test/headless/
DAndroid.bp18 "system/bt/stack/include",
32 "libbt-stack",
/system/bt/gd/docs/architecture/
Dstyle_guide.md26 The GD stack uses the Google Python Style Guide:
41 * One build target for the entire stack in system/bt (i.e. one cc_library())
42 * If only part of the stack needs to be compiled, configure it using the
50 * If the stack needs to be compiled using other build system, then the build
58 * Include path must be relative to the root directory of the stack. Normally
122 stack
186 * A header library to this certification stack
203 In general, errors that are caused by remote device should never crash our stack
204 and should be logged using LOG_WARN() only. Recoverable errors due to our stack
207 LOG_ALWAYS_FATAL() to crash the stack and restart.
/system/sepolicy/prebuilts/api/29.0/public/
Dnetwork_stack.te1 # Network stack service app
/system/sepolicy/public/
Dnetwork_stack.te1 # Network stack service app
/system/sepolicy/prebuilts/api/30.0/public/
Dnetwork_stack.te1 # Network stack service app
/system/core/libunwindstack/tests/files/offline/straddle_arm64/
Dmaps.txt2 0000007fe0d64000-0000007fe0d84fff rw-p 00000000 00:00 0 [stack]
/system/extras/simpleperf/doc/
DREADME.md43 a. When recording dwarf based call graph, simpleperf unwinds the stack before writing a sample
54 d. It uses the standard Android stack unwinder, so its results are consistent with all other
125 mode, recording stack frame based call graphs doesn't work well.
130 Below is our experiences of dwarf based call graphs and stack frame based call graphs.
135 3. Can only unwind 64K stack for each sample. So usually can't show complete flamegraph. But
137 4. Take more CPU time than stack frame based call graphs. So the sample frequency is suggested
140 stack frame based call graphs:
141 1. Need support of stack frame registers.
143 stack frame registers. So the kernel can't unwind user stack containing both ARM/THUMB code.
145 reserve stack frame registers.
[all …]
/system/bt/gd/cert/
Dasync_subprocess_logger.py84 with ExitStack() as stack:
85 … log_files = [stack.enter_context(open(file_path, 'w')) for file_path in self.log_file_paths]
/system/tools/hidl/
DType.cpp226 std::unordered_set<const Type*>* stack) const { in topologicalOrder()
227 if (stack->find(this) != stack->end()) { in topologicalOrder()
233 stack->insert(this); in topologicalOrder()
236 auto err = nextType->topologicalOrder(reversedOrder, stack); in topologicalOrder()
256 auto err = nextType->topologicalOrder(reversedOrder, stack); in topologicalOrder()
271 CHECK(stack->find(this) != stack->end()); in topologicalOrder()
272 stack->erase(this); in topologicalOrder()

123456789