iommu/vt-d: patches for v5.11
Subsystems (2)
Lu Baolu
maintainerHi Will,
Below patch is ready for v5.11. It includes:
- Avoid GFP_ATOMIC where it is not needed
Can you please consider it for v5.11?
Best regards,
Lu Baolu
Christophe JAILLET (1):
iommu/vt-d: Avoid GFP_ATOMIC where it is not needed
drivers/iommu/intel/iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 6 lines
2.25.1 _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
Lu Baolu
maintainerPATCH 1/1 iommu/vt-d: Avoid GFP_ATOMIC where it is not needed
From: Christophe JAILLET <[email protected]>
There is no reason to use GFP_ATOMIC in a 'suspend' function. Use GFP_KERNEL instead to give more opportunities to allocate the requested memory.
Signed-off-by Christophe JAILLET <[email protected]>
Signed-off-by Lu Baolu <[email protected]>
--- drivers/iommu/intel/iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/intel/iommu.c +1 -1
@@ -3485,7 +3485,7 @@ static int iommu_suspend(void)for_each_active_iommu (iommu, drhd) { iommu->iommu_state =kcalloc (MAX_SR_DMAR_REGS ,sizeof (u32), -GFP_ATOMIC ); +GFP_KERNEL );if (!iommu->iommu_state) goto nomem; }
Signature · 6 lines
2.25.1 _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
Quoted 10 lines · Lu Baolu
Below patch is ready for v5.11. It includes:
- Avoid
GFP_ATOMICwhere it is not neededCan you please consider it for v5.11?
Best regards,
Lu Baolu[...]
Applied to arm64 (for-next/iommu/vt-d), thanks!
[1/1] iommu/vt-d: Avoid GFP_ATOMIC where it is not needed
https://git.kernel.org/arm64/c/33e07157105e
Cheers,
Signature · 9 lines
Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu