lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1402932269.3707.35.camel@ul30vt.home>
Date:	Mon, 16 Jun 2014 09:24:29 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Joerg Roedel <joro@...tes.org>
Cc:	iommu@...ts.linux-foundation.org, dwmw2@...radead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] iommu: Expose IOMMU information in sysfs

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ