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
| ||
|
Date: Tue, 10 Mar 2020 17:23:20 +0100 From: Joerg Roedel <joro@...tes.org> To: Sibi Sankar <sibis@...eaurora.org> Cc: bjorn.andersson@...aro.org, robh+dt@...nel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org, iommu@...ts.linux-foundation.org, linux-remoteproc@...r.kernel.org, ohad@...ery.com, agross@...nel.org, linux-kernel-owner@...r.kernel.org Subject: Re: [PATCH 0/3] Request direct mapping for modem firmware subdevice On Tue, Mar 10, 2020 at 07:30:50PM +0530, Sibi Sankar wrote: > The accesses are initiated by the firmware > and they access modem reserved regions. > However as explained in ^^ any accesses > outside the region will result in a violation > and is controlled through XPUs (protection units). Okay, this sounds like a case for arm_smmu_get_resv_region(). It should return an entry for the reserved memory region the firmware needs to access, so that generic iommu can setup this mapping. Note that it should return that entry only for your device, not for all devices. Maybe there is a property in DT or IORT you can set to transport this information into the arm-smmu driver. This is pretty similar to RMRR mapping on the Intel VT-d IOMMU or Unity-mapped ranges in the AMD-Vi IOMMU. Regards, Joerg
Powered by blists - more mailing lists