AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Joshi, Mukul" <Mukul.Joshi@amd.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCHv3 2/2] drm/amdgpu: Register MCE notifier for Aldebaran RAS
Date: Fri, 24 Sep 2021 19:46:10 +0000	[thread overview]
Message-ID: <YU4rAigWIh8g6iOl@yaz-ubuntu> (raw)
In-Reply-To: <YUzD9wxtV411S8TC@zn.tnic>

On Thu, Sep 23, 2021 at 08:14:15PM +0200, Borislav Petkov wrote:
> On Thu, Sep 23, 2021 at 05:23:21PM +0000, Yazen Ghannam wrote:
> > Shouldn't the error still be reported to EDAC for decoding and counting? I
> > think users want this.
> 
> You know what happens with users getting ECCs reported, right? They
> think immediately their hw is going bad and start wanting to replace
> it...
> 
> So what does actually tell you if you were a simple user and you had 5
> correctable errors in the GPU VRAM?
> 

I agree with you in general. But this device isn't really a GPU. And users of
this device seem to want to count *every* error, at least for now.

> All you wanna do is play, I'd say.
> 
> :-)
>

Definitely. :)

Thanks,
Yazen

  reply	other threads:[~2021-09-24 19:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210511152538.148084-2-nchatrad@amd.com>
2021-09-13  2:13 ` [PATCHv2 1/2] x86/MCE/AMD: Export smca_get_bank_type symbol Mukul Joshi
2021-09-13  2:13   ` [PATCHv2 2/2] drm/amdgpu: Register MCE notifier for Aldebaran RAS Mukul Joshi
2021-09-22 11:40     ` Borislav Petkov
2021-09-22 19:43       ` Joshi, Mukul
2021-09-22 19:36     ` [PATCHv3 " Mukul Joshi
2021-09-23 14:29       ` Yazen Ghannam
2021-09-23 14:37         ` Borislav Petkov
2021-09-23 15:31           ` Joshi, Mukul
2021-09-23 15:30         ` Joshi, Mukul
2021-09-23 17:23           ` Yazen Ghannam
2021-09-23 18:14             ` Borislav Petkov
2021-09-24 19:46               ` Yazen Ghannam [this message]
2021-09-25 11:20                 ` Borislav Petkov
2021-09-27 18:37                   ` Yazen Ghannam
2021-09-23 18:34             ` Joshi, Mukul
2021-09-23 22:04       ` [PATCHv4 " Mukul Joshi
2021-09-24 19:53         ` Yazen Ghannam
2021-09-22 11:33   ` [PATCHv2 1/2] x86/MCE/AMD: Export smca_get_bank_type symbol Borislav Petkov
2021-09-22 16:27     ` Deucher, Alexander
2021-09-22 16:43       ` Borislav Petkov
2021-09-22 16:47         ` Joshi, Mukul

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=YU4rAigWIh8g6iOl@yaz-ubuntu \
    --to=yazen.ghannam@amd.com \
    --cc=Mukul.Joshi@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mingo@redhat.com \
    --cc=x86@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