mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: Borislav Petkov <bp@alien8.de>, Fan Wu <wufan@codeaurora.org>
Cc: mchehab@kernel.org, baicar.tyler@gmail.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, "Kani,
	Toshi" <toshi.kani@hpe.com>
Subject: Re: [PATCH] EDAC, ghes: use CPER module handles to locate DIMMs
Date: Thu, 30 Aug 2018 17:34:30 +0100	[thread overview]
Message-ID: <150ad0e4-e84a-565b-95ac-e7135e98bdc0@arm.com> (raw)
In-Reply-To: <20180830104307.GC20005@nazgul.tnic>

Hi Boris,

On 30/08/18 11:43, Borislav Petkov wrote:
> On Wed, Aug 29, 2018 at 06:33:52PM +0000, Fan Wu wrote:
>> The current ghes_edac driver does not update per-dimm error
>> counters when reporting memory errors, because there is no
>> platform-independent way to find DIMMs based on the error
>> information provided by firmware. This patch offers a solution
>> for platforms whose firmwares provide valid module handles
>> (SMBIOS type 17) in error records. In this case ghes_edac will
>> use the module handles to locate DIMMs and thus makes per-dimm
>> error reporting possible.

> If we're going to do this, it needs to be tested on an x86 box which loads
> ghes_edac. Adding Toshi to Cc.

Good point, thanks.


> Otherwise it must remain ARM-specific.

Hmmm, that would be a shame.

This should only be a problem if HPE Servers set CPER_MEM_VALID_MODULE_HANDLE,
but don't actually provide module handles, or if firmware has a different idea
of what they are.

If firmware never sets CPER_MEM_VALID_MODULE_HANDLE, this patch shouldn't change
anything.

(Someone must have an x86 that sets CPER_MEM_VALID_MODULE_HANDLE, otherwise the
code wouldn't be there right?!)


Thanks,

James

  parent reply	other threads:[~2018-08-30 16:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 18:33 Fan Wu
2018-08-30 10:43 ` Borislav Petkov
2018-08-30 14:20   ` wufan
2018-08-30 15:12     ` Boris Petkov
2018-08-30 16:34   ` James Morse [this message]
2018-08-30 10:48 ` James Morse
2018-08-30 14:40   ` wufan
2018-08-30 16:32     ` James Morse
2018-08-30 16:45       ` wufan
2018-08-30 16:46       ` Tyler Baicar
2018-08-30 17:11         ` wufan
2018-08-30 16:34 ` James Morse
2018-08-30 16:50   ` John Garry
2018-08-31 10:06     ` tanxiaofei
2018-09-03 15:05       ` wufan
2018-09-03 19:18         ` 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=150ad0e4-e84a-565b-95ac-e7135e98bdc0@arm.com \
    --to=james.morse@arm.com \
    --cc=baicar.tyler@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=toshi.kani@hpe.com \
    --cc=wufan@codeaurora.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

Powered by JetHome