From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH v5 02/12] iommu/vt-d: Manage scalalble mode PASID tables Date: Wed, 5 Dec 2018 16:47:10 +0100 Message-ID: <20181205154710.GB16835@8bytes.org> References: <20181128035449.10226-1-baolu.lu@linux.intel.com> <20181128035449.10226-3-baolu.lu@linux.intel.com> <20181203134411.lejlkbnagxml54ro@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "Liu, Yi L" Cc: Lu Baolu , David Woodhouse , "Raj, Ashok" , "Kumar, Sanjay K" , "Pan, Jacob jun" , "Tian, Kevin" , "Sun, Yi Y" , "peterx@redhat.com" , Jean-Philippe Brucker , "iommu@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , Jacob Pan List-Id: iommu@lists.linux-foundation.org On Mon, Dec 03, 2018 at 05:23:40PM +0000, Liu, Yi L wrote: > So for a device without PASID support, we need to at least to have a PASID > entry so that its DMA request (without pasid) can be translated. Thus a PASID > table is needed for such devices. That makes sense, thanks for the explanation. Joerg