linux-kernel - [PATCH 0/3] iommu: Expose IOMMU information in sysfs

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Jun 2014 16:12:18 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	iommu@...ts.linux-foundation.org
Cc:	joro@...tes.org, dwmw2@...radead.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] iommu: Expose IOMMU information in sysfs

Users want to know the features of their hardware and we need a better
way to get it than parsing it out of dmesg.  This series creates an
IOMMU class and allows drivers to create and destroy a device within
that class.  Drivers may also link and unlink devices to expose the
association of a device to a specific hardware unit and create
attribute groups to expose further information about the specific
IOMMU.

An example use case for this would be to determine whether the IOMMU
for a device supports super-pages, which can have performance
implications for a device assignment scenario.  A user with multiple
IOMMU units may also want to factor load per IOMMU into their hardware
layout.  This helps to expose those connections.

I posted an RFC for this last month, but there were no comments.  This
version officialy includes AMD-Vi support and removes the kobject used
for creating the "devices" subdirectory, instead using an empty
attribute group.  I've tried not to duplicate any information
available elsewhere for the user, for example in the DMAR or IVRS
tables.  This means that while I think it might be interesting to
expose things like RMRR, the user already has access to those by
parsing the appropriate firmware table.  I welcome any additional
IOMMU driver implementaitons.  Thanks,

Alex

---

Alex Williamson (3):
      iommu: Add sysfs support for IOMMUs
      iommu/intel: Make use of IOMMU sysfs support
      iommu/amd: Add sysfs support

 Documentation/ABI/testing/sysfs-class-iommu        |   17 +++
 .../ABI/testing/sysfs-class-iommu-amd-iommu        |   14 ++
 .../ABI/testing/sysfs-class-iommu-intel-iommu      |   32 +++++
 drivers/iommu/Makefile                             |    1 
 drivers/iommu/amd_iommu.c                          |    6 +
 drivers/iommu/amd_iommu_init.c                     |   38 ++++++
 drivers/iommu/amd_iommu_types.h                    |    3 
 drivers/iommu/dmar.c                               |    9 +
 drivers/iommu/intel-iommu.c                        |   77 +++++++++++-
 drivers/iommu/iommu-sysfs.c                        |  133 ++++++++++++++++++++
 include/linux/intel-iommu.h                        |    3 
 include/linux/iommu.h                              |   26 ++++
 12 files changed, 358 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/ABI/testing/sysfs-class-iommu
 create mode 100644 Documentation/ABI/testing/sysfs-class-iommu-amd-iommu
 create mode 100644 Documentation/ABI/testing/sysfs-class-iommu-intel-iommu
 create mode 100644 drivers/iommu/iommu-sysfs.c
--
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/