Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4674476ybi; Mon, 3 Jun 2019 15:18:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfmaSDuz8rCcj+AL+L0kFhRwE6kuvTjjZFk90hKRYB5K8+p/6s2dHf30ySL6ba2uFPzp1j X-Received: by 2002:a63:1516:: with SMTP id v22mr9570447pgl.204.1559600283682; Mon, 03 Jun 2019 15:18:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559600283; cv=none; d=google.com; s=arc-20160816; b=0tpEwrYEweaS+eCqaUWg3s71tgaVj3gO6osPzCdd5lIvwXOI1DB7nv6sk/74nxwbzz 2qhyjZr0ZNF3NJB6joXwg94VHBLZktfFEGSQKU+96jsR9JW06vbcvJDZh51zIg9f6QJN qmqM5LbGOP+Wxic7JChef42lkuS9xLCuPrfsvDAhUYaXAI4Vmr72qd4HPH4WR0ZbBU2T K8m4rr2zzSM4hhsiqOG3EPnAvpmMKC3KQzRAjyV/MbsS574NhjLhWguKPig4FCIcXKLz ZMEjUUcGU/QUoMoDkGqiZrBeU5R0jDz4AuEkgSyftzGEvBUCbSOsQjnmNRUhdwoIjrsp Sa8g== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=PaNfq+WOxAh6ooPAE5PN8hfqBkAXRBE+IcQZ/AXXnRM=; b=wPoCWHJoRZbvaO9bN8SEDqOy86j6uDRCjckaKdM4YfyISEoOkX26X8SzgKbs1GvqMJ 1dAMsAGMT29HXX+9v9WLpEux82DhMhhE4EgsCCuI+0ohof8YKodpVU3SD4bORlj7MeH7 EdrAYaRLn97bs/TN7uTh+Cz4RKGmxglaNe9vdBhEZBLi2SqezgUYztmb3Ihkvws7P62I v9VfV9v/FvIJhLu4BsoWKbhZ7NTvX2x5Vec3ehP0dVccIeiiHNLF8aJedSrKmI8N1eC9 0C7bcnCkiIfoojItN44DNdxak/0SBfHVGQut71WiX3putrKzD+BXwK/UVvT1rJw2fkqj EGkg== 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 e1si5578238pgj.171.2019.06.03.15.17.47; Mon, 03 Jun 2019 15:18:03 -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 S1726849AbfFCWQp (ORCPT + 99 others); Mon, 3 Jun 2019 18:16:45 -0400 Received: from mga09.intel.com ([134.134.136.24]:19879 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726163AbfFCWQo (ORCPT ); Mon, 3 Jun 2019 18:16:44 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jun 2019 14:56:47 -0700 X-ExtLoop1: 1 Received: from jacob-builder.jf.intel.com (HELO jacob-builder) ([10.7.199.155]) by orsmga008.jf.intel.com with ESMTP; 03 Jun 2019 14:56:47 -0700 Date: Mon, 3 Jun 2019 14:59:51 -0700 From: Jacob Pan To: Jean-Philippe Brucker Cc: joro@8bytes.org, alex.williamson@redhat.com, eric.auger@redhat.com, ashok.raj@intel.com, yi.l.liu@intel.com, robdclark@gmail.com, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, robin.murphy@arm.com, jacob.jun.pan@linux.intel.com Subject: Re: [PATCH v2 0/4] iommu: Add device fault reporting API Message-ID: <20190603145951.729600e6@jacob-builder> In-Reply-To: <20190603145749.46347-1-jean-philippe.brucker@arm.com> References: <20190603145749.46347-1-jean-philippe.brucker@arm.com> Organization: OTC X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 3 Jun 2019 15:57:45 +0100 Jean-Philippe Brucker wrote: > Allow device drivers and VFIO to get notified on IOMMU translation > fault, and handle recoverable faults (PCI PRI). Several series require > this API (Intel VT-d and Arm SMMUv3 nested support, as well as the > generic host SVA implementation). > > Changes since v1 [1]: > * Allocate iommu_param earlier, in iommu_probe_device(). > * Pass struct iommu_fault to fault handlers, instead of the > iommu_fault_event wrapper. > * Removed unused iommu_fault_event::iommu_private. > * Removed unnecessary iommu_page_response::addr. > * Added iommu_page_response::version, which would allow to introduce a > new incompatible iommu_page_response structure (as opposed to just > adding a flag + field). > > [1] [PATCH 0/4] iommu: Add device fault reporting API > https://lore.kernel.org/lkml/20190523180613.55049-1-jean-philippe.brucker@arm.com/ > > Jacob Pan (3): > driver core: Add per device iommu param > iommu: Introduce device fault data > iommu: Introduce device fault report API > > Jean-Philippe Brucker (1): > iommu: Add recoverable fault reporting > This interface meet the need for vt-d, just one more comment on 2/4. Do you want to add Co-developed-by you for the three patches from me? Thanks, Jacob > drivers/iommu/iommu.c | 236 > ++++++++++++++++++++++++++++++++++++- include/linux/device.h | > 3 + include/linux/iommu.h | 87 ++++++++++++++ > include/uapi/linux/iommu.h | 153 ++++++++++++++++++++++++ > 4 files changed, 476 insertions(+), 3 deletions(-) > create mode 100644 include/uapi/linux/iommu.h >