Home
last modified time | relevance | path

Searched refs:perCpuTracing (Results 1 – 3 of 3) sorted by relevance

/llvm-project-15.0.7/lldb/packages/Python/lldbsuite/test/tools/intelpt/
H A Dintelpt_testcase.py63 psbPeriod=None, perCpuTracing=False): argument
72 obj["perCpuTracing"] = perCpuTracing
101 perCpuTracing=False): argument
106 psbPeriod=psbPeriod, perCpuTracing=perCpuTracing)
116 if perCpuTracing:
/llvm-project-15.0.7/lldb/test/API/commands/trace/multiple-threads/
H A DTestTraceStartStopMultipleThreads.py176 perCpuTracing=True,
180 self.traceStartProcess(perCpuTracing=True)
183 self.traceStartProcess(perCpuTracing=True)
185 self.traceStartProcess(error=True, perCpuTracing=True,
/llvm-project-15.0.7/lldb/docs/
H A Dlldb-gdb-remote.txt302 // "perCpuTracing" option is false, then each thread is traced individually
306 // huge. If "perCpuTracing" is true, then each cpu core is traced invidually
309 // "perCpuTracing" below for more information.
355 // "perCpuTracing": <boolean>
377 // If "perCpuTracing" is false, whenever a thread is attempted to be
382 // If "perCpuTracing" is true, then starting the system-wide trace