linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Borislav Petkov <bp@suse.de>
Cc: Yazen Ghannam <Yazen.Ghannam@amd.com>, linux-next@vger.kernel.org
Subject: Re: [PATCH] EDAC: Document HW_EVENT_ERR_DEFERRED type
Date: Thu, 1 Dec 2016 19:36:45 -0200	[thread overview]
Message-ID: <20161201193645.1b5e4f24@vento.lan> (raw)
In-Reply-To: <20161201202741.gb3lkeohdo26fofu@pd.tnic>

Em Thu, 1 Dec 2016 21:27:42 +0100
Borislav Petkov <bp@suse.de> escreveu:

> On Thu, Dec 01, 2016 at 02:24:53PM -0600, Yazen Ghannam wrote:
> > Add a description of the HW_EVENT_ERR_DEFERRED type that wasn't included
> > with commit d12a969ebbfc ("EDAC, amd64: Add Deferred Error type").

Thanks for the patch!

> > 
> > Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> > Cc: Borislav Petkov <bp@suse.de>
> > Signed-off-by: Yazen Ghannam <Yazen.Ghannam@amd.com>
> > ---
> >  include/linux/edac.h | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/include/linux/edac.h b/include/linux/edac.h
> > index cb56dcb..43cd51d 100644
> > --- a/include/linux/edac.h
> > +++ b/include/linux/edac.h
> > @@ -128,6 +128,12 @@ enum dev_type {
> >   *				fatal (maybe it is on an unused memory area,
> >   *				or the memory controller could recover from
> >   *				it for example, by re-trying the operation).
> > + * @HW_EVENT_ERR_DEFERRED:	Deferred Error - Indicates an uncorrectable
> > + *				error whose handling is not urgent. This could
> > + *				be due to hardware data poisoning where the
> > + *				system can continue operation until the poisoned
> > + *				data is consumed. Preemptive measures may also
> > + *				be taken, e.g. offlining pages, etc.

I'm wandering if DEFERRED is the best name here... Maybe it could be
called, instead HW_EVENT_ERR_NON_URGENT or something like that.

Anyway, the description itself looks good.

> >   * @HW_EVENT_ERR_FATAL:		Fatal Error - Uncorrected error that could not
> >   *				be recovered.
> >   */
> > --   
> 
> Acked-by: Borislav Petkov <bp@suse.de>
> 
> Mauro, are you taking this through your tree or should I?

Boris, yeah, I can take care on it. I'll send my pull request
after yours, to avoid any issues.

-- 
Thanks,
Mauro

  reply	other threads:[~2016-12-01 21:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  3:37 linux-next: manual merge of the edac-amd tree with the edac tree Stephen Rothwell
2016-11-28  8:27 ` Borislav Petkov
2016-11-30 10:50   ` Mauro Carvalho Chehab
2016-12-01 10:48     ` Borislav Petkov
2016-12-01 12:06       ` Mauro Carvalho Chehab
2016-12-01 16:02         ` Yazen Ghannam
2016-12-01 18:15           ` Borislav Petkov
2016-12-01 19:57             ` Yazen Ghannam
2016-12-01 20:24               ` [PATCH] EDAC: Document HW_EVENT_ERR_DEFERRED type Yazen Ghannam
2016-12-01 20:27                 ` Borislav Petkov
2016-12-01 21:36                   ` Mauro Carvalho Chehab [this message]
2016-12-01 21:49                     ` Borislav Petkov
2016-12-01 22:00                       ` Mauro Carvalho Chehab

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=20161201193645.1b5e4f24@vento.lan \
    --to=mchehab@osg.samsung.com \
    --cc=Yazen.Ghannam@amd.com \
    --cc=bp@suse.de \
    --cc=linux-next@vger.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;
as well as URLs for NNTP newsgroup(s).