#
075c7923 |
| 16-Aug-2024 |
Patrick Williams <patrick@stwcx.xyz> |
clang-format: re-format for clang-18
clang-format-18 isn't compatible with the clang-format-17 output, so we need to reformat the code with the latest version. The way clang-18 handles lambda forma
clang-format: re-format for clang-18
clang-format-18 isn't compatible with the clang-format-17 output, so we need to reformat the code with the latest version. The way clang-18 handles lambda formatting also changed, so we have made changes to the organization default style format to better handle lambda formatting.
See I5e08687e696dd240402a2780158664b7113def0e for updated style. See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement.
Change-Id: I21d2ca8065f24fd73509229c517f5caf48934b60 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
5bc26533 |
| 10-Apr-2024 |
Arya K Padman <aryakpadman@gmail.com> |
PEL: Changing the remaining traces to lg2 style
Some of the logging traces of PEL files still uses old style of logging.
Changing the remaining traces in PEL files to lg2 style of logging.Some of t
PEL: Changing the remaining traces to lg2 style
Some of the logging traces of PEL files still uses old style of logging.
Changing the remaining traces in PEL files to lg2 style of logging.Some of the traces in phosphor logging code which use the old style is also considered.
Change-Id: I0daf9589af443881cb61730047c23db17fdec2c3 Signed-off-by: Arya K Padman <aryakpadman@gmail.com>
show more ...
|
#
1aa90d49 |
| 13-Sep-2023 |
Jayanth Othayoth <ojayanth@in.ibm.com> |
PEL: switch fmt::format to use std::format
fmt::format is supported in the c++ std. This will help to remove fmt package dependency.
Change-Id: I89f0a5b67bbfe54168a20e93c989a1ae87f54503 Signed-
PEL: switch fmt::format to use std::format
fmt::format is supported in the c++ std. This will help to remove fmt package dependency.
Change-Id: I89f0a5b67bbfe54168a20e93c989a1ae87f54503 Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
show more ...
|
#
8ac20500 |
| 04-Jan-2023 |
Matt Spinler <spinler@us.ibm.com> |
PEL: Put validation fail details into journal msg
In the PEL section classes, move some journal fields from the journal metadata section into the journal message itself, to make debug slightly easie
PEL: Put validation fail details into journal msg
In the PEL section classes, move some journal fields from the journal metadata section into the journal message itself, to make debug slightly easier.
Specifically, this is just for when unflattening or validating the sections fail.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I6d5661015b5ce5c07ed2fd6eb7ce864d0c620092
show more ...
|
#
7f1b9052 |
| 22-Mar-2022 |
Matt Spinler <spinler@us.ibm.com> |
Revert "PEL: Create trace wrapper for peltool"
This reverts commit 2ea96f6c6c92bb585668cff7c659cdea606dfc68.
Going to go in a different direction and not build peltool in other contexts.
Change-Id
Revert "PEL: Create trace wrapper for peltool"
This reverts commit 2ea96f6c6c92bb585668cff7c659cdea606dfc68.
Going to go in a different direction and not build peltool in other contexts.
Change-Id: I92fefbb3fe5249f2cc0ccf679febe5a3b3340048
show more ...
|
#
2ea96f6c |
| 23-Feb-2022 |
Matt Spinler <spinler@us.ibm.com> |
PEL: Create trace wrapper for peltool
In preparation for peltool being compiled for non-BMC platforms where libphosphor_logging.so isn't available, create a wrapper function for tracing so phosphor:
PEL: Create trace wrapper for peltool
In preparation for peltool being compiled for non-BMC platforms where libphosphor_logging.so isn't available, create a wrapper function for tracing so phosphor::logging::log() isn't directly used by the code that is part of peltool.
For now, the wrapper will just call phosphor::logging::log, but in the future will be changed to call std::cerr when not on the BMC.
A few files were changed to make use of the new calls. Others will be done with future commits. Only the code that is built into peltool needs to use this. This mostly consists of the PEL section classes.
Using this new API does mean no extra data can be stored in the journal metadata, as the systemd journal may not be available on some platforms the tool may need to run on, such as AIX. Instead, the data can just be added into the trace string itself.
In a future commit, the meson.build file will be refactored to remove the libphosphor_logging dependency so the build will fail if a call to the phosphor-logging's log() is made within peltool code.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I5e6c235d60466b031e15b157860c07a3f8ddb148
show more ...
|
#
d26fa3e7 |
| 21-Apr-2021 |
Patrick Williams <patrick@stwcx.xyz> |
openpower-pels: clean up various compile warnings
Compile warnings observed when compiling parts of the openpower-pels (or corresponding tests) under stricter compiler warning flags of Meson.
Issue
openpower-pels: clean up various compile warnings
Compile warnings observed when compiling parts of the openpower-pels (or corresponding tests) under stricter compiler warning flags of Meson.
Issues fixed: - many unused parameters - invalid case fall-through - excess semi-colons - incorrect 'const' on return-by-value type - removal of variable length array in test case - uncaught return from 'system' call in test case
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8af69184042cf8661d1307a02ecf3afcab4724a1
show more ...
|
#
386a61e6 |
| 13-Aug-2020 |
Matt Spinler <spinler@us.ibm.com> |
PEL: ExtendedUserData section class
This class represents the Extended User Data section. This section is similar to the UserData class in that it stores free form FFDC data, except that it is mean
PEL: ExtendedUserData section class
This class represents the Extended User Data section. This section is similar to the UserData class in that it stores free form FFDC data, except that it is meant to be added to an already existing PEL by a creator subsystem that is different than the PEL creator's subsystem. As such, it stores the section creator's creator ID value as a field within the section, which the regular UserData class doesn't do.
The same parsers that run on the UserData section can also run on this section.
Change-Id: I8562a89141f0305e397703f0cb92a06eb9f10133
show more ...
|