Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4838811imm; Tue, 31 Jul 2018 00:37:06 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfWFQrPC3II65Lg+F3mIyRBeeulHcEWQ4DHcv1GEFF8w6LhqNMUFpymXFtvQjsNg20+ZuR3 X-Received: by 2002:a17:902:a5:: with SMTP id a34-v6mr19750125pla.60.1533022626369; Tue, 31 Jul 2018 00:37:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533022626; cv=none; d=google.com; s=arc-20160816; b=ud+QI9u2qxkfnIQ8NBOlzLbawqFd3On/cjswVogFp9XAp/WbU19UpnZ3wWj4LL7iOi YZHITD+AghkPt8B9QPAz1AdFrmvkl0eC6Xu6ubx4jwjgz3hHMVgbzKUK/8XFG5LxQRQ2 PgzsNjypcGZ44wXYPtUHnqKB5+xtMUq1wD9rQCQHChRTdqEDZgZurU8XRr2wA2s89ZK1 y0ZqNqTXqVlaCaXdc2ncUAGoFBybiGO+eNvNtLPt7DRxsy7CGcouT2tSqbXm7WvM5Jke c/5UH7xuhCKqn49WseRf3flHrGKEYmVLCVglWNs6ilzFRs0B64FDmFUsstf+45jC4Feu zpFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=7cB24LETq9AsjUZ3bXY9U9syCh1eqRgB9kMnFfgsUJE=; b=Xnjepgwjixzhf5HYo0WirVHD3Hqo2/lEdcFDNV3dZh8B7Nf+JUEyc8KazowbD5YiId MvsMiaIOHw/GhFOFb8LR2/75C+Y4a5qmsrG7OP3N06w/57MU+cLL5dXtkyMEHmpixUkD ReJnZWPXaOLrSKoR9nmnODl0KHUi8bqe9s+5caf/yUf28nphF0vSAhTfWGNb1uaj3zes v7vz/qzj7c6v5TMBFCnx3EGO/5k24BQyywVOxccWdXfJY+2DkeJXdP4m3IiwqfkfiaVh BgOCWlKY8YwPv6W6i7+lPgFp0T4E8YRxWheXekU9uD5P2p4ktcfmvoOUrm53xDuTXO0c rkRA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j2-v6si13669380pgs.475.2018.07.31.00.36.52; Tue, 31 Jul 2018 00:37:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729175AbeGaJPE (ORCPT + 99 others); Tue, 31 Jul 2018 05:15:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:34228 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727015AbeGaJPD (ORCPT ); Tue, 31 Jul 2018 05:15:03 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 44F43AE29; Tue, 31 Jul 2018 07:36:03 +0000 (UTC) Date: Tue, 31 Jul 2018 09:36:02 +0200 From: Joerg Roedel To: Bjorn Helgaas Cc: Christoph Hellwig , linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org, x86@kernel.org, linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] PCI: call dma_debug_add_bus for pci_bus_type in common code Message-ID: <20180731073602.jbbcr4twd2gnkfoc@suse.de> References: <20180730073842.16092-1-hch@lst.de> <20180730211713.GA45322@bhelgaas-glaptop.roam.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180730211713.GA45322@bhelgaas-glaptop.roam.corp.google.com> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 30, 2018 at 04:17:13PM -0500, Bjorn Helgaas wrote: > [+cc Joerg] > > On Mon, Jul 30, 2018 at 09:38:42AM +0200, Christoph Hellwig wrote: > > There is nothing arch specific about PCI or dma-debug, so move this > > call to common code just after registering the bus type. > > I assume that previously, even if the user set CONFIG_DMA_API_DEBUG=y > we only got PCI DMA debug on powerpc, sh, and x86. And after this > patch, we'll get PCI DMA debug on *all* arches? > > If that's true, I'll add a comment to that effect to the commitlog > since that new functionality might be of interest to other arches. There should be implicit support for dma-debug for all arches that use the generic dma_ops code. The dma_debug_add_bus() function just adds the reporting of pending dma-allocations on driver-unload for a device. Regards, Joerg