Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1534365
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: manual merge of the edac-amd tree with the edac tree |
| Date | 2016-12-01 19:20 +0100 |
| Message-ID | <sJE7D-85V-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <sIpu1-883-19@gated-at.bofh.it> <sJaMi-52Z-23@gated-at.bofh.it> <sJx6a-2JW-21@gated-at.bofh.it> <sJylz-3Eb-13@gated-at.bofh.it> <sJE7D-85V-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
linux-next: manual merge of the edac-amd tree with the edac tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-11-28 04:40 +0100
Re: linux-next: manual merge of the edac-amd tree with the edac tree Borislav Petkov <bp@alien8.de> - 2016-11-28 09:30 +0100
Re: linux-next: manual merge of the edac-amd tree with the edac tree Mauro Carvalho Chehab <mchehab@osg.samsung.com> - 2016-11-30 12:00 +0100
Re: linux-next: manual merge of the edac-amd tree with the edac tree Borislav Petkov <bp@alien8.de> - 2016-12-01 11:50 +0100
Re: linux-next: manual merge of the edac-amd tree with the edac tree Mauro Carvalho Chehab <mchehab@osg.samsung.com> - 2016-12-01 13:10 +0100
Re: linux-next: manual merge of the edac-amd tree with the edac tree Borislav Petkov <bp@alien8.de> - 2016-12-01 19:20 +0100
csiph-web