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
Date: Thu, 15 Mar 2018 14:58:38 +0100 [thread overview]
Message-ID: <20180315135838.GB5259@8bytes.org> (raw)
In-Reply-To: <152106836233.67212.15861879210675477690.stgit@sosxen2.amd.com>
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
next prev parent reply other threads:[~2018-03-15 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 23:04 [PATCH v3 0/5] Add debugfs info for the AMD IOMMU Gary R Hook
2018-03-14 23:04 ` [PATCH v3 1/5] iommu/amd - Add debugfs support Gary R Hook
2018-03-14 23:05 ` [PATCH v3 2/5] iommu/amd - Add a 'verbose' switch for IOMMU debugfs Gary R Hook
2018-03-14 23:05 ` [PATCH v3 3/5] iommu/amd - Add a README variable for the " Gary R Hook
2018-03-14 23:05 ` [PATCH v3 4/5] iommu/amd - Expose the active IOMMU device table entries Gary R Hook
2018-03-14 23:05 ` [PATCH v3 5/5] iommu/amd - Add a debugfs entry to specify a IOMMU device table entry Gary R Hook
2018-03-17 20:09 ` kbuild test robot
2018-03-15 13:58 ` Joerg Roedel [this message]
2018-03-26 23:33 ` [PATCH v3 0/5] Add debugfs info for the AMD IOMMU Gary R Hook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180315135838.GB5259@8bytes.org \
--to=joro@8bytes.org \
--cc=gary.hook@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox