Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 62337a9253eeb78187a7ae7ce8a2cb1d9d771daf
commit62337a9253eeb78187a7ae7ce8a2cb1d9d771daf[log] [tgz]
authorDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Sun Nov 22 21:24:30 2020 -0600
committerDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Mon Jan 18 03:55:58 2021 -0600
tree55129fb3daf9263e4902f0f1cbd505269f182e84
parent6a54d9afebfd204ace67b842f7b3c2373451f472 [diff]
Add Resource dump support

To build use option -Dhost-transport=pldm and
-Dopenpower-dumps-extension=enabled
Add support for resource dump operations like
creation and offloading.
Tests:(Dump manager tests)
  Created dump entry.
  Faked notify to check whether progress is turning to completed.

Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Ifeec5670a7806d7ee1b572158b4fff7dc14729a6
8 files changed
tree: 55129fb3daf9263e4902f0f1cbd505269f182e84
  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