iommu/vt-d: Avoid GFP_ATOMIC where it is not needed
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 <christophe.jaillet@wanadoo.fr> Link: https://lore.kernel.org/r/20201030182630.5154-1-christophe.jaillet@wanadoo.fr Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Link: https://lore.kernel.org/r/20201201013149.2466272-2-baolu.lu@linux.intel.com Signed-off-by: Will Deacon <will@kernel.org>
This commit is contained in:
parent
405a43cc00
commit
33e0715710
1 changed files with 1 additions and 1 deletions
|
@ -3492,7 +3492,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;
|
||||
}
|
||||
|
|
Loading…
Add table
Reference in a new issue