From: Vasant Hegde <vasant.hegde@amd.com>
To: Li RongQing <lirongqing@baidu.com>,
iommu@lists.linux.dev, robin.murphy@arm.com, will@kernel.org,
joro@8bytes.org
Subject: Re: [PATCH] iommu: move the adding group info to proper place
Date: Mon, 6 Jan 2025 16:25:22 +0530 [thread overview]
Message-ID: <ac420b8a-cd5b-41dc-8a4d-247f560a9043@amd.com> (raw)
In-Reply-To: <20250103052811.39544-1-lirongqing@baidu.com>
On 1/3/2025 10:58 AM, Li RongQing wrote:
> After commit fa0828036488 ("iommu: Split iommu_group_add_device()"), the
> adding group information is left in iommu_group_alloc_device, but which
> only allocate group device, not attach the device to iommu group;
>
> so move the print to iommu probing and adding functions
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> drivers/iommu/iommu.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 599030e..03f95f2 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -586,6 +586,9 @@ static int __iommu_probe_device(struct device *dev, struct list_head *group_list
>
> mutex_unlock(&group->mutex);
>
> + trace_add_device_to_group(group->id, dev);
> + dev_info(dev, "Adding to iommu group %d\n", group->id);
> +
> return 0;
>
> err_remove_gdev:
> @@ -594,6 +597,7 @@ static int __iommu_probe_device(struct device *dev, struct list_head *group_list
> err_put_group:
> iommu_deinit_device(dev);
> mutex_unlock(&group->mutex);
> + dev_err(dev, "Failed to add to iommu group %d: %d\n", group->id, ret);
> iommu_group_put(group);
>
> return ret;
> @@ -1192,10 +1196,6 @@ static struct group_device *iommu_group_alloc_device(struct iommu_group *group,
> goto err_free_name;
> }
>
> - trace_add_device_to_group(group->id, dev);
> -
> - dev_info(dev, "Adding to iommu group %d\n", group->id);
> -
> return device;
>
> err_free_name:
> @@ -1204,7 +1204,6 @@ static struct group_device *iommu_group_alloc_device(struct iommu_group *group,
> sysfs_remove_link(&dev->kobj, "iommu_group");
> err_free_device:
> kfree(device);
> - dev_err(dev, "Failed to add to iommu group %d: %d\n", group->id, ret);
> return ERR_PTR(ret);
> }
>
> @@ -1230,6 +1229,10 @@ int iommu_group_add_device(struct iommu_group *group, struct device *dev)
Add error message if iommu_group_alloc_device() fails here?
-Vasant
next prev parent reply other threads:[~2025-01-06 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 5:28 [PATCH] iommu: move the adding group info to proper place Li RongQing
2025-01-06 1:06 ` Baolu Lu
2025-01-06 10:55 ` Vasant Hegde [this message]
2025-01-06 12:15 ` 答复: [外部邮件] " Li,Rongqing
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=ac420b8a-cd5b-41dc-8a4d-247f560a9043@amd.com \
--to=vasant.hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lirongqing@baidu.com \
--cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox