From: tbaicar@codeaurora.org (Baicar, Tyler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V9 09/10] trace, ras: add ARM processor error trace event
Date: Wed, 15 Feb 2017 10:51:43 -0700 [thread overview]
Message-ID: <6421d298-0497-1a2c-7aa2-c53e4bc4a466@codeaurora.org> (raw)
In-Reply-To: <20170215124743.68343176@gandalf.local.home>
On 2/15/2017 10:47 AM, Steven Rostedt wrote:
> On Wed, 15 Feb 2017 10:44:51 -0700
> Tyler Baicar <tbaicar@codeaurora.org> 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@codeaurora.org>
>> Acked-by: Steven Rostedt <rostedt@goodmis.org>
>> ---
>> 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/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
>> index be365e2..560a172 100644
>> --- a/drivers/acpi/apei/ghes.c
>> +++ b/drivers/acpi/apei/ghes.c
>> @@ -514,7 +514,13 @@ static void ghes_do_proc(struct ghes *ghes,
>> }
>> #endif
>> #ifdef CONFIG_RAS
>> - else if(trace_unknown_sec_event_enabled()) {
>> + else if (!uuid_le_cmp(sec_type, CPER_SEC_PROC_ARM) &&
>> + trace_arm_event_enabled()) {
>> + struct cper_sec_proc_arm *arm_err;
>> +
>> + arm_err = acpi_hest_generic_data_payload(gdata);
>> + trace_arm_event(arm_err);
>> + } else if(trace_unknown_sec_event_enabled()) {
> I think you want a space between "if" and "("
>
> -- Steve
Oops :) I'll add that in.
>> void *unknown_err = acpi_hest_generic_data_payload(gdata);
>> trace_unknown_sec_event(&sec_type,
>> fru_id, fru_text, sec_sev,
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-02-15 17:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 17:44 [PATCH V9 00/10] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64 Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 01/10] acpi: apei: read ack upon ghes record consumption Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 02/10] ras: acpi/apei: cper: generic error data entry v3 per ACPI 6.1 Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 03/10] efi: parse ARM processor error Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 04/10] arm64: exception: handle Synchronous External Abort Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 05/10] acpi: apei: handle SEA notification type for ARMv8 Tyler Baicar
2017-02-15 20:52 ` kbuild test robot
2017-02-15 17:44 ` [PATCH V9 06/10] acpi: apei: panic OS with fatal error status block Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 07/10] efi: print unrecognized CPER section Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 08/10] ras: acpi / apei: generate trace event for " Tyler Baicar
2017-02-15 17:44 ` [PATCH V9 09/10] trace, ras: add ARM processor error trace event Tyler Baicar
2017-02-15 17:47 ` Steven Rostedt
2017-02-15 17:51 ` Baicar, Tyler [this message]
2017-02-15 17:44 ` [PATCH V9 10/10] arm/arm64: KVM: add guest SEA support Tyler Baicar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6421d298-0497-1a2c-7aa2-c53e4bc4a466@codeaurora.org \
--to=tbaicar@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).