Searched hist:"6 bc74ae6a1c3deafd95cd098698ad3ea8b45b712" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | device_callouts_test.cpp | diff 6bc74ae6a1c3deafd95cd098698ad3ea8b45b712 Wed Jun 03 15:13:59 CDT 2020 Matt Spinler <spinler@us.ibm.com> PEL: devcallouts: Get callouts from the JSON
Using the functions that extract search keys from the device path, look
up the callouts in the appriopriate JSON entry and return them as a
vector of Callout objects.
The first callout will have the 'debug' field filled in with the search
keys used and the MRW target name of the destination device. In the
future this will be added into a UserData section of a PEL with these
callouts to make debugging easier - i.e. making it easier to know what
device it was that failed when looking at the PEL.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic4df1ce95fbc5ed277b43a1ffca08ce477d5f8c6
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | device_callouts.cpp | diff 6bc74ae6a1c3deafd95cd098698ad3ea8b45b712 Wed Jun 03 15:13:59 CDT 2020 Matt Spinler <spinler@us.ibm.com> PEL: devcallouts: Get callouts from the JSON
Using the functions that extract search keys from the device path, look
up the callouts in the appriopriate JSON entry and return them as a
vector of Callout objects.
The first callout will have the 'debug' field filled in with the search
keys used and the MRW target name of the destination device. In the
future this will be added into a UserData section of a PEL with these
callouts to make debugging easier - i.e. making it easier to know what
device it was that failed when looking at the PEL.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic4df1ce95fbc5ed277b43a1ffca08ce477d5f8c6
|