| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This buffer is designed to be used in a runtime environment.
I am laying the ground work for an over arching story that will
save traces in a buffer for future consumption.
For this commit, I have created the methods necessary to add, remove and find
available space (for an Entry) in a buffer bound region of memory using a
circular, doubly linked list.
Change-Id: I259bb0f6051611a17b7b919bf026919ffdb12eb1
RTC: 191303
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/59575
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Reviewed-by: Prachi Gupta <pragupta@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
|
|
|
-Hostboot master Drawer will create TRACEBUF section in the HB
Rsvd Mem and HBRT, while booting, gets the TRACEBUF section
details and initializes the circual buffer, if available.
-If a valid data is present in the buffer, HBRT will create an
info log ERRL, otherwise initializes the buffer.
-Traces from all components are serialized and stored in the
single TRACEBUF in the same format (fsp-binary Trace). When
buffer is full, it deletes the oldest entry/entries to store
the new ones.
-ERRL->collectTrace() works similar to other buffers.
-A new test case is added to dump the traces from TRACEBUF.
Change-Id: I4ce943231a2ba30e3a13ca34d1c40ff68464a994
RTC:188726
RTC:191302
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56450
Reviewed-by: Prachi Gupta <pragupta@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
Tested-by: Daniel M. Crowell <dcrowell@us.ibm.com>
|
