Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 6f2f09853658c4f1c3e090bf50510d3f313997a2
commit6f2f09853658c4f1c3e090bf50510d3f313997a2[log] [tgz]
authorDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Thu Jun 29 03:46:25 2023 -0500
committerDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Sun Jul 16 06:47:51 2023 -0500
tree8bd1bbf58d2508a9e26202e6508f5385704e8f2c
parent0518b74d7e03186b1128a37947a4973be4df5ea6 [diff]
BMCDump: dump subtype input parameter support

The BMC dump is not accepting any parameters to specify the type of
dump or level of data to be collected. It was always creating a default
user-requested dump.

This commit allows for the specification of the dump type during the
dump creation process. A new table has been added in a new header file
which stores the valid dump types. When a new dump is requested, the
specified dump type is verified against this table. If no dump type is
mentioned, a user-requested BMC dump is created for backward
compatibility. If an invalid dump type is mentioned, an Invalid
Argument exception is thrown.

Tested:
- Create BMC dump with no arguments
- Create BMC dump with type as user
- Create a error log dump and make sure other types of dumps
  which is using internal interface is not impacted.

Change-Id: I79f68be6ac6892ac7754b7221db64c22330b1822
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
8 files changed
tree: 8bd1bbf58d2508a9e26202e6508f5385704e8f2c
  1. .vscode/
  2. dump-extensions/
  3. host-transport-extensions/
  4. subprojects/
  5. test/
  6. tools/
  7. xyz/
  8. .clang-format
  9. .gitignore
  10. .shellcheck-ignore
  11. bmc_dump_entry.cpp
  12. bmc_dump_entry.hpp
  13. core_manager.cpp
  14. core_manager.hpp
  15. core_manager_main.cpp
  16. dump-extensions.hpp
  17. dump_entry.cpp
  18. dump_entry.hpp
  19. dump_internal.hpp
  20. dump_manager.cpp
  21. dump_manager.hpp
  22. dump_manager_bmc.cpp
  23. dump_manager_bmc.hpp
  24. dump_manager_faultlog.cpp
  25. dump_manager_faultlog.hpp
  26. dump_manager_main.cpp
  27. dump_offload.cpp
  28. dump_offload.hpp
  29. dump_serialize.cpp
  30. dump_serialize.hpp
  31. dump_types.cpp
  32. dump_types.hpp
  33. dump_utils.cpp
  34. dump_utils.hpp
  35. elog_watch.cpp
  36. elog_watch.hpp
  37. errors_map.hpp
  38. errors_map.mako.cpp
  39. errors_map_gen.py
  40. example_errors_watch.yaml
  41. faultlog_dump_entry.cpp
  42. faultlog_dump_entry.hpp
  43. ffdc
  44. host_transport_exts.hpp
  45. LICENSE
  46. meson.build
  47. meson_options.txt
  48. OWNERS
  49. ramoops_manager.cpp
  50. ramoops_manager.hpp
  51. ramoops_manager_main.cpp
  52. README.md
  53. watch.cpp
  54. 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.

One such mechanism is dreport, a script that collects debug data and packages it into an archive file.

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 -Dtests=enabled build
ninja -C build test