Searched hist:"475 e574da95a75af6001fdc2198c1892c1bfc041" (Results 1 – 5 of 5) sorted by relevance
/openbmc/phosphor-logging/test/openpower-pels/ |
H A D | repository_test.cpp | diff 475e574da95a75af6001fdc2198c1892c1bfc041 Thu Jul 18 16:09:49 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Remove a PEL based on an ID
When someone deletes an OpenBMC event log, the corresponding PEL should also be deleted. This commit adds support for that by keeping an internal map of the IDs to the files that contain the PEL data in the repository in order to find the file to remove. This will then get called in the phosphor-logging extension's delete hook.
The actual map key is a structure of both the PEL ID and OpenBMC log ID, so either can be used to find a PEL in the repository, which will be useful in other cases, for example for retrieving PEL data based on the PEL ID.
As the map needs to match the actual repository file contents, it will get built on startup, and modified when PELs are added and removed.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I33bb96da297c770e175c5c6b19705dda1c8766b6
|
H A D | pel_manager_test.cpp | diff 475e574da95a75af6001fdc2198c1892c1bfc041 Thu Jul 18 16:09:49 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Remove a PEL based on an ID
When someone deletes an OpenBMC event log, the corresponding PEL should also be deleted. This commit adds support for that by keeping an internal map of the IDs to the files that contain the PEL data in the repository in order to find the file to remove. This will then get called in the phosphor-logging extension's delete hook.
The actual map key is a structure of both the PEL ID and OpenBMC log ID, so either can be used to find a PEL in the repository, which will be useful in other cases, for example for retrieving PEL data based on the PEL ID.
As the map needs to match the actual repository file contents, it will get built on startup, and modified when PELs are added and removed.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I33bb96da297c770e175c5c6b19705dda1c8766b6
|
/openbmc/phosphor-logging/extensions/openpower-pels/ |
H A D | repository.hpp | diff 475e574da95a75af6001fdc2198c1892c1bfc041 Thu Jul 18 16:09:49 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Remove a PEL based on an ID
When someone deletes an OpenBMC event log, the corresponding PEL should also be deleted. This commit adds support for that by keeping an internal map of the IDs to the files that contain the PEL data in the repository in order to find the file to remove. This will then get called in the phosphor-logging extension's delete hook.
The actual map key is a structure of both the PEL ID and OpenBMC log ID, so either can be used to find a PEL in the repository, which will be useful in other cases, for example for retrieving PEL data based on the PEL ID.
As the map needs to match the actual repository file contents, it will get built on startup, and modified when PELs are added and removed.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I33bb96da297c770e175c5c6b19705dda1c8766b6
|
H A D | repository.cpp | diff 475e574da95a75af6001fdc2198c1892c1bfc041 Thu Jul 18 16:09:49 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Remove a PEL based on an ID
When someone deletes an OpenBMC event log, the corresponding PEL should also be deleted. This commit adds support for that by keeping an internal map of the IDs to the files that contain the PEL data in the repository in order to find the file to remove. This will then get called in the phosphor-logging extension's delete hook.
The actual map key is a structure of both the PEL ID and OpenBMC log ID, so either can be used to find a PEL in the repository, which will be useful in other cases, for example for retrieving PEL data based on the PEL ID.
As the map needs to match the actual repository file contents, it will get built on startup, and modified when PELs are added and removed.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I33bb96da297c770e175c5c6b19705dda1c8766b6
|
H A D | manager.cpp | diff 475e574da95a75af6001fdc2198c1892c1bfc041 Thu Jul 18 16:09:49 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Remove a PEL based on an ID
When someone deletes an OpenBMC event log, the corresponding PEL should also be deleted. This commit adds support for that by keeping an internal map of the IDs to the files that contain the PEL data in the repository in order to find the file to remove. This will then get called in the phosphor-logging extension's delete hook.
The actual map key is a structure of both the PEL ID and OpenBMC log ID, so either can be used to find a PEL in the repository, which will be useful in other cases, for example for retrieving PEL data based on the PEL ID.
As the map needs to match the actual repository file contents, it will get built on startup, and modified when PELs are added and removed.
Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I33bb96da297c770e175c5c6b19705dda1c8766b6
|