[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7eb6b36c-da94-4363-9ee2-d3d38ec46a22@ti.com>
Date: Mon, 21 Jul 2025 12:51:06 +0530
From: s-vadapalli <s-vadapalli@...com>
To: <huaqian.li@...mens.com>
CC: <s-vadapalli@...com>, <baocheng.su@...mens.com>, <bhelgaas@...gle.com>,
<conor+dt@...nel.org>, <devicetree@...r.kernel.org>,
<diogo.ivo@...mens.com>, <helgaas@...nel.org>,
<jan.kiszka@...mens.com>, <kristo@...nel.org>, <krzk+dt@...nel.org>,
<kw@...ux.com>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-pci@...r.kernel.org>,
<lpieralisi@...nel.org>, <nm@...com>, <robh@...nel.org>,
<ssantosh@...nel.org>, <vigneshr@...com>
Subject: Re: [PATCH v10 4/7] PCI: keystone: Add support for PVU-based DMA
isolation on AM654
On Mon, Jul 21, 2025 at 10:59:42AM +0800, huaqian.li@...mens.com wrote:
> From: Jan Kiszka <jan.kiszka@...mens.com>
>
> The AM654 lacks an IOMMU, thus does not support isolating DMA requests
> from untrusted PCI devices to selected memory regions this way. Use
> static PVU-based protection instead. The PVU, when enabled, will only
> accept DMA requests that address previously configured regions.
>
> Use the availability of a restricted-dma-pool memory region as trigger
> and register it as valid DMA target with the PVU. In addition, enable
> the mapping of requester IDs to VirtIDs in the PCI RC. Use only a single
> VirtID so far, catching all devices.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@...mens.com>
> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
> Signed-off-by: Li Hua Qian <huaqian.li@...mens.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@...com>
Regards,
Siddharth.
Powered by blists - more mailing lists