From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] iommu: Expose IOMMU information in sysfs
Date: Mon, 16 Jun 2014 17:16:19 +0200 [thread overview]
Message-ID: <20140616151619.GA31771@8bytes.org> (raw)
In-Reply-To: <20140612215954.2754.30263.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
On Thu, Jun 12, 2014 at 04:12:18PM -0600, Alex Williamson wrote:
> Alex Williamson (3):
> iommu: Add sysfs support for IOMMUs
> iommu/intel: Make use of IOMMU sysfs support
> iommu/amd: Add sysfs support
I like the general approach. But why do you only enable the x86 iommus?
Some ARM IOMMUs and PAMU would certainly also benefit from a sysfs
representation of which device is translated by which IOMMU.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: iommu@lists.linux-foundation.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iommu: Expose IOMMU information in sysfs
Date: Mon, 16 Jun 2014 17:16:19 +0200 [thread overview]
Message-ID: <20140616151619.GA31771@8bytes.org> (raw)
In-Reply-To: <20140612215954.2754.30263.stgit@bling.home>
On Thu, Jun 12, 2014 at 04:12:18PM -0600, Alex Williamson wrote:
> Alex Williamson (3):
> iommu: Add sysfs support for IOMMUs
> iommu/intel: Make use of IOMMU sysfs support
> iommu/amd: Add sysfs support
I like the general approach. But why do you only enable the x86 iommus?
Some ARM IOMMUs and PAMU would certainly also benefit from a sysfs
representation of which device is translated by which IOMMU.
Joerg
next prev parent reply other threads:[~2014-06-16 15:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 22:12 [PATCH 0/3] iommu: Expose IOMMU information in sysfs Alex Williamson
2014-06-12 22:12 ` Alex Williamson
[not found] ` <20140612215954.2754.30263.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2014-06-12 22:12 ` [PATCH 1/3] iommu: Add sysfs support for IOMMUs Alex Williamson
2014-06-12 22:12 ` Alex Williamson
2014-06-12 22:12 ` [PATCH 2/3] iommu/intel: Make use of IOMMU sysfs support Alex Williamson
2014-06-12 22:12 ` Alex Williamson
2014-06-12 22:12 ` [PATCH 3/3] iommu/amd: Add " Alex Williamson
2014-06-12 22:12 ` Alex Williamson
2014-06-16 15:16 ` Joerg Roedel [this message]
2014-06-16 15:16 ` [PATCH 0/3] iommu: Expose IOMMU information in sysfs Joerg Roedel
[not found] ` <20140616151619.GA31771-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-06-16 15:24 ` Alex Williamson
2014-06-16 15:24 ` Alex Williamson
[not found] ` <1402932269.3707.35.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2014-07-03 16:08 ` Alex Williamson
2014-07-03 16:08 ` Alex Williamson
[not found] ` <1404403726.1862.78.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2014-07-03 17:43 ` Varun Sethi
2014-07-03 17:43 ` Varun Sethi
2014-07-04 10:37 ` Joerg Roedel
2014-07-04 10:37 ` Joerg Roedel
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=20140616151619.GA31771@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.