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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 3C869C432C3 for ; Wed, 20 Nov 2019 10:44:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 16AFD22429 for ; Wed, 20 Nov 2019 10:44:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728824AbfKTKom (ORCPT ); Wed, 20 Nov 2019 05:44:42 -0500 Received: from verein.lst.de ([213.95.11.211]:39432 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728814AbfKTKol (ORCPT ); Wed, 20 Nov 2019 05:44:41 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id 10C3B68AFE; Wed, 20 Nov 2019 11:44:38 +0100 (CET) Date: Wed, 20 Nov 2019 11:44:37 +0100 From: Christoph Hellwig To: Lu Baolu Cc: Christoph Hellwig , David Woodhouse , Joerg Roedel , Bjorn Helgaas , ashok.raj@intel.com, jacob.jun.pan@intel.com, alan.cox@intel.com, kevin.tian@intel.com, mika.westerberg@linux.intel.com, Ingo Molnar , Greg Kroah-Hartman , pengfei.xu@intel.com, Konrad Rzeszutek Wilk , Marek Szyprowski , Robin Murphy , Jonathan Corbet , Boris Ostrovsky , Juergen Gross , Stefano Stabellini , Steven Rostedt , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Jacob Pan Subject: Re: [PATCH v5 02/10] iommu/vt-d: Use per-device dma_ops Message-ID: <20191120104437.GB3800@lst.de> References: <20190725114348.GA30957@lst.de> <20191112071640.GA3343@lst.de> <0885617e-8390-6d18-987f-40d49f9f563e@linux.intel.com> <20191113070312.GA2735@lst.de> <20191113095353.GA5937@lst.de> <0ddc8aff-783a-97b9-f5cc-9e27990de278@linux.intel.com> <20191114081423.GA27407@lst.de> <6069128f-354c-e708-fa1d-d866dc186d57@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6069128f-354c-e708-fa1d-d866dc186d57@linux.intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 15, 2019 at 08:57:32AM +0800, Lu Baolu wrote: > Hi, > > On 11/14/19 4:14 PM, Christoph Hellwig wrote: >> On Thu, Nov 14, 2019 at 01:14:11PM +0800, Lu Baolu wrote: >>> Could you please educate me what dma_supported() is exactly for? Will >>> it always get called during boot? When will it be called? >> >> ->dma_supported is set when setting either the dma_mask or >> dma_coherent_mask. These days it serves too primary purposes: reject >> too small masks that can't be addressed, and provide any hooks needed >> in the driver based on the mask. > > Thanks! So ->dma_supported might not be called before driver maps buffer > and start DMA. Right? It is supposed to, yes.