mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
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 09:24:29 -0600	[thread overview]
Message-ID: <1402932269.3707.35.camel@ul30vt.home> (raw)
In-Reply-To: <20140616151619.GA31771@8bytes.org>

On Mon, 2014-06-16 at 17:16 +0200, Joerg Roedel wrote:
> 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.

Only because I have no ability to test the others platforms.  I'd be
thrilled if someone working on those IOMMUs could validate this on
non-x86.  Thanks,

Alex


  reply	other threads:[~2014-06-16 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 22:12 Alex Williamson
2014-06-12 22:12 ` [PATCH 1/3] iommu: Add sysfs support for IOMMUs 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 ` [PATCH 3/3] iommu/amd: Add " Alex Williamson
2014-06-16 15:16 ` [PATCH 0/3] iommu: Expose IOMMU information in sysfs Joerg Roedel
2014-06-16 15:24   ` Alex Williamson [this message]
2014-07-03 16:08     ` Alex Williamson
2014-07-03 17:43       ` Varun Sethi
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=1402932269.3707.35.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.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

all inboxes | Powered by JetHome®