Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp430309img; Tue, 26 Feb 2019 02:37:48 -0800 (PST) X-Google-Smtp-Source: AHgI3IYRK/R2+Ilgl5K/Tc0uvtLr/ktvZa2p5/2ZJXmQ73aPea8N0LbGM2rFsGamQ4ZgzIRV0ET3 X-Received: by 2002:a62:1342:: with SMTP id b63mr3041924pfj.7.1551177468682; Tue, 26 Feb 2019 02:37:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551177468; cv=none; d=google.com; s=arc-20160816; b=qVxRK4nUu9ioUXec8Hr5nvEY7LP5qHPTJZrS/uOpKbhvu/RaXgxN1ah+VQ1x86uGYA /BcEvjQAIMYrFq8slvr3KGJUOANTv4naPJ3fx0iy3kn96NxB6DTO6xyPvB5ue/yv3nKN 7MiYDcAyJGXqbUNqZPRHEXpzjem4speqkG9ZKSu1hRT4liKmI9roBwJAlpzkOK13lp7f fEarf8/59Bbjl85OVaI2nCEntHzxyqEbsNqVWwxq6Why0e8rb1xPCrwOktLmgYMfUiht 2SoCMC9+9C6+qu2Srn6PORCj+dPhmXpuuoBwS5HoWrmUhF6zvHixBsS3cRPFJuAAn4Ft j5uw== 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; bh=s2NuXpvt09XCMVuBoiZaNhRfxCYphROAdzzJvJ2wLtU=; b=G0nvfAk72WkfZt3VY6OWF+7exoobloEhzV/bBBVViiQ4h5Zz4mU5caFnq+VMPwGJF+ qgC+iv9o5fR8NAIOAJZb+oCNuL/s0lJXH4gDtY2Q4cA2jgVfbByn06P5Fq5TbFZBD1XF +s3vjXoO1r6ujydhbKC/G3t/fRsEAeTt6yYeren3YnXOqCR9eJ+HI+i2almqWUj7BDSi epaINO8A0PP2i57qaSgiRQ9DdhBL6RUUtmqWtr2kbC00mkrnOfPSrKbakhH55WvhAA9d c3sB13ximMrubYE6i9S4gji64ENBDX7bpMG5EYtaaqRbXBLiZ5LiLN3Nghj3viaqXw+U +iwQ== 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=8bytes.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t74si12019202pgc.150.2019.02.26.02.37.33; Tue, 26 Feb 2019 02:37:48 -0800 (PST) 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=8bytes.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727367AbfBZKhM (ORCPT + 99 others); Tue, 26 Feb 2019 05:37:12 -0500 Received: from 8bytes.org ([81.169.241.247]:41400 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726267AbfBZKhL (ORCPT ); Tue, 26 Feb 2019 05:37:11 -0500 Received: by theia.8bytes.org (Postfix, from userid 1000) id AB90741A; Tue, 26 Feb 2019 11:37:09 +0100 (CET) Date: Tue, 26 Feb 2019 11:37:08 +0100 From: Joerg Roedel To: Lu Baolu Cc: David Woodhouse , Alex Williamson , Kirti Wankhede , ashok.raj@intel.com, sanjay.k.kumar@intel.com, jacob.jun.pan@intel.com, kevin.tian@intel.com, Jean-Philippe Brucker , yi.l.liu@intel.com, yi.y.sun@intel.com, peterx@redhat.com, tiwei.bie@intel.com, xin.zeng@intel.com, iommu@lists.linux-foundation.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 0/9] vfio/mdev: IOMMU aware mediated device Message-ID: <20190226103707.GG20740@8bytes.org> References: <20190222021927.13132-1-baolu.lu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190222021927.13132-1-baolu.lu@linux.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 22, 2019 at 10:19:18AM +0800, Lu Baolu wrote: > Lu Baolu (9): > iommu: Add APIs for multiple domains per device > iommu/vt-d: Move enable pasid out of CONFIG_INTEL_IOMMU_SVM > iommu/vt-d: Add per-device IOMMU feature ops entries > iommu/vt-d: Move common code out of iommu_attch_device() > iommu/vt-d: Aux-domain specific domain attach/detach > iommu/vt-d: Return ID associated with an auxiliary domain > vfio/mdev: Add iommu related member in mdev_device > vfio/type1: Add domain at(de)taching group helpers > vfio/type1: Handle different mdev isolation type This looks mostly good to me from an IOMMU point of view. I have some ideas for improving it further, but that can be left for later work. For example, I wonder if it makes sense to track the enabled/disabled state for features in core iommu code to safe the call-backs into the iommu-drivers for the is_enabled checks. When Alex Acks the vfio changes I am inclined to merge this for v5.1. Regards, Joerg