All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Baolu Lu <baolu.lu@linux.intel.com>, joro@8bytes.org
Cc: will@kernel.org, iommu@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	suravee.suthikulpanit@amd.com, vasant.hegde@amd.com,
	mjrosato@linux.ibm.com, gerald.schaefer@linux.ibm.com,
	schnelle@linux.ibm.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 03/15] iommu: Always register bus notifiers
Date: Wed, 6 Jul 2022 14:43:40 +0100	[thread overview]
Message-ID: <3d613192-f673-852e-9c52-b8a913d25616@arm.com> (raw)
In-Reply-To: <1fab4c8a-7bc5-9a50-d48a-0dc590cac7a6@linux.intel.com>

On 2022-07-06 02:53, Baolu Lu wrote:
> 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.

Indeed, it's commenting on the fact that we don't try to clean up or 
propagate an error value further even if it did ever manage to return 
one. I feared that if I strip the error handling out of iommu_bus_init() 
itself on the same reasoning, we'll just get constant patches from the 
static checker brigade trying to add it back, so it seemed like the 
neatest compromise to keep that decision where it's obviously in an 
early initcall, rather than in the helper function which can be viewed 
out of context. However, I'm happy to either expand this comment or go 
the whole way and make iommu_bus_init() return void if you think it's 
worthwhile.

Cheers,
Robin.

> 
>> +    for (int i = 0; i < ARRAY_SIZE(iommu_buses); i++)
>> +        iommu_bus_init(iommu_buses[i]);
>> +
>>       return 0;
> 
> Best regards,
> baolu

WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: Baolu Lu <baolu.lu@linux.intel.com>, joro@8bytes.org
Cc: will@kernel.org, iommu@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	suravee.suthikulpanit@amd.com, vasant.hegde@amd.com,
	mjrosato@linux.ibm.com, gerald.schaefer@linux.ibm.com,
	schnelle@linux.ibm.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 03/15] iommu: Always register bus notifiers
Date: Wed, 6 Jul 2022 14:43:40 +0100	[thread overview]
Message-ID: <3d613192-f673-852e-9c52-b8a913d25616@arm.com> (raw)
In-Reply-To: <1fab4c8a-7bc5-9a50-d48a-0dc590cac7a6@linux.intel.com>

On 2022-07-06 02:53, Baolu Lu wrote:
> 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.

Indeed, it's commenting on the fact that we don't try to clean up or 
propagate an error value further even if it did ever manage to return 
one. I feared that if I strip the error handling out of iommu_bus_init() 
itself on the same reasoning, we'll just get constant patches from the 
static checker brigade trying to add it back, so it seemed like the 
neatest compromise to keep that decision where it's obviously in an 
early initcall, rather than in the helper function which can be viewed 
out of context. However, I'm happy to either expand this comment or go 
the whole way and make iommu_bus_init() return void if you think it's 
worthwhile.

Cheers,
Robin.

> 
>> +    for (int i = 0; i < ARRAY_SIZE(iommu_buses); i++)
>> +        iommu_bus_init(iommu_buses[i]);
>> +
>>       return 0;
> 
> Best regards,
> baolu

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-07-06 13:43 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:08 [PATCH v3 00/15] iommu: Retire bus_set_iommu() Robin Murphy
2022-07-05 17:08 ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 01/15] iommu/vt-d: Handle race between registration and device probe Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-06  1:39   ` Baolu Lu
2022-07-06  1:39     ` Baolu Lu
2022-07-07  6:51   ` Tian, Kevin
2022-07-07  6:51     ` Tian, Kevin
2022-07-08  7:52   ` Baolu Lu
2022-07-08  7:52     ` Baolu Lu
2022-07-15 12:37     ` Robin Murphy
2022-07-15 12:37       ` Robin Murphy
2022-07-19  0:06       ` Lu Baolu
2022-07-19  0:06         ` Lu Baolu
2022-07-05 17:08 ` [PATCH v3 02/15] iommu/amd: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 03/15] iommu: Always register bus notifiers Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-06  1:53   ` Baolu Lu
2022-07-06  1:53     ` Baolu Lu
2022-07-06 13:43     ` Robin Murphy [this message]
2022-07-06 13:43       ` Robin Murphy
2022-07-07  0:20       ` Baolu Lu
2022-07-07  0:20         ` Baolu Lu
2022-07-07  6:34         ` Tian, Kevin
2022-07-07  6:34           ` Tian, Kevin
2022-07-07  9:38           ` Robin Murphy
2022-07-07  9:38             ` Robin Murphy
2022-07-07  6:31   ` Tian, Kevin
2022-07-07  6:31     ` Tian, Kevin
2022-07-07  9:58     ` Robin Murphy
2022-07-07  9:58       ` Robin Murphy
2022-07-08  5:50       ` Tian, Kevin
2022-07-08  5:50         ` Tian, Kevin
2022-07-05 17:08 ` [PATCH v3 04/15] iommu: Move bus setup to IOMMU device registration Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-06  2:35   ` Baolu Lu
2022-07-06  2:35     ` Baolu Lu
2022-07-06 14:37     ` Robin Murphy
2022-07-06 14:37       ` Robin Murphy
2022-07-07  1:19       ` Baolu Lu
2022-07-07  1:19         ` Baolu Lu
2022-07-07  6:51   ` Tian, Kevin
2022-07-07  6:51     ` Tian, Kevin
2022-07-07 10:58     ` Robin Murphy
2022-07-07 10:58       ` Robin Murphy
2022-07-08  5:52       ` Tian, Kevin
2022-07-08  5:52         ` Tian, Kevin
2022-07-05 17:08 ` [PATCH v3 05/15] iommu/amd: Clean up bus_set_iommu() Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 06/15] iommu/arm-smmu: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 07/15] iommu/arm-smmu-v3: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 08/15] iommu/dart: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 09/15] iommu/exynos: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 10/15] iommu/ipmmu-vmsa: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 11/15] iommu/mtk: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 12/15] iommu/omap: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 13/15] iommu/tegra-smmu: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 14/15] iommu/virtio: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-05 17:08 ` [PATCH v3 15/15] iommu: " Robin Murphy
2022-07-05 17:08   ` Robin Murphy
2022-07-07  7:45   ` Tian, Kevin
2022-07-07  7:45     ` Tian, Kevin
2022-07-07 12:49   ` Matthew Rosato
2022-07-07 12:49     ` Matthew Rosato
2022-07-07 12:54     ` Matthew Rosato
2022-07-07 12:54       ` Matthew Rosato
2022-07-07 14:58       ` Robin Murphy
2022-07-07 14:58         ` Robin Murphy
2022-07-07 16:42         ` Matthew Rosato
2022-07-07 16:42           ` Matthew Rosato
2022-07-08  8:14     ` [PATCH] iommu/s390: fail probe for non-pci device Niklas Schnelle
2022-07-08  8:14       ` Niklas Schnelle
2022-07-08  8:17 ` [PATCH v3 00/15] iommu: Retire bus_set_iommu() Niklas Schnelle
2022-07-08  8:17   ` Niklas Schnelle
2022-07-15 13:12 ` Robin Murphy
2022-07-15 13:12   ` Robin Murphy
2022-07-21  7:17   ` Tian, Kevin
2022-07-21  7:17     ` Tian, Kevin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3d613192-f673-852e-9c52-b8a913d25616@arm.com \
    --to=robin.murphy@arm.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=schnelle@linux.ibm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.