From: Quan Nguyen <quan@os.amperecomputing.com>
To: Quan Nguyen <quan@os.amperecomputing.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
Open Source Submission <patches@amperecomputing.com>
Cc: Phong Vo <phong@os.amperecomputing.com>,
Thang Nguyen <thang@os.amperecomputing.com>
Subject: [PATCH v3 0/2] Add DIMM 2x refresh event and failure syndrome
Date: Fri, 10 Mar 2023 15:34:14 +0700 [thread overview]
Message-ID: <20230310083416.3670980-1-quan@os.amperecomputing.com> (raw)
Adds event_dimm_2x_refresh sysfs to report doubling of DIMM refresh
rate on high temperature condition and event_dimm[0-15]_syndrome sysfs
to report the DDR failure syndrome to BMC when DIMM training failed.
Discussion for v2:
https://lore.kernel.org/lkml/20230228092010.1863419-1-quan@os.amperecomputing.com/
v3:
+ Corrected kernel version to 6.4 [Greg]
v2:
+ Change "to initialized" to "to initialize" [Paul]
+ Corrected kernel version to 6.3 [Greg,Paul]
+ Corrected variables type to 'unsigned int" [Paul]
Quan Nguyen (2):
misc: smpro-errmon: Add DIMM 2x Refresh rate event
misc: smpro-errmon: Add dimm training failure syndrome
.../sysfs-bus-platform-devices-ampere-smpro | 19 ++++-
drivers/misc/smpro-errmon.c | 82 +++++++++++++++++++
2 files changed, 98 insertions(+), 3 deletions(-)
--
2.35.1
next reply other threads:[~2023-03-10 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 8:34 Quan Nguyen [this message]
2023-03-10 8:34 ` [PATCH v3 1/2] misc: smpro-errmon: Add DIMM 2x Refresh rate event Quan Nguyen
2023-03-10 8:34 ` [PATCH v3 2/2] misc: smpro-errmon: Add dimm training failure syndrome Quan Nguyen
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=20230310083416.3670980-1-quan@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=pmenzel@molgen.mpg.de \
--cc=thang@os.amperecomputing.com \
/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
all inboxes | Powered by JetHome®