diff options
| author | Vasant Hegde <vasant.hegde@amd.com> | 2023-11-22 09:02:08 +0000 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2023-12-11 15:25:34 +0100 |
| commit | 3f2571fed2fa9e9ea61fd990a9a4fc20ca83b62e (patch) | |
| tree | ad5ccf2b906feef6fad03d4ebdb048404113b84b /drivers/iommu | |
| parent | af3263758bf0b65a040e90190ab708b8a4027947 (diff) | |
| download | linux-stable-3f2571fed2fa9e9ea61fd990a9a4fc20ca83b62e.tar.gz linux-stable-3f2571fed2fa9e9ea61fd990a9a4fc20ca83b62e.tar.bz2 linux-stable-3f2571fed2fa9e9ea61fd990a9a4fc20ca83b62e.zip | |
iommu/amd: Remove redundant domain flush from attach_device()
Domain flush was introduced in attach_device() path to handle kdump
scenario. Later init code was enhanced to handle kdump scenario where
it also takes care of flushing everything including TLB
(see early_enable_iommus()).
Hence remove redundant flush from attach_device() function.
Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
Reviewed-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/r/20231122090215.6191-3-vasant.hegde@amd.com
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu')
| -rw-r--r-- | drivers/iommu/amd/iommu.c | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c index c2578b567e35..233076686379 100644 --- a/drivers/iommu/amd/iommu.c +++ b/drivers/iommu/amd/iommu.c @@ -1896,15 +1896,6 @@ static int attach_device(struct device *dev, do_attach(dev_data, domain); - /* - * We might boot into a crash-kernel here. The crashed kernel - * left the caches in the IOMMU dirty. So we have to flush - * here to evict all dirty stuff. - */ - amd_iommu_domain_flush_tlb_pde(domain); - - amd_iommu_domain_flush_complete(domain); - out: spin_unlock(&dev_data->lock); |