[all-commits] [llvm/llvm-project] 5de0a3: [trace][intelpt] Support system-wide tracing [1] -...

walter erquinigo via All-commits all-commits at lists.llvm.org
Mon May 2 08:49:09 PDT 2022

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 5de0a3e9da721189dd648a90e87829d375c5d17f
  Author: Walter Erquinigo <wallace at fb.com>
  Date:   2022-05-02 (Mon, 02 May 2022)

  Changed paths:
    M lldb/docs/lldb-gdb-remote.txt
    M lldb/include/lldb/Utility/TraceIntelPTGDBRemotePackets.h
    M lldb/source/Plugins/Process/Linux/CMakeLists.txt
    M lldb/source/Plugins/Process/Linux/IntelPTCollector.cpp
    M lldb/source/Plugins/Process/Linux/Perf.cpp
    A lldb/source/Plugins/Process/Linux/Procfs.cpp
    M lldb/source/Plugins/Process/Linux/Procfs.h
    M lldb/source/Plugins/Trace/intel-pt/TraceIntelPT.cpp
    M lldb/source/Plugins/Trace/intel-pt/TraceIntelPTSessionSaver.cpp
    M lldb/source/Utility/TraceIntelPTGDBRemotePackets.cpp
    M lldb/unittests/Process/Linux/CMakeLists.txt
    M lldb/unittests/Process/Linux/PerfTests.cpp
    A lldb/unittests/Process/Linux/ProcfsTests.cpp

  Log Message:
  [trace][intelpt] Support system-wide tracing [1] - Add a method for accessing the list of logical core ids

In order to open perf events per core, we need to first get the list of
core ids available in the system. So I'm adding a function that does
that by parsing /proc/cpuinfo. That seems to be the simplest and most
portable way to do that.

Besides that, I made a few refactors and renames to reflect better that
the cpu info that we use in lldb-server comes from procfs.

Differential Revision: https://reviews.llvm.org/D124573

More information about the All-commits mailing list