| Andrew Scull | b4b6d4a | 2019-01-02 15:54:55 +0000 | [diff] [blame] | 1 | What: /sys/kernel/iommu_groups/ |
| 2 | Date: May 2012 |
| 3 | KernelVersion: v3.5 |
| 4 | Contact: Alex Williamson <alex.williamson@redhat.com> |
| 5 | Description: /sys/kernel/iommu_groups/ contains a number of sub- |
| 6 | directories, each representing an IOMMU group. The |
| 7 | name of the sub-directory matches the iommu_group_id() |
| 8 | for the group, which is an integer value. Within each |
| 9 | subdirectory is another directory named "devices" with |
| 10 | links to the sysfs devices contained in this group. |
| 11 | The group directory also optionally contains a "name" |
| 12 | file if the IOMMU driver has chosen to register a more |
| 13 | common name for the group. |
| 14 | Users: |
| 15 | |
| 16 | What: /sys/kernel/iommu_groups/reserved_regions |
| 17 | Date: January 2017 |
| 18 | KernelVersion: v4.11 |
| 19 | Contact: Eric Auger <eric.auger@redhat.com> |
| 20 | Description: /sys/kernel/iommu_groups/reserved_regions list IOVA |
| 21 | regions that are reserved. Not necessarily all |
| 22 | reserved regions are listed. This is typically used to |
| 23 | output direct-mapped, MSI, non mappable regions. Each |
| 24 | region is described on a single line: the 1st field is |
| 25 | the base IOVA, the second is the end IOVA and the third |
| 26 | field describes the type of the region. |
| David Brazdil | 0f672f6 | 2019-12-10 10:32:29 +0000 | [diff] [blame^] | 27 | |
| 28 | What: /sys/kernel/iommu_groups/reserved_regions |
| 29 | Date: June 2019 |
| 30 | KernelVersion: v5.3 |
| 31 | Contact: Eric Auger <eric.auger@redhat.com> |
| 32 | Description: In case an RMRR is used only by graphics or USB devices |
| 33 | it is now exposed as "direct-relaxable" instead of "direct". |
| 34 | In device assignment use case, for instance, those RMRR |
| 35 | are considered to be relaxable and safe. |