From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "mchehab@infradead.org" <mchehab@infradead.org>,
"bp@alien8.de" <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Subject: Re: [PATCH 3/3] EDAC, ghes: Make it a proper module
Date: Wed, 26 Jul 2017 19:49:17 +0000 [thread overview]
Message-ID: <1501097993.2042.79.camel@hpe.com> (raw)
In-Reply-To: <20170726072404.3cb283c5@vento.lan>
On Wed, 2017-07-26 at 07:24 -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 26 Jul 2017 10:48:27 +0200
> Borislav Petkov <bp@alien8.de> escreveu:
>
> > From: Borislav Petkov <bp@suse.de>
> >
> > Register with the GHES notifier chain so that there's no need to
> > call into the module with ghes_edac_report_mem_error().
>
> Hmm... I'm not seeing any implementation that would allow setting
> between firmware first, hardware first or "auto", as we've discussed.
A minor nit for terminology - hardware is always the first one to
detect an error. The difference is whether an error is first reported
to the kernel or firmware. So, "kernel first" or "os first" would be
more appropriate as an alternative to "firmware first". That said,
such wording may be misleading since it does not change the mode.
Thanks,
-Toshi
next prev parent reply other threads:[~2017-07-26 19:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 8:48 [PATCH 0/3] EDAC: Convert ghes_edac to a normal module Borislav Petkov
2017-07-26 8:48 ` [PATCH 1/3] EDAC: Add edac_pr_err/info macros Borislav Petkov
2017-07-26 8:48 ` [PATCH 2/3] ACPI/GHES: Add an EDAC notifier chain Borislav Petkov
2017-07-26 8:48 ` [PATCH 3/3] EDAC, ghes: Make it a proper module Borislav Petkov
2017-07-26 10:24 ` Mauro Carvalho Chehab
2017-07-26 10:37 ` Borislav Petkov
2017-07-26 10:51 ` Mauro Carvalho Chehab
2017-07-26 17:27 ` Luck, Tony
2017-07-26 18:17 ` Mauro Carvalho Chehab
2017-07-26 19:24 ` Kani, Toshimitsu
2017-07-27 5:20 ` Borislav Petkov
2017-07-26 19:49 ` Kani, Toshimitsu [this message]
2017-07-28 18:50 ` Kani, Toshimitsu
2017-07-29 6:47 ` Borislav Petkov
2017-07-31 20:19 ` Kani, Toshimitsu
2017-08-01 9:46 ` Borislav Petkov
2017-08-02 0:19 ` Kani, Toshimitsu
2017-08-02 3:18 ` Borislav Petkov
2017-08-02 22:41 ` Kani, Toshimitsu
2017-07-27 5:54 ` [PATCH 0/3] EDAC: Convert ghes_edac to a normal module 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=1501097993.2042.79.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.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