Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3555950ybi; Sun, 2 Jun 2019 17:46:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqyh6ViWrbj6I0pVscrAWoik/loiSdH/G8KEFxtRPbl+oA7Pq/ZVelrEjANi5jipQBqTEYWK X-Received: by 2002:a17:902:a70a:: with SMTP id w10mr25424258plq.250.1559522790024; Sun, 02 Jun 2019 17:46:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559522790; cv=none; d=google.com; s=arc-20160816; b=jfk03vKSwUff4NGYEYz0yvT7kV+ueR6hrbUoSeYEL2gAOWAE82aN9dBbBZX/fC9do3 VagpX1/OzRab8BuUveGUrG9pprUijtWPRi56vJDu+tT3/q1ZfNYoU4MemqPlzuWOaQtI M6QCGWzgsyF4Ngy6y/dopPrxyN2RuX1UWOXSyQVHN2lqAIBjgXGmf+36+2A8UzYQlvdx Lyh1toD2e4mnt/Ewu277CjLTFE+fPL1kb+mK3gZ5vL+u5DvKFbc/UTS4+uThKO+mdh4d 1NaHlvusJ3e3PexMARw+NFR6NYl4gsLb3zi5XZ4xoUZ4/0v15ZctMjJmdXojN+AljP4q I7ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=5UsWZL2kfq7zvdRrL/f7NXweHhl97mjRDJ82V0mm5Zw=; b=D75qEOCeFfBOs9OOJAu+zib0BRzQrR2yA14MvjvBHQaU3Ce3c26Ye35luYyKJyDETN dykxPfN29hhUEeGsnN/6qmN2S2cTTSNHSnoQs0O3FskR3qqBleboI9SaRyjkRhNxn9+s MHoOtGzpAR/jF9y97UfyI1JETjIwY++4UH578co/Ox/6hhwgNKS9xmy6zmCUB6KSb+DE YZb5ZDL527CmrSuCJh6NSUY6B11ZehYEIYN9r+Qw2qqqs4lh6I3SEKjcV/dxAYsqKxvM BbSu9p2AQuN2t2bGXQlUOXQorTtzGHMj9wIjgkyRkuIMb5G8QlMBhywb3ZeZut/DNuHd dZcg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l5si15448391pgg.520.2019.06.02.17.45.45; Sun, 02 Jun 2019 17:46:30 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726663AbfFCAmj (ORCPT + 99 others); Sun, 2 Jun 2019 20:42:39 -0400 Received: from mga03.intel.com ([134.134.136.65]:65403 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726270AbfFCAmj (ORCPT ); Sun, 2 Jun 2019 20:42:39 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jun 2019 17:42:39 -0700 X-ExtLoop1: 1 Received: from allen-box.sh.intel.com (HELO [10.239.159.136]) ([10.239.159.136]) by orsmga004.jf.intel.com with ESMTP; 02 Jun 2019 17:42:35 -0700 Cc: baolu.lu@linux.intel.com, David Woodhouse , Joerg Roedel , kevin.tian@intel.com, ashok.raj@intel.com, dima@arista.com, tmurphy@arista.com, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, jacob.jun.pan@intel.com Subject: Re: [PATCH v4 10/15] iommu/vt-d: Probe DMA-capable ACPI name space devices To: Christoph Hellwig References: <20190525054136.27810-1-baolu.lu@linux.intel.com> <20190525054136.27810-11-baolu.lu@linux.intel.com> <20190529061626.GA26055@infradead.org> From: Lu Baolu Message-ID: <23d9d04c-c3fd-716e-dd66-eb5119aad4f9@linux.intel.com> Date: Mon, 3 Jun 2019 08:35:39 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190529061626.GA26055@infradead.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 5/29/19 2:16 PM, Christoph Hellwig wrote: > On Sat, May 25, 2019 at 01:41:31PM +0800, Lu Baolu wrote: >> Some platforms may support ACPI name-space enumerated devices >> that are capable of generating DMA requests. Platforms which >> support DMA remapping explicitly declares any such DMA-capable >> ACPI name-space devices in the platform through ACPI Name-space >> Device Declaration (ANDD) structure and enumerate them through >> the Device Scope of the appropriate remapping hardware unit. >> >> Signed-off-by: Lu Baolu > > Isn't this something that should be handled through the IOMMU API so > that it covers other IOMMU types as well? > > How does this scheme compare to the one implemented in > drivers/acpi/arm64/iort.c? > This part of code was added to be compatible with the past. Yes. I've ever thought about this. But these devices sit on the acpi bus together with other devices which are not DMA-capable. And on some platforms these devices exist on the pci bus as well. Best regards, Baolu