Hi Baicar Tyler,
On 2017/3/11 2:23, Baicar, Tyler wrote:
> Hello Xie XiuQi,
>
>
> On 3/9/2017 2:41 AM, Xie XiuQi wrote:
>> On 2017/3/7 4:45, 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 with the ARM processor error section type
>>> defined in UEFI 2.6 spec section N.2.4.4.
>>>
>>> Signed-off-by: Tyler Baicar <tbaicar@xxxxxxxxxxxxxx>
>>> Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx>
>>> ---
>>> drivers/acpi/apei/ghes.c | 8 +++++++-
>>> drivers/firmware/efi/cper.c | 1 +
>>> drivers/ras/ras.c | 1 +
>>> include/ras/ras_event.h | 34 ++++++++++++++++++++++++++++++++++
>>> 4 files changed, 43 insertions(+), 1 deletion(-)
>
>>> diff --git a/include/ras/ras_event.h b/include/ras/ras_event.h
>>> index 5861b6f..b36db48 100644
>>> --- a/include/ras/ras_event.h
>>> +++ b/include/ras/ras_event.h
>>> @@ -162,6 +162,40 @@
>>> );
>>> /*
>>> + * ARM Processor Events Report
>>> + *
>>> + * This event is generated when hardware detects an ARM processor error
>>> + * has occurred. UEFI 2.6 spec section N.2.4.4.
>>> + */
>>> +TRACE_EVENT(arm_event,
>>> +
>>> + TP_PROTO(const struct cper_sec_proc_arm *proc),
>>> +
>>> + TP_ARGS(proc),
>>> +
>>> + TP_STRUCT__entry(
>>> + __field(u64, mpidr)
>>> + __field(u64, midr)
>>> + __field(u32, running_state)
>>> + __field(u32, psci_state)
>>> + __field(u8, affinity)
>>> + ),
>>> +
>>> + TP_fast_assign(
>>> + __entry->affinity = proc->affinity_level;
>>> + __entry->mpidr = proc->mpidr;
>>> + __entry->midr = proc->midr;
>>> + __entry->running_state = proc->running_state;
>>> + __entry->psci_state = proc->psci_state;
>>> + ),
>>> +
>>> + TP_printk("affinity level: %d; MPIDR: %016llx; MIDR: %016llx; "
>>> + "running state: %d; PSCI state: %d",
>>> + __entry->affinity, __entry->mpidr, __entry->midr,
>>> + __entry->running_state, __entry->psci_state)
>>> +);
>>> +
>> I think these fields are not enough, we need also export arm processor error
>> information (UEFI 2.6 spec section N.2.4.4.1), or at least the error type,
>> address, etc. So that the userspace (such as rasdaemon tool) could know what
>> error occurred.
>
> This is something I am planning on adding in later. It is not clear to me how to
> actually do this at this point. If you look at the spec, there is not a single
> error information structure. There is at least one, but possibly a lot. There is
> also an unknown amount of context information structures. In "Table 260. ARM Processor
> Error Section" there are ERR_INFO_NUM and CONTEXT_INFO_NUM which give the number of these
> structures. I think there will need to be separate trace events added in for each of
> these structures because I don't think there is a way to have variable amounts of
> structures inside of a trace event.
Yes, I agree.
Additional, cper_sec_proc_arm has validation bit, which indicates whether or not each of
the fields is valid in this section. How could we show it in this trace event? If the filed
is invalid, we would get a wrong value here.
--
Thanks,
Xie XiuQi
>
> The ARM processor error section also has a vendor specific error info buffer which will need to be exposed to userspace. This may be something that can reuse the unknown section type trace event or have it's own trace event for.
>
> Thanks,
> Tyler
>
