From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/3] iommu: Expose IOMMU information in sysfs
Date: Thu, 12 Jun 2014 16:12:18 -0600 [thread overview]
Message-ID: <20140612215954.2754.30263.stgit@bling.home> (raw)
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
next reply other threads:[~2014-06-12 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 22:12 Alex Williamson [this message]
[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 ` [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
[not found] ` <20140616151619.GA31771-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
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
[not found] ` <1404403726.1862.78.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
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=20140612215954.2754.30263.stgit@bling.home \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox