Received: by 10.223.185.116 with SMTP id b49csp402040wrg; Fri, 16 Feb 2018 00:36:06 -0800 (PST) X-Google-Smtp-Source: AH8x227ENFJfTLt5+DYjbT1nRNU/QLiebaZdfCplXNP7YvJ4MYdLduOIt4JOi0Pg6ySe2ET7hCoa X-Received: by 10.98.149.69 with SMTP id p66mr5331462pfd.183.1518770166567; Fri, 16 Feb 2018 00:36:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518770166; cv=none; d=google.com; s=arc-20160816; b=Hmnsd50sdJR2Wq0Iqg6OxpWeMfaoRCJ94m53moGlQireRMYx0XtTF/2tAalkrCQvHP LOEnqX3SgAL86AX+cXe5Y9/1DogsQuy/G/XjQnfe5XyM9n0SHHigc2RCGG5cCCX28fxS cUDLihUCUE64Pxge7lAnRh3tkMY/XO2zDnlRavEIJpsMB8QE+qEX4AZMl9Q36xIPCthe sJu6RmB9u6AlHWIjBZ3kQR7KPqLVGLYiapC5htll0juZ8r7+vXQUayjwp50R34Lhy7ZG V6LeL+i1GbERAniD+SbjsPHR9l3kIRptmbUhP/xocaHuCv5ZYWRG8SHZNupey/qeKm1S 530w== 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:arc-authentication-results; bh=38PabjgcrBEyhkhaqBXKtUmswkUOu786T918TPOHdTc=; b=QgZGfF+uUmYP3sh16ShZ+zHtn9t/E+6Edhu0fy2sF9iVVtzVY4AVDqU8btnjuqnagg 6s1TkZT72wRMEp+apRzHA8e7lhNIkJOZn1biseDHirNnmjTI1A7gehLGmH3hO4X4ab5N L7oa59xFgnEcCuvBvN1Hu5BUERv0x82bv/7raWHugiz4CU4JU7DeXGLcmwFMOaN4n3Ep iFuR4QD+DrEXhP8tcC6An1X+KQzvE78+EBcZqI3uKU1hKNzzrNPShka3Wp6AT1zOydDt nmWvE9F4/QbPLwpdNmwtnUglsUwoB1JOZaYN8ODjK4tQ/VEHD/1vp6IZ/Z4ESkWgtM+j qG5A== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q9si1107855pgn.210.2018.02.16.00.35.51; Fri, 16 Feb 2018 00:36:06 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1426141AbeBOQho (ORCPT + 99 others); Thu, 15 Feb 2018 11:37:44 -0500 Received: from mga07.intel.com ([134.134.136.100]:53717 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1426072AbeBOQgR (ORCPT ); Thu, 15 Feb 2018 11:36:17 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Feb 2018 08:36:16 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,517,1511856000"; d="scan'208";a="28306003" Received: from jacob-builder.jf.intel.com (HELO jacob-builder) ([10.7.199.155]) by orsmga003.jf.intel.com with ESMTP; 15 Feb 2018 08:36:16 -0800 Date: Thu, 15 Feb 2018 08:38:11 -0800 From: Jacob Pan To: Joerg Roedel Cc: "Raj, Ashok" , Sohil Mehta , Alex Williamson , David Woodhouse , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Gayatri Kammela , Ravi V Shankar , Andy Shevchenko , Lu Baolu , Fenghua Yu , jacob.jun.pan@linux.intel.com Subject: Re: [PATCH v7 0/5] Add Intel IOMMU debugfs support Message-ID: <20180215083811.3ec86e49@jacob-builder> In-Reply-To: <20180215095337.fccoozdclfnbepi4@8bytes.org> References: <1517619001-148586-1-git-send-email-sohil.mehta@intel.com> <20180213140303.42mbzfxpypljy37l@8bytes.org> <20180213214002.GA27066@otc-nc-03> <20180213145332.35c73eda@jacob-builder> <20180215095337.fccoozdclfnbepi4@8bytes.org> 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 Thu, 15 Feb 2018 10:53:38 +0100 Joerg Roedel wrote: > On Tue, Feb 13, 2018 at 02:53:32PM -0800, Jacob Pan wrote: > > We did start out with /dev/mem but run into CONFIG_STRICT_DEVMEM > > requirement which is turned on by default. > > libpci is only limited to PCI config space access, right? > > Even if /dev/mem is not an option, I am still not convinced that this > is a good idea. How should this be used? Will you just use it to debug > Intel IOMMUs when you guys work on the driver or should users report > the data back when they hit problems? > It is for both but mainly the latter. when we have customers/users reporting Intel IOMMU issues, it would be extremely helpful if we can ask them to turn debugfs on and report the state. As we move to SVA, we may also include io page table similar to /sys/kernel/debug/page_table for PASID etc. Just wondering if your concern is on the implementation or the debugfs idea in general. Perhaps have some common IOMMU debugfs?