[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276287E75395A59865812978C919@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Thu, 21 Jul 2022 07:39:20 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>
CC: Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
"Robin Murphy" <robin.murphy@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/1] iommu/vt-d: Fix possible recursive locking in
intel_iommu_init()
> From: Lu Baolu <baolu.lu@...ux.intel.com>
> Sent: Tuesday, July 19, 2022 7:53 AM
>
> @@ -88,7 +89,8 @@ extern struct list_head dmar_drhd_units;
> static inline bool dmar_rcu_check(void)
> {
> return rwsem_is_locked(&dmar_global_lock) ||
> - system_state == SYSTEM_BOOTING;
> + system_state == SYSTEM_BOOTING ||
> + (IS_ENABLED(CONFIG_INTEL_IOMMU)
> && !intel_iommu_enabled);
> }
intel_iommu_enabled is 0 if CONFIG_INTEL_IOMMU is not set.
same for other similar checks.
Powered by blists - more mailing lists