cb01cd40 | 10-Jul-2023 |
Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> |
Dump: Add user-challenge to System Dump entry
This commit introduces a 'UserChallenge' field to the xyz.openbmc_project.Dump.Entry.System interface. This update specifically addresses the requiremen
Dump: Add user-challenge to System Dump entry
This commit introduces a 'UserChallenge' field to the xyz.openbmc_project.Dump.Entry.System interface. This update specifically addresses the requirement for non-disruptive system dumps. Non-disruptive dumps are requested to the host and do not disrupt the current system state. However, as they consume significant host resources and involve the collection of host memory data, they must be executed by authorized personnel.
To enforce this, the host requires user-challenge validation to process the dump request. If the provided user-challenge is incorrect, the host rejects the operation.
Change-Id: Ia9871a7264e036715a3ebe10f9054a2302e64c32 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
show more ...
|
2117deab | 08-Jul-2023 |
Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> |
Dump: Add 'SystemImpact' to System Dump entry
This commit introduces 'SystemImpact' to the system dump entry. This new enum field indicates whether a system dump is 'Disruptive' or 'NonDisruptive'.
Dump: Add 'SystemImpact' to System Dump entry
This commit introduces 'SystemImpact' to the system dump entry. This new enum field indicates whether a system dump is 'Disruptive' or 'NonDisruptive'.
'Disruptive' dumps alter the system state and capture extensive data, making them useful for diagnosing system crashes. In contrast, 'NonDisruptive' dumps do not disturb the system state while still providing valuable data for analysis.
Change-Id: I03810e86e1db9d2b46891dbe2e00e436e76b2cc2 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
show more ...
|