Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753151AbdCXRgl (ORCPT ); Fri, 24 Mar 2017 13:36:41 -0400 Received: from foss.arm.com ([217.140.101.70]:45018 "EHLO foss.arm.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753054AbdCXRge (ORCPT ); Fri, 24 Mar 2017 13:36:34 -0400 Date: Fri, 24 Mar 2017 17:35:15 +0000 From: Mark Rutland To: Doug Berger Cc: catalin.marinas@arm.com, robh+dt@kernel.org, will.deacon@arm.com, computersforpeace@gmail.com, gregory.0xf0@gmail.com, f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com, wangkefeng.wang@huawei.com, james.morse@arm.com, vladimir.murzin@arm.com, panand@redhat.com, andre.przywara@arm.com, cmetcalf@mellanox.com, mingo@kernel.org, sandeepa.s.prabhu@gmail.com, shijie.huang@arm.com, linus.walleij@linaro.org, treding@nvidia.com, jonathanh@nvidia.com, olof@lixom.net, mirza.krak@gmail.com, suzuki.poulose@arm.com, bgolaszewski@baylibre.com, horms+renesas@verge.net.au, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 3/9] arm64: mm: install SError abort handler Message-ID: <20170324173515.GB10746@leverpostej> References: <20170324144632.5896-1-opendmb@gmail.com> <20170324144632.5896-4-opendmb@gmail.com> <20170324151654.GD29588@leverpostej> <58D54DE8.9020707@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <58D54DE8.9020707@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 717 Lines: 16 On Fri, Mar 24, 2017 at 09:48:40AM -0700, Doug Berger wrote: > On 03/24/2017 08:16 AM, Mark Rutland wrote: > >On Fri, Mar 24, 2017 at 07:46:26AM -0700, Doug Berger wrote: > If you would consider an alternative implementation where we scrap > the SError handler (i.e. maintain the ugliness in our downstream > kernel) in favor of a more gentle user mode crash on SError that > allows the kernel the opportunity to service the interrupt for > diagnostic purposes I could try to repackage that. If this is just for diagnostic purposes, I believe you can register a panic notifier, which can then read from the bus. The panic will occur, but you'll have the opportunity to log some information to dmesg. Thanks, Mark.