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;
Date:   Thu, 15 Mar 2018 14:58:38 +0100
From:   Joerg Roedel <joro@8bytes.org>
To:     Gary R Hook <gary.hook@amd.com>
Cc:     iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Add debugfs info for the AMD IOMMU
Message-ID: <20180315135838.GB5259@8bytes.org>
References: <152106836233.67212.15861879210675477690.stgit@sosxen2.amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <152106836233.67212.15861879210675477690.stgit@sosxen2.amd.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Mar 14, 2018 at 06:04:44PM -0500, Gary R Hook wrote:
> Gary R Hook (5):
>       iommu/amd - Add debugfs support
>       iommu/amd - Add a 'verbose' switch for IOMMU debugfs
>       iommu/amd - Add a README variable for the IOMMU debugfs
>       iommu/amd - Expose the active IOMMU device table entries
>       iommu/amd - Add a debugfs entry to specify a IOMMU device table entry

Same problem here as with the Intel patches, I don't think it's a good
idea to reveal internal iommu data structures to user-space in this way.

I've debugged iommu issues for around 10 years now and never had the
need for an interface that reveals those internals. How exactly are you
planning to use this information?


	Joerg