Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <d7b70de6-cd7f-3724-3449-5b838a478277@quicinc.com>
Date:   Wed, 9 Nov 2022 21:50:35 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.13.1
Content-Language: en-US
From:   Mukesh Ojha <quic_mojha@quicinc.com>
To:     <maz@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
        <catalin.marinas@arm.com>, <will@kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>
CC:     lkml <linux-kernel@vger.kernel.org>
Subject: Query on handling some special Group0 interrupt in Linux
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi,

I was working on a use case where both el2/el3 are implemented and we 
have a watchdog interrupt (SPI), which is used for detecting software 
hangs and cause device reset; If that interrupt's current cpu affinity 
is on a core, where interrupts are disabled, we won't be able to serve 
it or if this interrupt comes on a core which has interrupt enabled, 
calling panic() or with smp_send_stop(), we would not be able
to know the call stack of the other cores which is running with 
interrupt disabled.

I was thinking of configuring both a watchdog irq(SPI) and IPI_STOP 
(SGI) or any reserve IPI as an FIQ. And from the watchdog irq handler,
I was thinking of calling panic() which eventually sends IPI_STOP(SGI 
FIQ) to all the cores. And with this we will able to dump all the core 
call stack.

I am able to achieve this but wanted to know if this is acceptable to 
the community to support/allow such use cases like above and enable 
group0 interrupt from GIC for some special use cases.

-Mukesh