Hello Xie XiuQi,
On 3/21/2017 8:48 PM, Xie XiuQi wrote:
Reviewed-by: Xie XiuQi
Thank you!
Tyler
On 2017/3/22 6:47, Tyler Baicar wrote:
Currently there are trace events for the various RAS
errors with the exception of ARM processor type errors.
Add a new trace event for
Hello Xie XiuQi,
On 3/21/2017 8:48 PM, Xie XiuQi wrote:
Reviewed-by: Xie XiuQi
Thank you!
Tyler
On 2017/3/22 6:47, Tyler Baicar wrote:
Currently there are trace events for the various RAS
errors with the exception of ARM processor type errors.
Add a new trace event for such errors so that
Reviewed-by: Xie XiuQi
On 2017/3/22 6:47, Tyler Baicar wrote:
> Currently there are trace events for the various RAS
> errors with the exception of ARM processor type errors.
> Add a new trace event for such errors so that the user
> will know when they occur. These trace
Reviewed-by: Xie XiuQi
On 2017/3/22 6:47, Tyler Baicar wrote:
> Currently there are trace events for the various RAS
> errors with the exception of ARM processor type errors.
> Add a new trace event for such errors so that the user
> will know when they occur. These trace events are
> consistent
Currently there are trace events for the various RAS
errors with the exception of ARM processor type errors.
Add a new trace event for such errors so that the user
will know when they occur. These trace events are
consistent with the ARM processor error section type
defined in UEFI 2.6 spec
Currently there are trace events for the various RAS
errors with the exception of ARM processor type errors.
Add a new trace event for such errors so that the user
will know when they occur. These trace events are
consistent with the ARM processor error section type
defined in UEFI 2.6 spec
6 matches
Mail list logo