From: Tyler Baicar OS <baicar@os.amperecomputing.com>
To: Open Source Submission <patches@amperecomputing.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"guohanjun@huawei.com" <guohanjun@huawei.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"lenb@kernel.org" <lenb@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"Matteo.Carlini@arm.com" <Matteo.Carlini@arm.com>,
"Andrew.Murray@arm.com" <Andrew.Murray@arm.com>
Cc: Tyler Baicar OS <baicar@os.amperecomputing.com>
Subject: [PATCH RFC 4/4] trace, ras: add ARM RAS extension trace event
Date: Tue, 2 Jul 2019 16:52:01 +0000 [thread overview]
Message-ID: <1562086280-5351-5-git-send-email-baicar@os.amperecomputing.com> (raw)
In-Reply-To: <1562086280-5351-1-git-send-email-baicar@os.amperecomputing.com>
Add a trace event for hardware errors reported by the ARMv8.2
RAS extension registers.
Signed-off-by: Tyler Baicar <baicar@os.amperecomputing.com>
---
arch/arm64/kernel/ras.c | 3 +++
drivers/acpi/arm64/aest.c | 4 ++++
include/ras/ras_event.h | 46 ++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 53 insertions(+)
diff --git a/arch/arm64/kernel/ras.c b/arch/arm64/kernel/ras.c
index ca47efa..4e34d63 100644
--- a/arch/arm64/kernel/ras.c
+++ b/arch/arm64/kernel/ras.c
@@ -5,6 +5,7 @@
#include <linux/smp.h>
#include <asm/ras.h>
+#include <ras/ras_event.h>
void arch_arm_ras_report_error(void)
{
@@ -50,6 +51,8 @@ void arch_arm_ras_report_error(void)
regs.err_misc1);
}
+ trace_arm_ras_ext_event(0, cpu_num, ®s);
+
/*
* In the future, we will treat UER conditions as potentially
* recoverable.
diff --git a/drivers/acpi/arm64/aest.c b/drivers/acpi/arm64/aest.c
index fd4f3b5..21ec583 100644
--- a/drivers/acpi/arm64/aest.c
+++ b/drivers/acpi/arm64/aest.c
@@ -13,6 +13,7 @@
#include <linux/ratelimit.h>
#include <asm/ras.h>
+#include <ras/ras_event.h>
#undef pr_fmt
#define pr_fmt(fmt) "ACPI AEST: " fmt
@@ -102,6 +103,9 @@ static void aest_proc(struct aest_node_data *data)
aest_print(data, regs, i);
+ trace_arm_ras_ext_event(data->node_type, data->data.proc.id,
+ ®s);
+
if (regs.err_status & ERR_STATUS_UE)
fatal = true;
diff --git a/include/ras/ras_event.h b/include/ras/ras_event.h
index 36c5c5e..8b76cb1 100644
--- a/include/ras/ras_event.h
+++ b/include/ras/ras_event.h
@@ -339,6 +339,52 @@
);
/*
+ * ARM RAS Extension Events Report
+ *
+ * This event is generated when an error reported by the ARM RAS extension
+ * hardware is detected.
+ */
+
+#ifdef CONFIG_ARM64
+#include <asm/ras.h>
+TRACE_EVENT(arm_ras_ext_event,
+
+ TP_PROTO(u8 type, u32 id, struct ras_ext_regs *regs),
+
+ TP_ARGS(type, id, regs),
+
+ TP_STRUCT__entry(
+ __field(u8, type)
+ __field(u32, id)
+ __field(u64, err_fr)
+ __field(u64, err_ctlr)
+ __field(u64, err_status)
+ __field(u64, err_addr)
+ __field(u64, err_misc0)
+ __field(u64, err_misc1)
+ ),
+
+ TP_fast_assign(
+ __entry->type = type;
+ __entry->id = id;
+ __entry->err_fr = regs->err_fr;
+ __entry->err_ctlr = regs->err_ctlr;
+ __entry->err_status = regs->err_status;
+ __entry->err_addr = regs->err_addr;
+ __entry->err_misc0 = regs->err_misc0;
+ __entry->err_misc1 = regs->err_misc1;
+ ),
+
+ TP_printk("type: %d; id: %d; ERR_FR: %llx; ERR_CTLR: %llx; "
+ "ERR_STATUS: %llx; ERR_ADDR: %llx; ERR_MISC0: %llx; "
+ "ERR_MISC1: %llx",
+ __entry->type, __entry->id, __entry->err_fr,
+ __entry->err_ctlr, __entry->err_status, __entry->err_addr,
+ __entry->err_misc0, __entry->err_misc1)
+);
+#endif
+
+/*
* memory-failure recovery action result event
*
* unsigned long pfn - Page Frame Number of the corrupted page
--
1.8.3.1
prev parent reply other threads:[~2019-07-02 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 16:51 [PATCH RFC 0/4] ARM Error Source Table Support Tyler Baicar OS
2019-07-02 16:51 ` [PATCH RFC 1/4] ACPI/AEST: Initial AEST driver Tyler Baicar OS
2019-07-03 9:25 ` Andrew Murray
2019-07-03 17:30 ` Tyler Baicar OS
2019-07-04 9:05 ` Andrew Murray
2019-07-04 16:02 ` Shiju Jose
2019-07-10 0:49 ` Tyler Baicar OS
2019-07-02 16:51 ` [PATCH RFC 2/4] arm64: mm: Add RAS extension system register check to SEA handling Tyler Baicar OS
2019-07-08 10:00 ` James Morse
2019-07-10 0:51 ` Tyler Baicar OS
2019-07-11 4:14 ` Tyler Baicar OS
2019-07-17 17:41 ` James Morse
2019-07-02 16:51 ` [PATCH RFC 3/4] arm64: traps: Add RAS extension system register check to serror handling Tyler Baicar OS
2019-07-02 16:52 ` Tyler Baicar OS [this message]
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=1562086280-5351-5-git-send-email-baicar@os.amperecomputing.com \
--to=baicar@os.amperecomputing.com \
--cc=Andrew.Murray@arm.com \
--cc=Matteo.Carlini@arm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=patches@amperecomputing.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.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).