From: Borislav Petkov <bp@alien8•de>
To: Yazen Ghannam <yazen.ghannam@amd•com>
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 19:15:01 +0100 [thread overview]
Message-ID: <20161201181501.eynw6ucx6cdsg6hl@pd.tnic> (raw)
In-Reply-To: <20161201160203.hhm6w3iyrnvcukzu@yaz-fedora.dyhomenet>
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?
And I believe deferred errors can be handled differently like freeze the
process using the page instead of killing it. And so on...
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.
> Boris,
> Can we drop or revert commit d12a969ebbfc?
No can do. It is a public branch and there's no touching it.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2016-12-01 18:15 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 [this message]
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
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=20161201181501.eynw6ucx6cdsg6hl@pd.tnic \
--to=bp@alien8$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@osg$(echo .)samsung.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=yazen.ghannam@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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