Create dump manager for each dump type.

Currently all types of dumps exist in the same path
and under the single dump manager. When there are
multiple dumps to be created separate path is needed
for creating and managing the dump. this commit
is splitting the dump manager into multiple objects
without  adding any new functionality. There will be
only one dump manager process but it will contain
seperate dump manager objects for system and BMC
dumps as per current scope.

Tested the existing dump functions with the build
- created bmc dump
- created system dump using notify
- deleted dump entry
- offloaded bmc dump

Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Id4806660be1f1ba0b3cb6f840ae185a967f05a83
12 files changed
tree: 413ba6449937895d67da78516074766aaa7e7b8e
  1. offload-extensions/
  2. test/
  3. tools/
  4. xyz/
  5. .clang-format
  6. .gitignore
  7. bmc_dump_entry.cpp
  8. bmc_dump_entry.hpp
  9. core_manager.cpp
  10. core_manager.hpp
  11. core_manager_main.cpp
  12. dump_entry.cpp
  13. dump_entry.hpp
  14. dump_internal.hpp
  15. dump_manager.cpp
  16. dump_manager.hpp
  17. dump_manager_bmc.cpp
  18. dump_manager_bmc.hpp
  19. dump_manager_main.cpp
  20. dump_manager_system.cpp
  21. dump_manager_system.hpp
  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. LICENSE
  35. MAINTAINERS
  36. meson.build
  37. meson_options.txt
  38. offload-extensions.hpp
  39. README.md
  40. system_dump_entry.cpp
  41. system_dump_entry.hpp
  42. watch.cpp
  43. 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