RE: [PATCH v2 01/10] iommu: Add a gfp parameter to iommu_map()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: RE: [PATCH v2 01/10] iommu: Add a gfp parameter to iommu_map()
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 19 Jan 2023 03:45:27 +0000
Accept-language: en-US
Cc: Alex Williamson <alex.williamson@xxxxxxxxxx>, "ath10k@xxxxxxxxxxxxxxxxxxx" <ath10k@xxxxxxxxxxxxxxxxxxx>, "ath11k@xxxxxxxxxxxxxxxxxxx" <ath11k@xxxxxxxxxxxxxxxxxxx>, Christian Borntraeger <borntraeger@xxxxxxxxxxxxx>, "dri-devel@xxxxxxxxxxxxxxxxxxxxx" <dri-devel@xxxxxxxxxxxxxxxxxxxxx>, "iommu@xxxxxxxxxxxxxxx" <iommu@xxxxxxxxxxxxxxx>, "kvm@xxxxxxxxxxxxxxx" <kvm@xxxxxxxxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-arm-msm@xxxxxxxxxxxxxxx" <linux-arm-msm@xxxxxxxxxxxxxxx>, "linux-media@xxxxxxxxxxxxxxx" <linux-media@xxxxxxxxxxxxxxx>, "linux-rdma@xxxxxxxxxxxxxxx" <linux-rdma@xxxxxxxxxxxxxxx>, "linux-remoteproc@xxxxxxxxxxxxxxx" <linux-remoteproc@xxxxxxxxxxxxxxx>, "linux-s390@xxxxxxxxxxxxxxx" <linux-s390@xxxxxxxxxxxxxxx>, "linux-stm32@xxxxxxxxxxxxxxxxxxxxxxxxxxxx" <linux-stm32@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "linux-tegra@xxxxxxxxxxxxxxx" <linux-tegra@xxxxxxxxxxxxxxx>, "linux-wireless@xxxxxxxxxxxxxxx" <linux-wireless@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx>, "nouveau@xxxxxxxxxxxxxxxxxxxxx" <nouveau@xxxxxxxxxxxxxxxxxxxxx>, Niklas Schnelle <schnelle@xxxxxxxxxxxxx>, "virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx" <virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx>
In-reply-to: <1-v2-ce66f632bd0d+484-iommu_map_gfp_jgg@nvidia.com>
References: <0-v2-ce66f632bd0d+484-iommu_map_gfp_jgg@nvidia.com> <1-v2-ce66f632bd0d+484-iommu_map_gfp_jgg@nvidia.com>

> From: Jason Gunthorpe <jgg@xxxxxxxxxx>
> Sent: Thursday, January 19, 2023 2:01 AM
> 
> The internal mechanisms support this, but instead of exposting the gfp to
> the caller it wrappers it into iommu_map() and iommu_map_atomic()
> 
> Fix this instead of adding more variants for GFP_KERNEL_ACCOUNT.
> 
> Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxx>

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

References:
- [PATCH v2 00/10] Let iommufd charge IOPTE allocations to the memory cgroup
  - From: Jason Gunthorpe
- [PATCH v2 01/10] iommu: Add a gfp parameter to iommu_map()
  - From: Jason Gunthorpe

Prev by Date: RE: [PATCH v2 04/10] iommu/dma: Use the gfp parameter in __iommu_dma_alloc_noncontiguous()
Next by Date: RE: [PATCH v2 02/10] iommu: Remove iommu_map_atomic()
Previous by thread: [PATCH v2 01/10] iommu: Add a gfp parameter to iommu_map()
Next by thread: [PATCH v2 09/10] iommu/s390: Push the gfp parameter to the kmem_cache_alloc()'s
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]