[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fab4c8a-7bc5-9a50-d48a-0dc590cac7a6@linux.intel.com>
Date: Wed, 6 Jul 2022 09:53:40 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Robin Murphy <robin.murphy@....com>, joro@...tes.org
Cc: baolu.lu@...ux.intel.com, will@...nel.org, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
suravee.suthikulpanit@....com, vasant.hegde@....com,
mjrosato@...ux.ibm.com, gerald.schaefer@...ux.ibm.com,
schnelle@...ux.ibm.com, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 03/15] iommu: Always register bus notifiers
On 2022/7/6 01:08, Robin Murphy wrote:
> /*
> * Use a function instead of an array here because the domain-type is a
> * bit-field, so an array would waste memory.
> @@ -152,6 +172,10 @@ static int __init iommu_subsys_init(void)
> (iommu_cmd_line & IOMMU_CMD_LINE_STRICT) ?
> "(set via kernel command line)" : "");
>
> + /* If the system is so broken that this fails, it will WARN anyway */
Can you please elaborate a bit on this? iommu_bus_init() still return
errors.
> + for (int i = 0; i < ARRAY_SIZE(iommu_buses); i++)
> + iommu_bus_init(iommu_buses[i]);
> +
> return 0;
Best regards,
baolu
Powered by blists - more mailing lists