Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: <cohuck@redhat.com>, <kvm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <wanghaibin.wang@huawei.com>
Subject: Re: [PATCH] vfio/type1: Use the new helper to find vfio_group
Date: Tue, 3 Nov 2020 11:18:01 -0700	[thread overview]
Message-ID: <20201103111801.05d4cee5@w520.home> (raw)
In-Reply-To: <20201022122417.245-1-yuzenghui@huawei.com>

On Thu, 22 Oct 2020 20:24:17 +0800
Zenghui Yu <yuzenghui@huawei.com> wrote:

> When attaching a new group to the container, let's use the new helper
> vfio_iommu_find_iommu_group() to check if it's already attached. There
> is no functional change.
> 
> Also take this chance to add a missing blank line.
> 
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
>  drivers/vfio/vfio_iommu_type1.c | 17 +++++------------
>  1 file changed, 5 insertions(+), 12 deletions(-)


Applied to vfio for-linus branch for v5.10.  Thanks,

Alex

> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index a05d856ae806..aa586bd684da 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -1997,6 +1997,7 @@ static void vfio_iommu_iova_insert_copy(struct vfio_iommu *iommu,
>  
>  	list_splice_tail(iova_copy, iova);
>  }
> +
>  static int vfio_iommu_type1_attach_group(void *iommu_data,
>  					 struct iommu_group *iommu_group)
>  {
> @@ -2013,18 +2014,10 @@ static int vfio_iommu_type1_attach_group(void *iommu_data,
>  
>  	mutex_lock(&iommu->lock);
>  
> -	list_for_each_entry(d, &iommu->domain_list, next) {
> -		if (find_iommu_group(d, iommu_group)) {
> -			mutex_unlock(&iommu->lock);
> -			return -EINVAL;
> -		}
> -	}
> -
> -	if (iommu->external_domain) {
> -		if (find_iommu_group(iommu->external_domain, iommu_group)) {
> -			mutex_unlock(&iommu->lock);
> -			return -EINVAL;
> -		}
> +	/* Check for duplicates */
> +	if (vfio_iommu_find_iommu_group(iommu, iommu_group)) {
> +		mutex_unlock(&iommu->lock);
> +		return -EINVAL;
>  	}
>  
>  	group = kzalloc(sizeof(*group), GFP_KERNEL);


      reply	other threads:[~2020-11-03 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 12:24 [PATCH] vfio/type1: Use the new helper to find vfio_group Zenghui Yu
2020-11-03 18:18 ` Alex Williamson [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=20201103111801.05d4cee5@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wanghaibin.wang@huawei.com \
    --cc=yuzenghui@huawei.com \
    /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