Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

Intel-IOMMU.txt: standardize document format

Each text file under Documentation follows a different
format. Some doesn't even have titles!

Change its representation to follow the adopted standard,
using ReST markups for it to be parseable by Sphinx:

This file is almost in the right format. It only needed to
convert a list to bulleted list and to use the right markup
for literal blocks.

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

Mauro Carvalho Chehab and committed by
Jonathan Corbet
45d85146 7e18c07e

+20 -17
+20 -17
Documentation/Intel-IOMMU.txt
··· 1 + =================== 1 2 Linux IOMMU Support 2 3 =================== 3 4 ··· 10 9 11 10 Some Keywords 12 11 13 - DMAR - DMA remapping 14 - DRHD - DMA Remapping Hardware Unit Definition 15 - RMRR - Reserved memory Region Reporting Structure 16 - ZLR - Zero length reads from PCI devices 17 - IOVA - IO Virtual address. 12 + - DMAR - DMA remapping 13 + - DRHD - DMA Remapping Hardware Unit Definition 14 + - RMRR - Reserved memory Region Reporting Structure 15 + - ZLR - Zero length reads from PCI devices 16 + - IOVA - IO Virtual address. 18 17 19 18 Basic stuff 20 19 ----------- ··· 34 33 unity mappings for these regions for these devices to access these regions. 35 34 36 35 How is IOVA generated? 37 - --------------------- 36 + ---------------------- 38 37 39 38 Well behaved drivers call pci_map_*() calls before sending command to device 40 39 that needs to perform DMA. Once DMA is completed and mapping is no longer ··· 83 82 ACPI: DMAR (v001 A M I OEMDMAR 0x00000001 MSFT 0x00000097) @ 0x000000007f5b5ef0 84 83 85 84 When DMAR is being processed and initialized by ACPI, prints DMAR locations 86 - and any RMRR's processed. 85 + and any RMRR's processed:: 87 86 88 - ACPI DMAR:Host address width 36 89 - ACPI DMAR:DRHD (flags: 0x00000000)base: 0x00000000fed90000 90 - ACPI DMAR:DRHD (flags: 0x00000000)base: 0x00000000fed91000 91 - ACPI DMAR:DRHD (flags: 0x00000001)base: 0x00000000fed93000 92 - ACPI DMAR:RMRR base: 0x00000000000ed000 end: 0x00000000000effff 93 - ACPI DMAR:RMRR base: 0x000000007f600000 end: 0x000000007fffffff 87 + ACPI DMAR:Host address width 36 88 + ACPI DMAR:DRHD (flags: 0x00000000)base: 0x00000000fed90000 89 + ACPI DMAR:DRHD (flags: 0x00000000)base: 0x00000000fed91000 90 + ACPI DMAR:DRHD (flags: 0x00000001)base: 0x00000000fed93000 91 + ACPI DMAR:RMRR base: 0x00000000000ed000 end: 0x00000000000effff 92 + ACPI DMAR:RMRR base: 0x000000007f600000 end: 0x000000007fffffff 94 93 95 94 When DMAR is enabled for use, you will notice.. 96 95 ··· 99 98 Fault reporting 100 99 --------------- 101 100 102 - DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000 103 - DMAR:[fault reason 05] PTE Write access is not set 104 - DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000 105 - DMAR:[fault reason 05] PTE Write access is not set 101 + :: 102 + 103 + DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000 104 + DMAR:[fault reason 05] PTE Write access is not set 105 + DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000 106 + DMAR:[fault reason 05] PTE Write access is not set 106 107 107 108 TBD 108 109 ----