Lines Matching full:logging

30 Extensions within phosphor-logging may process logs that do not always come
31 through the standard phosphor-logging interfaces (for example logs sent down by
40   phosphor-logging log is created with a inventory callout
56   utilized by phosphor-logging extensions to halt firmware for other causes
68 `xyz.openbmc_project.Logging.Settings`. Within this create a boolean property
74 `xyz.openbmc_project.Logging.ErrorBlocksTransition`
77 `/xyz/openbmc_project/logging/blockX` where X is the instance of the
80 When an error is created via a phosphor-logging interface, the software will
82 `xyz.openbmc_project.Logging.Settings.QuiesceOnHwError`. If this is true then
83 phosphor-logging will create a `/xyz/openbmc_project/logging/blockX` D-Bus
84 object with a `xyz.openbmc_project.Logging.ErrorBlocksTransition` interface
87 phosphor-logging.
94 See the phosphor-logging [callout][4] design for more information on callouts.
117 The interfaces provided within phosphor-logging to handle the hardware callout
122 Currently this feature is a part of the base phosphor-logging design. If no one
124 phosphor-logging.
149   https://github.com/openbmc/phosphor-logging/blob/master/extensions/openpower-pels/README.md