linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
	Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Muralidhara M K <muralimk@amd.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	Muralidhara M K <muralidhara.mk@amd.com>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Begin a RAS section
Date: Tue, 28 Nov 2023 09:04:22 -0800	[thread overview]
Message-ID: <7c5c3634-7a89-48b3-96fa-4d9f3be3ba05@infradead.org> (raw)
In-Reply-To: <20231128142049.GTZWX3QQTSaQk/+u53@fat_crate.local>

Hi,

On 11/28/23 06:20, Borislav Petkov wrote:
> On Thu, Nov 02, 2023 at 11:42:22AM +0000, Muralidhara M K wrote:
>> From: Muralidhara M K <muralidhara.mk@amd.com>
>>
>> AMD systems with Scalable MCA, each machine check error of a SMCA bank
>> type has an associated bit position in the bank's control (CTL) register.
> 
> Ontop of this. It is long overdue:
> 
> ---
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> Date: Tue, 28 Nov 2023 14:37:56 +0100
> 
> Add some initial RAS documentation. The expectation is for this to
> collect all the user-visible features for interacting with the RAS
> features of the kernel.
> 

In general, does RAS include EDAC and MCE?

Thanks.

> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
>  Documentation/RAS/ras.rst | 26 ++++++++++++++++++++++++++
>  Documentation/index.rst   |  1 +
>  2 files changed, 27 insertions(+)
>  create mode 100644 Documentation/RAS/ras.rst
> 


-- 
~Randy

  parent reply	other threads:[~2023-11-28 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 11:42 [PATCH v3 0/4] Few cleanups and AMD Family 19h Models 90h-9fh EDAC Support Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 1/4] EDAC/mce_amd: Remove SMCA Extended Error code descriptions Muralidhara M K
2023-11-28 14:20   ` [PATCH] Documentation: Begin a RAS section Borislav Petkov
2023-11-28 15:23     ` Yazen Ghannam
2023-11-28 17:04     ` Randy Dunlap [this message]
2023-11-28 19:39       ` Borislav Petkov
2024-01-09 17:47     ` Jonathan Corbet
2024-01-09 18:36       ` Borislav Petkov
2024-01-09 19:44         ` Jonathan Corbet
2024-01-09 20:04           ` Borislav Petkov
2024-01-24 12:40             ` Borislav Petkov
2024-02-05 19:41               ` Borislav Petkov
2023-11-28 14:24   ` [tip: ras/core] EDAC/mce_amd: Remove SMCA Extended Error code descriptions tip-bot2 for Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 2/4] x86/MCE/AMD: Add new MA_LLC, USR_DP, and USR_CP bank types Muralidhara M K
2023-11-29 10:33   ` [tip: ras/core] " tip-bot2 for Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 3/4] EDAC/mc: Add support for HBM3 memory type Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 4/4] EDAC/amd64: Add support for family 0x19, models 0x90-9f devices Muralidhara M K
2023-11-29 10:26 ` [PATCH v3 0/4] Few cleanups and AMD Family 19h Models 90h-9fh EDAC Support Borislav Petkov

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=7c5c3634-7a89-48b3-96fa-4d9f3be3ba05@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bp@alien8.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muralidhara.mk@amd.com \
    --cc=muralimk@amd.com \
    --cc=tony.luck@intel.com \
    --cc=yazen.ghannam@amd.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;
as well as URLs for NNTP newsgroup(s).