linux-kernel - Re: [PATCH v7 0/8] soc: ti: Add and use PVU on K3-AM65 for DMA isolation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250418134324.ewsfnze2btnx2r2w@country>
Date: Fri, 18 Apr 2025 08:43:24 -0500
From: Nishanth Menon <nm@...com>
To: <huaqian.li@...mens.com>
CC: <helgaas@...nel.org>, <m.szyprowski@...sung.com>, <robin.murphy@....com>,
        <baocheng.su@...mens.com>, <bhelgaas@...gle.com>,
        <conor+dt@...nel.org>, <devicetree@...r.kernel.org>,
        <diogo.ivo@...mens.com>, <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>,
        <robh@...nel.org>, <s-vadapalli@...com>, <ssantosh@...nel.org>,
        <vigneshr@...com>, <iommu@...ts.linux.dev>
Subject: Re: [PATCH v7 0/8] soc: ti: Add and use PVU on K3-AM65 for DMA
 isolation

On 15:30-20250418, huaqian.li@...mens.com wrote:
> 
> Jan Kiszka (7):
>   dt-bindings: soc: ti: Add AM65 peripheral virtualization unit
>   dt-bindings: PCI: ti,am65: Extend for use with PVU
>   soc: ti: Add IOMMU-like PVU driver
>   PCI: keystone: Add support for PVU-based DMA isolation on AM654
>   arm64: dts: ti: k3-am65-main: Add PVU nodes
>   arm64: dts: ti: k3-am65-main: Add VMAP registers to PCI root complexes
>   arm64: dts: ti: iot2050: Add overlay for DMA isolation for devices
>     behind PCI RC
> 
> Li Hua Qian (1):
>   swiotlb: Make IO_TLB_SEGSIZE configurable

I see at least 3 or 4 maintainers needing to co-ordinate, gets
complicated as I am not sure which maintainer needs to pick up what
patches in what dependency order. This looks like a mixed bag. Can
we split this patch into independent series for each maintainer with
clear indication of dependencies that is spread around a couple of
kernel windows (maybe dts comes in last?)

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D