From: Joerg Roedel Subject: Re: [PATCH] iommu/amd: Allow non-ATS devices in IOMMUv2 domains Date: Thu, 30 Jul 2015 13:24:25 +0200 Message-ID: <20150730112425.GR27614@suse.de> References: <1438250724-4443-1-git-send-email-joro@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Oded Gabbay Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, "Linux-Kernel@Vger. Kernel. Org" List-Id: iommu@lists.linux-foundation.org Hi Oded, On Thu, Jul 30, 2015 at 01:08:46PM +0300, Oded Gabbay wrote: > Why amdkfd's devices are considered a non-IOMMUv2 capable devices ? > After all, they contain the IOMMUv2 H/W and use it constantly for HSA. With 4.2 the AMD IOMMU driver relies on iommu groups from the iommu core code. With that, all functions of a multi-function device will be in one group (and have to be in one domain). This means that the audio device which comes with every HSA GPU is in the same group, and this device lacks the IOMMUv2 features. Joerg