linux-kernel - Re: [PATCH V3 1/2] Documentation: x86: Add documentation for AMD IOMMU

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b3998af9-24bc-6191-a8ed-de747e895799@intel.com>
Date:   Tue, 29 Mar 2022 08:24:31 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Alex Deucher <alexander.deucher@....com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        corbet@....net, hpa@...or.com, x86@...nel.org,
        dave.hansen@...ux.intel.com, bp@...en8.de, mingo@...hat.com,
        tglx@...utronix.de, joro@...tes.org, suravee.suthikulpanit@....com,
        will@...nel.org, iommu@...ts.linux-foundation.org,
        robin.murphy@....com, vasant.hegde@....com
Subject: Re: [PATCH V3 1/2] Documentation: x86: Add documentation for AMD
 IOMMU

On 3/28/22 10:28, Alex Deucher wrote:
> +How is IOVA generated?
> +----------------------
> +
> +Well behaved drivers call dma_map_*() calls before sending command to device
> +that needs to perform DMA. Once DMA is completed and mapping is no longer
> +required, driver performs dma_unmap_*() calls to unmap the region.
> +
> +Fault reporting
> +---------------
> +
> +When errors are reported, the IOMMU signals via an interrupt. The fault
> +reason and device that caused it is printed on the console.

Just scanning this, it looks *awfully* generic.  Is anything in here
AMD-specific?  Should this be in an AMD-specific file?