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.2 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 00856C47094 for ; Thu, 10 Jun 2021 08:07:11 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id CA31A613CB for ; Thu, 10 Jun 2021 08:07:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CA31A613CB 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-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org 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:MIME-Version:References:In-Reply-To: Subject:Cc: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=CSClmltUfDNodnzYWpWYfzQMvRv6ghwa7m/THhIuPtA=; b=ORAQ7J+QB38XK2 28KfZmyMoJf6IvpkD7nvZzZ4AFji4NT8wxquKdh7gHBXBqBrBAFKgVp6NWrstchDIHTJFkHPvrmlO V6ZJjZGQi/W1ZIQ/KvvV0KnO63ZIDLkGzOysCkb0e45+vlqQeIsKtM+Mls1b8U/081Ik4wnztLa1F 1X30T36LSy7t4G640TniZqleLqKCvQboqsiZRLR5X9/EFH+MkFa++vinDcjLtLJTnn340v5VHA5PW Ih0Mf/lhbYsHrbXJf9zGb4nEh2cXmNf/0db2wlQduDHm5KrywrwrKQXu6j7ZnUPiRUflPBHLjDasr bRVbZ+lM9/owKJipKI/A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1lrFiN-00HOcr-L9; Thu, 10 Jun 2021 08:06:59 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1lrFho-00HOLq-6w for linux-nvme@lists.infradead.org; Thu, 10 Jun 2021 08:06:25 +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 E7E57613ED; Thu, 10 Jun 2021 08:06:22 +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.2) (envelope-from ) id 1lrFhk-006gKO-U5; Thu, 10 Jun 2021 09:06:21 +0100 Date: Thu, 10 Jun 2021 09:06:19 +0100 Message-ID: <87k0n2qh38.wl-maz@kernel.org> From: Marc Zyngier To: Heiner Kallweit Cc: Thomas Gleixner , Linux Kernel Mailing List , "linux-nvme@lists.infradead.org" , Christoph Hellwig Subject: Re: linux-next: NVME using PCI legacy interrupts only In-Reply-To: <52371274-20bc-a150-a3ed-ba3e1305ad3e@gmail.com> References: <52371274-20bc-a150-a3ed-ba3e1305ad3e@gmail.com> 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: hkallweit1@gmail.com, tglx@linutronix.de, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, hch@lst.de 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-20210610_010624_303490_90138E0F X-CRM114-Status: GOOD ( 22.13 ) X-BeenThere: linux-nvme@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-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org On Wed, 09 Jun 2021 19:43:57 +0100, Heiner Kallweit wrote: > > I found that on linux-next from June 8th my nvme disk is using legacy > interrupts only. Some debugging lead me to irq_find_mapping() in > msi_domain_alloc() returning -EEXIST. > > The nvme core first allocates a MSI-X interrupt for setup purposes > and later frees it and allocates the final number of MSI-X interrupts. > > The following experimental change brought back the MSI-X interrupts. > This makes me think that somehow freeing a MSI-X interrupt doesn't > free it completely. I didn't see this behavior a few days ago, > therefore I think it's related to the recent changes to > irqdomain/genirq. > > Didn't do a bisect yet, maybe you have an idea already. Yeah, recent changes in the irqdomain subsystem seem to have uncovered a long standing issue where we are leaving dangling references in some domains.... I've now dropped the branch from -next while I figure it out. Thanks, M. -- Without deviation from the norm, progress is not possible. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme