From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C8E91C433DB for ; Mon, 22 Feb 2021 12:56:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8076A64E76 for ; Mon, 22 Feb 2021 12:56:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230520AbhBVM4m (ORCPT ); Mon, 22 Feb 2021 07:56:42 -0500 Received: from mail.kernel.org ([198.145.29.99]:49206 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231255AbhBVMXs (ORCPT ); Mon, 22 Feb 2021 07:23:48 -0500 Received: from disco-boy.misterjones.org (disco-boy.misterjones.org [51.254.78.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 85ED564E61; Mon, 22 Feb 2021 12:23:07 +0000 (UTC) Received: from 78.163-31-62.static.virginmediabusiness.co.uk ([62.31.163.78] helo=why.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1lEAEz-00FJdN-6a; Mon, 22 Feb 2021 12:23:05 +0000 Date: Mon, 22 Feb 2021 12:23:04 +0000 Message-ID: <87ft1o1ec7.wl-maz@kernel.org> From: Marc Zyngier To: Mark Rutland Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, james.morse@arm.com, marcan@marcan.st, tglx@linutronix.de, will@kernel.org Subject: Re: [PATCH 5/8] arm64: irq: add a default handle_irq panic function In-Reply-To: <20210222120614.GC70951@C02TD0UTHF1T.local> References: <20210219113904.41736-1-mark.rutland@arm.com> <20210219113904.41736-6-mark.rutland@arm.com> <20210222095913.GA70951@C02TD0UTHF1T.local> <1d2c27d72b9b2cbdb83d25165a20559a@kernel.org> <20210222112544.GB70951@C02TD0UTHF1T.local> <2e6a9659eabcccb355318ff7214c8d1f@kernel.org> <20210222120614.GC70951@C02TD0UTHF1T.local> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 62.31.163.78 X-SA-Exim-Rcpt-To: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, james.morse@arm.com, marcan@marcan.st, tglx@linutronix.de, will@kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 22 Feb 2021 12:06:14 +0000, Mark Rutland wrote: > > On Mon, Feb 22, 2021 at 11:43:13AM +0000, Marc Zyngier wrote: [...] > > As I said, it's not a big deal. I doubt that we'll see default_handle_irq() > > exploding in practice. But the real nit here is the difference of treatment > > between IRQ and FIQ. *IF* we ever get a system that only signals its > > interrupt as FIQ (and I don't see why we'd forbid that), then we would > > That's a fair point. > > For consistency, we could remove the init_IRQ() panic() and instead log > the registered handlers, e.g. > > | pr_info("Root IRQ handler is %ps\n", handle_arch_irq); > | pr_info("Root FIQ handler is %ps\n", handle_arch_fiq); > > ... or do that inside the set_handle_{irq,fiq}() functions. That way the > messages (or absence thereof) would be sufficient to diagnose the lack > of a root IRQ/FIQ handler when IRQ/FIQ happens to be quiescent. > > Does that sound any better? Yup, I quite like the second variant (using set_handle_{irq,fiq}()). Thanks, M. -- Without deviation from the norm, progress is not possible. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D461C433DB for ; Mon, 22 Feb 2021 12:24:49 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DD4F964E44 for ; Mon, 22 Feb 2021 12:24:48 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DD4F964E44 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To:Subject:To:From: Message-ID:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=qnXzWyJeWQl4tWHTe6HO0qkdus2n1kNg3YIZcClWeyI=; b=XY3OmcPiJ+yHR4ryVw9j2ktuY tZlh+2KxUu0IHBhTmz8ehN746rVvkWNJeeoWngwMKzIuxb7sv3b0byZL69fF4btK0Ty7ClmtcDPVw D9bPEyK0ng5kbdAj2E9+jBz3sjKtPT4fDotGLfvq+RJ1EgIoNNIQBj37CDKTxbANTSsreOJm46qGm ro6QBeqxgoACzsYIk9tMNG2GLYgidGparrz3PhP0dBxf1SUaIGcToh6Uo/ZeD6Fhv9Ilw6VMygRbo kJY8LjtMCZ8llUqW/tbxY4whTl/xsJLrMePLSmrFu91nMFDQWTMDUDL/IJ5WuQrV/CGGK3edfqYfS DQIYRRJnw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lEAF4-0002oD-8X; Mon, 22 Feb 2021 12:23:10 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lEAF2-0002ne-Fe for linux-arm-kernel@lists.infradead.org; Mon, 22 Feb 2021 12:23:09 +0000 Received: from disco-boy.misterjones.org (disco-boy.misterjones.org [51.254.78.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 85ED564E61; Mon, 22 Feb 2021 12:23:07 +0000 (UTC) Received: from 78.163-31-62.static.virginmediabusiness.co.uk ([62.31.163.78] helo=why.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1lEAEz-00FJdN-6a; Mon, 22 Feb 2021 12:23:05 +0000 Date: Mon, 22 Feb 2021 12:23:04 +0000 Message-ID: <87ft1o1ec7.wl-maz@kernel.org> From: Marc Zyngier To: Mark Rutland Subject: Re: [PATCH 5/8] arm64: irq: add a default handle_irq panic function In-Reply-To: <20210222120614.GC70951@C02TD0UTHF1T.local> References: <20210219113904.41736-1-mark.rutland@arm.com> <20210219113904.41736-6-mark.rutland@arm.com> <20210222095913.GA70951@C02TD0UTHF1T.local> <1d2c27d72b9b2cbdb83d25165a20559a@kernel.org> <20210222112544.GB70951@C02TD0UTHF1T.local> <2e6a9659eabcccb355318ff7214c8d1f@kernel.org> <20210222120614.GC70951@C02TD0UTHF1T.local> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") X-SA-Exim-Connect-IP: 62.31.163.78 X-SA-Exim-Rcpt-To: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, james.morse@arm.com, marcan@marcan.st, tglx@linutronix.de, will@kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210222_072308_610974_EF80E68B X-CRM114-Status: GOOD ( 19.12 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: catalin.marinas@arm.com, marcan@marcan.st, linux-kernel@vger.kernel.org, james.morse@arm.com, tglx@linutronix.de, will@kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 22 Feb 2021 12:06:14 +0000, Mark Rutland wrote: > > On Mon, Feb 22, 2021 at 11:43:13AM +0000, Marc Zyngier wrote: [...] > > As I said, it's not a big deal. I doubt that we'll see default_handle_irq() > > exploding in practice. But the real nit here is the difference of treatment > > between IRQ and FIQ. *IF* we ever get a system that only signals its > > interrupt as FIQ (and I don't see why we'd forbid that), then we would > > That's a fair point. > > For consistency, we could remove the init_IRQ() panic() and instead log > the registered handlers, e.g. > > | pr_info("Root IRQ handler is %ps\n", handle_arch_irq); > | pr_info("Root FIQ handler is %ps\n", handle_arch_fiq); > > ... or do that inside the set_handle_{irq,fiq}() functions. That way the > messages (or absence thereof) would be sufficient to diagnose the lack > of a root IRQ/FIQ handler when IRQ/FIQ happens to be quiescent. > > Does that sound any better? Yup, I quite like the second variant (using set_handle_{irq,fiq}()). Thanks, M. -- Without deviation from the norm, progress is not possible. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel