Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 3af5c32bc26f108501ae3353f9470f122a687b7c
commit3af5c32bc26f108501ae3353f9470f122a687b7c[log] [tgz]
authorRamesh Iyyar <rameshi1@in.ibm.com>Fri Dec 04 00:38:42 2020 -0600
committerRamesh Iyyar <rameshi1@in.ibm.com>Wed Dec 16 05:21:21 2020 -0600
tree142b3bc3b67a4a424d6a5867cd9269c2a67f15c3
parent131994bedbfa09a821e0860382969e79b58d23ee [diff]
offload: Moved existing pldm offload as oem/ibm command

Currently used host mctp end point id is ibm specific and also
the used effecter id (0x05) is for phyp and "SetNumericEffecterValue"
pldm command is common so, changing existing pldm offload implementation
into oem based and added default pldm offload interface as well.

Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I8a401e03d29f9245dd54577b8b7b1d87d4a13d18
9 files changed
tree: 142b3bc3b67a4a424d6a5867cd9269c2a67f15c3
  1. dump-extensions/
  2. host-transport-extensions/
  3. test/
  4. tools/
  5. xyz/
  6. .clang-format
  7. .gitignore
  8. bmc_dump_entry.cpp
  9. bmc_dump_entry.hpp
  10. core_manager.cpp
  11. core_manager.hpp
  12. core_manager_main.cpp
  13. dump-extensions.hpp
  14. dump_entry.cpp
  15. dump_entry.hpp
  16. dump_internal.hpp
  17. dump_manager.cpp
  18. dump_manager.hpp
  19. dump_manager_bmc.cpp
  20. dump_manager_bmc.hpp
  21. dump_manager_main.cpp
  22. dump_offload.cpp
  23. dump_offload.hpp
  24. dump_serialize.cpp
  25. dump_serialize.hpp
  26. dump_utils.cpp
  27. dump_utils.hpp
  28. elog_watch.cpp
  29. elog_watch.hpp
  30. errors_map.mako.hpp
  31. errors_map_gen.py
  32. example_errors_watch.yaml
  33. ffdc
  34. host_transport_exts.hpp
  35. LICENSE
  36. MAINTAINERS
  37. meson.build
  38. meson_options.txt
  39. README.md
  40. watch.cpp
  41. watch.hpp
README.md

phosphor-debug-collector

Phosphor Debug Collector provides mechanisms to collect various log files and system parameters. Used to troubleshoot problems in OpenBMC based systems.

To Build

To build this package with meson, do the following steps:

    1. meson builddir
    2. ninja -C builddir

To clean the built files run ninja -C builddir clean.

To run unit tests

Tests can be run in the CI docker container, refer local-ci-build

or with an OpenBMC x86 sdk(see below for x86 steps).

meson -Doe-sdk=enabled -Dtests=enabled build
ninja -C build test