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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6E390C38145 for ; Wed, 7 Sep 2022 12:02:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229449AbiIGMCF (ORCPT ); Wed, 7 Sep 2022 08:02:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59354 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229436AbiIGMCE (ORCPT ); Wed, 7 Sep 2022 08:02:04 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BC12785FF4 for ; Wed, 7 Sep 2022 05:02:03 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 5824967373; Wed, 7 Sep 2022 14:02:00 +0200 (CEST) Date: Wed, 7 Sep 2022 14:02:00 +0200 From: Christoph Hellwig To: Patrisious Haddad Cc: Sagi Grimberg , Christoph Hellwig , Israel Rukshin , Leon Romanovsky , Linux-nvme , linux-rdma@vger.kernel.org, Michael Guralnik , Maor Gottlieb , Max Gurtovoy Subject: Re: [PATCH rdma-next 4/4] nvme-rdma: add more error details when a QP moves to an error state Message-ID: <20220907120200.GA12104@lst.de> References: <20220907113800.22182-1-phaddad@nvidia.com> <20220907113800.22182-5-phaddad@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220907113800.22182-5-phaddad@nvidia.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Wed, Sep 07, 2022 at 02:38:00PM +0300, Patrisious Haddad wrote: > From: Israel Rukshin > > Add debug prints for fatal QP events that are helpful for finding the > root cause of the errors. The ib_get_qp_err_syndrome is called at > a work queue since the QP event callback is running on an > interrupt context that can't sleep. What an awkward interface. What prevents us from allowing ib_get_qp_err_syndrome to be called from arbitrary calling contexts, or even better just delivering the error directly as part of the event?