From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: linux-next: manual merge of the edac-amd tree with the edac tree Date: Thu, 1 Dec 2016 19:15:01 +0100 Message-ID: <20161201181501.eynw6ucx6cdsg6hl@pd.tnic> References: <20161128143726.7fda1849@canb.auug.org.au> <20161128082734.bdl4dhothemm7ja5@pd.tnic> <20161130085013.4798b4a7@vento.lan> <20161201104846.kjvuy5tj475oxzke@pd.tnic> <20161201100617.511d8aae@vento.lan> <20161201160203.hhm6w3iyrnvcukzu@yaz-fedora.dyhomenet> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20161201160203.hhm6w3iyrnvcukzu@yaz-fedora.dyhomenet> Sender: linux-kernel-owner@vger.kernel.org To: Yazen Ghannam Cc: Mauro Carvalho Chehab , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-next.vger.kernel.org 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.