mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: Nicolin Chen <nicolinc@nvidia.com>,
	joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org,
	robin.murphy@arm.com
Cc: jgg@nvidia.com, kevin.tian@intel.com, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 02/13] iommu/amd: Drop unnecessary checks in amd_iommu_attach_device()
Date: Wed, 14 Sep 2022 20:16:09 +0530	[thread overview]
Message-ID: <2430049f-bcb3-466b-fbed-03b4cd0e895a@amd.com> (raw)
In-Reply-To: <20220914051451.10304-1-nicolinc@nvidia.com>

On 9/14/2022 10:44 AM, Nicolin Chen wrote:
> The same checks are done in amd_iommu_probe_device(). If any of them fails
> there, then the device won't get a group, so there's no way for it to even
> reach amd_iommu_attach_device any more.
> 
> Suggested-by: Robin Murphy <robin.murphy@arm.com>
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>

Looks good to me.

Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>

-Vasant

> ---
>  drivers/iommu/amd/iommu.c | 12 ++----------
>  1 file changed, 2 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> index 828672a46a3d..930d9946b9f7 100644
> --- a/drivers/iommu/amd/iommu.c
> +++ b/drivers/iommu/amd/iommu.c
> @@ -2135,21 +2135,13 @@ static void amd_iommu_detach_device(struct iommu_domain *dom,
>  static int amd_iommu_attach_device(struct iommu_domain *dom,
>  				   struct device *dev)
>  {
> +	struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
>  	struct protection_domain *domain = to_pdomain(dom);
> -	struct iommu_dev_data *dev_data;
> -	struct amd_iommu *iommu;
> +	struct amd_iommu *iommu = rlookup_amd_iommu(dev);
>  	int ret;
>  
> -	if (!check_device(dev))
> -		return -EINVAL;
> -
> -	dev_data = dev_iommu_priv_get(dev);
>  	dev_data->defer_attach = false;
>  
> -	iommu = rlookup_amd_iommu(dev);
> -	if (!iommu)
> -		return -EINVAL;
> -
>  	if (dev_data->domain)
>  		detach_device(dev);
>  


      reply	other threads:[~2022-09-14 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  5:14 Nicolin Chen
2022-09-14 14:46 ` Vasant Hegde [this message]

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=2430049f-bcb3-466b-fbed-03b4cd0e895a@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®