linux-kernel - Re: [PATCH v3 0/5] Introduce "non-pixel" sub node within iris video node

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: <25c64712-960a-50b4-e7fa-398e4bf809ef@quicinc.com>
Date: Thu, 10 Jul 2025 23:48:30 +0530
From: Prakash Gupta <quic_guptap@...cinc.com>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
        Dmitry Baryshkov
	<dmitry.baryshkov@....qualcomm.com>
CC: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
        Krzysztof Kozlowski
	<krzk@...nel.org>,
        Vikash Garodia <quic_vgarodia@...cinc.com>,
        "Dikshita
 Agarwal" <quic_dikshita@...cinc.com>,
        Abhinav Kumar
	<abhinav.kumar@...ux.dev>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Rob
 Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor
 Dooley <conor+dt@...nel.org>, <linux-media@...r.kernel.org>,
        <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/5] Introduce "non-pixel" sub node within iris video
 node



On 7/5/2025 4:14 AM, Bryan O'Donoghue wrote:
> On 04/07/2025 17:45, Dmitry Baryshkov wrote:
>> What about instead:
>>
>> - keep IOMMU entries as is
> ack
> 
>> - Add iommu-maps, mapping the non-pixel SID
>> - In future expand iommu-maps, describing the secure contexts?
> 
> Interesting, we are _adding_ so that's not an ABI break and if I'm
> reading the documentation right, there's no hard rule on what iommu-map
> defines i.e. nothing to preclude us from encoding the information we
> want here.
> 
> This might work.
> 
> drivers/pci/controller/dwc/pcie-qcom.c::qcom_pcie_config_sid_1_9_0()
> 
> You can register your platform device to the SID map you parse.

I see few limitations with using iommu-map here, some of these are
listed in [1]

1. We can't specify SMR mask with iommu-map.
2. We can't specify different iommu-addresses range for specific contexts.
3. The secure CB support [2] would require vmid information associated
with per context. I think this can't be provided with iommu-map.

[1]
https://lore.kernel.org/all/85137a8e-45be-3bb2-d094-79754fa2a8be@quicinc.com/
[2]
https://lore.kernel.org/all/20231101071144.16309-2-quic_gkohli@quicinc.com/

Thanks,
Prakash