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 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A11F2C433EF for ; Fri, 25 Feb 2022 11:20:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) id 6AC75C340F1; Fri, 25 Feb 2022 11:20:52 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.kernel.org (Postfix) with ESMTPS id E0324C340E7; Fri, 25 Feb 2022 11:20:50 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 smtp.kernel.org E0324C340E7 Authentication-Results: smtp.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: smtp.kernel.org; spf=none smtp.mailfrom=arndb.de Received: from mail-wr1-f51.google.com ([209.85.221.51]) by mrelayeu.kundenserver.de (mreue011 [213.165.67.97]) with ESMTPSA (Nemesis) id 1M433w-1nNYeW2SJ6-0000Jl; Fri, 25 Feb 2022 12:20:48 +0100 Received: by mail-wr1-f51.google.com with SMTP id s13so3957618wrb.6; Fri, 25 Feb 2022 03:20:48 -0800 (PST) X-Gm-Message-State: AOAM531oyscCvz1ycjugo5JxISk+VZn+77hiLVs2il9OzuoGurrt5+EZ rKLncEb5LSQ4BGPG5xWBtO7ESnbRMfSrzk61nII= X-Google-Smtp-Source: ABdhPJz6Sv6Vhh/XIVu7MkCYDgoQWagiA2O2Q0TopRL5dPjv2UrfovxrCvY3lRFoeExdFoiVYQQeG3layaHVGTRZZ2Y= X-Received: by 2002:adf:a446:0:b0:1ed:c41b:cf13 with SMTP id e6-20020adfa446000000b001edc41bcf13mr6102767wra.407.1645788047928; Fri, 25 Feb 2022 03:20:47 -0800 (PST) MIME-Version: 1.0 References: <20220218092010.1327309-1-hasegawa-hitomi@fujitsu.com> In-Reply-To: From: Arnd Bergmann Date: Fri, 25 Feb 2022 12:20:31 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] soc: fujitsu: Add A64FX diagnostic interrupt driver To: "hasegawa-hitomi@fujitsu.com" List-Id: Cc: "gregkh@linuxfoundation.org" , "jirislaby@kernel.org" , Arnd Bergmann , Linux ARM , SoC Team , Olof Johansson , Catalin Marinas , Will Deacon , Sumit Garg Content-Type: text/plain; charset="UTF-8" X-Provags-ID: V03:K1:Hugpxyf1qMuILGYOS5E6hGf78MoLveP2eTaIqHVIugYw1Y+wuhL c8StmbOHPq4zGvaQng8IBgvNFNeg+e8pkcABUcfZNVK8f1sP4r8CmjsSQwW0WIrhg62kAh8 RpXADnExoWY/PECqiOr9g0yICDOKizHDTqds39j9dVb4fe1kCxSjyhWgDiklKDU484md0SH GZ/eFan5CeiiH3Wl9atBA== X-UI-Out-Filterresults: notjunk:1;V03:K0:rpf24B1M0dI=:TFc9DGtCG8FrFO3gC/BKZ1 8n2iU8cuV0ZL8TsRkD3yWZ/rdn7JaDoDIlwHRixkkMmpWdP3AuEGNb2Wt+qCgORwpH+C3CDSf d+kAGUEQqF36PO9ofJGZCZm7zCtnPC7HGDUr9pHOxfaUoIrpwH8/HtO9K+SSAmU+KPqc4hSzL hddQV8AOfwhSECef4//dj8pKJAnTyQMN5IkPOdnJhy4bQBLBayUHtpXvpssYpyzieZyV4a1PJ 3nDr6tPqvWZ+Q/dUoTm2ZxJ4Lkfg5TgrsQhzT/qUr33vgXwEbY2S6RRFX0gqxkC7gJv/JlxeW auLrAYQEcfAzRxZgxnEMYIcx9tIlV8ejIIfM1qKXSUE0G47RazLKaNuOdqYX8B9lYcJiRtLdQ Ks4mb5rWyHgsWCoDNk7Z9Kfz0i64ZnpMY0KnufTKIuyodUdy5O2VmFptN6EkJ0raarsjwKaAd 3gB1ozJW3SEyh2Izzgs195/tcWhMnJ2ARnOogIS3A7KBK+Vnc6/NN41mvHc7F5LRpMUzoXZ9c eBuVIoL6WKCQaW/xNdrNb84wSPdXX97933T2K9R7fDLtwXa92MPHLV65onCQBzMKDFjB5gDiN bikXFGJM0MrkpjgVfrBAP5splF+WQt80+p4oND3n4TVsATl6nHphpQAYWxkgu3Qs+Hy9G+weh JyWPWhLzFYTSC+JVw3wLwvklVLETvTEyLJXdu2WgmWL/1SJ3/oxd+QGcc/5DnNNjfPsYRP4xG WVfNYDBw86DcINLpHKxxqOMD+XB7Z8Gx0q19x22eQtZ79RkmA3qzaP4Kh5+bF+h1+pI2sSXih VGDmKcVjLioJKBVKfyfDEPDdjQ2St5NBg/Epx8M159W1x10m0Y= On Fri, Feb 25, 2022 at 11:35 AM hasegawa-hitomi@fujitsu.com wrote: > > Hi Greg and Jiri, > > I'm trying to implement a feature for A64FX that will panic when > a diagnostic interrupt is received. > Arnd suggested that handle_sysrq() should be used > but I'm wonderingif it's ok to call it in NMI. > Would you please let me know if we can call handle_sysrq() in NMI? I see some work from Sumit Garg to make it possible, but this was never merged, so presumably it is not safe: https://lore.kernel.org/linux-arm-kernel/CAFA6WYOWHgmYYt=KGXDh2hKiuy_rQbJfi279ev0+s-Qh7L21kA@mail.gmail.com/t/#m2b5006f08581448020eb24566927a104d0b95c44 Sumit has worked on some related areas as well, and may have additional ideas for you. Arnd 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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 452B3C433F5 for ; Fri, 25 Feb 2022 11:22:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=rhFrZRMmE8Ac0atauObYo5cLq/vsuD+Gy+/s8U5pSjM=; b=DnT7qDxSSrCZyH +vd3RNYhp4m3fRe80whG2+y7pwnoWoK5QP2wIQyS87RWC0+B8QkXHvQ57iH2Nw9/+zomMlzZjdapj oqgb/VEUaqXa7VRRB9BnoBBsg8u/1O3Ig8aYXtTyhaTpzitYt9Z5vM71TX/tdMn3VkVPULhmi6hIF NnUYmsDv4AKMmp44KaDkKVae4M3YbkSTtFSlRRTvG9OYu6huy1XmAbwkXPVhtUtQJ+Y9A2K/adaX5 uLetj5K4w4vC+QjaVHNP17u5Mtatn2iMfs5o2pk9H0mAjIrXQq7AD8H/C8FHvIuuK/t8uwUF7B1Cw hv/HAZoO+zou5Xt+yIHw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nNYed-004f5P-Dd; Fri, 25 Feb 2022 11:20:55 +0000 Received: from mout.kundenserver.de ([212.227.126.130]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nNYeY-004f53-Vm for linux-arm-kernel@lists.infradead.org; Fri, 25 Feb 2022 11:20:52 +0000 Received: from mail-wr1-f48.google.com ([209.85.221.48]) by mrelayeu.kundenserver.de (mreue012 [213.165.67.97]) with ESMTPSA (Nemesis) id 1MP2zs-1nZhka2oqC-00PKiw for ; Fri, 25 Feb 2022 12:20:48 +0100 Received: by mail-wr1-f48.google.com with SMTP id n14so3949189wrq.7 for ; Fri, 25 Feb 2022 03:20:48 -0800 (PST) X-Gm-Message-State: AOAM533TTCX1c/cszB66gERdbYcDkoqntUBraw5qlPacV4gwSwHvR/qE V4ZeuF2v6abAHX/IpjlWjecEDfwXHVqXNG6hdzY= X-Google-Smtp-Source: ABdhPJz6Sv6Vhh/XIVu7MkCYDgoQWagiA2O2Q0TopRL5dPjv2UrfovxrCvY3lRFoeExdFoiVYQQeG3layaHVGTRZZ2Y= X-Received: by 2002:adf:a446:0:b0:1ed:c41b:cf13 with SMTP id e6-20020adfa446000000b001edc41bcf13mr6102767wra.407.1645788047928; Fri, 25 Feb 2022 03:20:47 -0800 (PST) MIME-Version: 1.0 References: <20220218092010.1327309-1-hasegawa-hitomi@fujitsu.com> In-Reply-To: From: Arnd Bergmann Date: Fri, 25 Feb 2022 12:20:31 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] soc: fujitsu: Add A64FX diagnostic interrupt driver To: "hasegawa-hitomi@fujitsu.com" Cc: "gregkh@linuxfoundation.org" , "jirislaby@kernel.org" , Arnd Bergmann , Linux ARM , SoC Team , Olof Johansson , Catalin Marinas , Will Deacon , Sumit Garg X-Provags-ID: V03:K1:cRew1iFIRjZM3BIabMcrzMCxia96cRIKJu5s4Ce5GyZVj9lfiIc Ayl0JTuPx7byHIVHYqT/NLFvVDY98o6xJ57KziYaf5xhRfi0Cefn03fG0093y4iAnjr6ekL fjZxDZenAQZ8dHxKx9CEUjCumgefkx3s2DAXTtRgn7XDyIYVCuLC3pNCWO5GSFJnURwK21P BChLQ8R0AbYfnfyX3gT7w== X-UI-Out-Filterresults: notjunk:1;V03:K0:oeTpKHbLwRs=:nQxFHgrG2/rp0tymr4miB/ tYCSHVQcvAG9SVfN1vHgoROBl4iPycXTKQRZgRWSTz5IesR4NTYQgjSQJPI5/smg9m4778TEN mB3oNRR5hDymIwL9ZrQ92D3ellyJBWyHVWhstgesHJGoMCnRM6JBiW9Y7fbqAiQ9F+jKJ8flZ 7CSbIO5jXgHBjzgMSBbeaRoXTvvCGzFq1bdAmtt6PDLq9K/3LLH8o5/Azv5gSpVxhIU3xwO+E CF81y/tfk2Va0lMjUxB5x3NAsmoAjQfqGqb4OvkHdGdSPU7RAR65W+6DeN01bVELzIlzt4EQf /pu9Xh0W8dRfAiYKQLR7bVtmN8qRdYFtzznKnrXx+78xhnJxjeAy7ZGckDr7c4qnGZvV8K0kO /Fd8SpUIkp9yBXA66RTIp9fUW8zs7tLVLmyFUsxHwKbTgJq8NgqfIqcQe+1rKw81hNcWuAYXK MR2UcjuB1tZv3cg8CIT/Wn2Czae9hSuPQzHNMUqt4vihLd781j7EoQtLIzkxTSjxU1UgX5Txc vKBrtmD3E3no5+ue3yvCw0sOfVyBRE8tiR3KCgLNu/fj13eLoN/bFKdbyijM45IBfyGYDYcL3 zzWlEbzJ3mrhipMcl3WaUPa9JA0l7mhrnJHBZ3nwFEq2y6PDTp1pwng4QSF99S44ltjhbTtlU 7OGGIfZf+gn2nsJRnDIMtIlTUtQgA39unNFD9lNxWeq0Q+XfqT6m/C+Hm2JuIvjNNSTs= X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220225_032051_352435_CB9BDEF6 X-CRM114-Status: GOOD ( 14.45 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Fri, Feb 25, 2022 at 11:35 AM hasegawa-hitomi@fujitsu.com wrote: > > Hi Greg and Jiri, > > I'm trying to implement a feature for A64FX that will panic when > a diagnostic interrupt is received. > Arnd suggested that handle_sysrq() should be used > but I'm wonderingif it's ok to call it in NMI. > Would you please let me know if we can call handle_sysrq() in NMI? I see some work from Sumit Garg to make it possible, but this was never merged, so presumably it is not safe: https://lore.kernel.org/linux-arm-kernel/CAFA6WYOWHgmYYt=KGXDh2hKiuy_rQbJfi279ev0+s-Qh7L21kA@mail.gmail.com/t/#m2b5006f08581448020eb24566927a104d0b95c44 Sumit has worked on some related areas as well, and may have additional ideas for you. Arnd _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel