From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the edac-amd tree with the edac tree
Date: Thu, 1 Dec 2016 14:57:54 -0500 [thread overview]
Message-ID: <20161201195753.rrxgwvltptq4gegp@yaz-fedora.dyhomenet> (raw)
In-Reply-To: <20161201181501.eynw6ucx6cdsg6hl@pd.tnic>
On Thu, Dec 01, 2016 at 07:15:01PM +0100, Borislav Petkov wrote:
> On Thu, Dec 01, 2016 at 11:02:04AM -0500, Yazen Ghannam wrote:
> > A deferred error is an uncorrectable error whose handling can be
> > deferred, i.e. it's not urgent. This affects the system behavior, but
> > I'm now thinking that this shouldn't affect users' behavior. I think it
> > would be simpler to just classify deferred errors as uncorrectable
> > errors so that users treat them as such.
>
> Why would we want to lie about deferred errors being uncorrectable?
>
They are uncorrectable errors that can be handled differently. If you
can't handle them then there's not much difference.
> And I believe deferred errors can be handled differently like freeze the
> process using the page instead of killing it. And so on...
>
If deferred errors can be handled differently in userspace, then you're
right we should maintain the distinction. I was thinking we'd only
handle them in the kernel.
> Why aren't you simply adding the documentation about
> HW_EVENT_ERR_DEFERRED and be done with it? The downstream path like
> tracepoint and all can handle all that just fine.
>
Okay, will do.
> > Boris,
> > Can we drop or revert commit d12a969ebbfc?
>
> No can do. It is a public branch and there's no touching it.
>
Okay, got it.
Thanks,
Yazen
next prev parent reply other threads:[~2016-12-01 19:57 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 [this message]
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
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=20161201195753.rrxgwvltptq4gegp@yaz-fedora.dyhomenet \
--to=yazen.ghannam@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=sfr@canb.auug.org.au \
/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).