mirror of
git://nv-tegra.nvidia.com/linux-nv-oot.git
synced 2025-12-22 09:11:26 +03:00
6e5aec9ce4
- The VI is allowed to access the whole of the Guest VM currently as it is a stage-2 SMMU device. Hence it can read and write to any memory. This may lead to breach of confidentiality and integrity. In order to restrict the VI from accessing the whole VM, a mempool is being created by HV that would restrict access to VI to just the mempool memory. - In nvmap, we have some special rules for IVM carveout like if user specify IVM carveout to allocate from, then if first IVM carveout does not have sufficient memory then nvmap tries to allocate from next IVM carveout. We don't want these rules applicable for VI mempool heap, hence only carveout initialization part would remain similar to IVM carveouts but rest of the operations would be performed normally like any other carveout. - Add DT binding doc for VI-carveout. Bug 4648721 Change-Id: Ib40415a4c80da908654c86162c1cd4b50b33ef31 Signed-off-by: Ketan Patil <ketanp@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nv-oot/+/3196238 Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>