Linux IOMMU Development
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Jann Horn <jannh@google.com>,
	Vasant Hegde <vasant.hegde@amd.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Alistair Popple <apopple@nvidia.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Andy Lutomirski <luto@kernel.org>,
	"Tested-by : Yi Lai" <yi1.lai@intel.com>,
	iommu@lists.linux.dev, security@kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] iommu/sva: Invalidate KVA range on kernel TLB flush
Date: Thu, 10 Jul 2025 17:53:19 +0200	[thread overview]
Message-ID: <20250710155319.GK1613633@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250710135432.GO1613376@noisy.programming.kicks-ass.net>

On Thu, Jul 10, 2025 at 03:54:32PM +0200, Peter Zijlstra wrote:

> > @@ -132,8 +136,15 @@ struct iommu_sva *iommu_sva_bind_device(struct device *dev, struct mm_struct *mm
> >  	if (ret)
> >  		goto out_free_domain;
> >  	domain->users = 1;
> > -	list_add(&domain->next, &mm->iommu_mm->sva_domains);
> >  
> > +	if (list_empty(&iommu_mm->sva_domains)) {
> > +		scoped_guard(spinlock_irqsave, &iommu_mms_lock) {
> > +			if (list_empty(&iommu_sva_mms))
> > +				static_branch_enable(&iommu_sva_present);
> > +			list_add(&iommu_mm->mm_list_elm, &iommu_sva_mms);
> > +		}
> > +	}
> > +	list_add(&domain->next, &iommu_mm->sva_domains);
> >  out:
> >  	refcount_set(&handle->users, 1);
> >  	mutex_unlock(&iommu_sva_lock);
> > @@ -175,6 +186,15 @@ void iommu_sva_unbind_device(struct iommu_sva *handle)
> >  		list_del(&domain->next);
> >  		iommu_domain_free(domain);
> >  	}
> > +
> > +	if (list_empty(&iommu_mm->sva_domains)) {
> > +		scoped_guard(spinlock_irqsave, &iommu_mms_lock) {
> > +			list_del(&iommu_mm->mm_list_elm);
> > +			if (list_empty(&iommu_sva_mms))
> > +				static_branch_disable(&iommu_sva_present);
> > +		}
> > +	}
> > +
> >  	mutex_unlock(&iommu_sva_lock);
> >  	kfree(handle);
> >  }
> 
> This seems an odd coding style choice; why the extra unneeded
> indentation? That is, what's wrong with:
> 
> 	if (list_empty()) {
> 		guard(spinlock_irqsave)(&iommu_mms_lock);
> 		list_del();
> 		if (list_empty()
> 			static_branch_disable();
> 	}

Well, for one, you can't do static_branch_{en,dis}able() from atomic
context...

Was this ever tested?

  reply	other threads:[~2025-07-10 15:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09  6:28 [PATCH v2 1/1] iommu/sva: Invalidate KVA range on kernel TLB flush Lu Baolu
2025-07-09 15:29 ` Dave Hansen
2025-07-10  2:14   ` Baolu Lu
2025-07-10  2:55     ` Tian, Kevin
2025-07-10 12:53     ` Dave Hansen
2025-07-10 13:22       ` Jason Gunthorpe
2025-07-10 15:26         ` Dave Hansen
2025-07-11  2:46           ` Tian, Kevin
2025-07-11  2:54           ` Tian, Kevin
2025-07-11  8:17           ` Yu Zhang
2025-07-24  3:01             ` Baolu Lu
2025-07-28 17:36               ` Yu Zhang
2025-07-29  2:08                 ` Baolu Lu
2025-07-24  3:06           ` Baolu Lu
2025-07-11  2:49         ` Tian, Kevin
2025-07-10  3:02 ` Tian, Kevin
2025-07-10  8:11   ` Yu Zhang
2025-07-10  8:15     ` Tian, Kevin
2025-07-10  9:37       ` Yu Zhang
2025-07-10 13:54 ` Peter Zijlstra
2025-07-10 15:53   ` Peter Zijlstra [this message]
2025-07-11  3:09     ` Baolu Lu
2025-07-11  8:27       ` Peter Zijlstra
2025-07-16 11:57     ` David Laight
2025-07-17  1:47       ` Baolu Lu
2025-07-11  3:00   ` Baolu Lu
2025-07-11  4:01     ` Tian, Kevin
2025-07-11  8:32     ` Peter Zijlstra
2025-07-11 11:58       ` Jason Gunthorpe
2025-07-15  5:55       ` Baolu Lu
2025-07-15 12:25         ` Jason Gunthorpe
2025-07-16  6:34           ` Baolu Lu
2025-07-16 12:08             ` Jason Gunthorpe
2025-07-17  1:43               ` Baolu Lu
2025-07-17 11:50                 ` Vasant Hegde
2025-07-11 11:54     ` Jason Gunthorpe
2025-07-16 10:54 ` Yi Liu
2025-07-17  1:51   ` Baolu Lu

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=20250710155319.GK1613633@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=apopple@nvidia.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dave.hansen@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jannh@google.com \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=security@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=urezki@gmail.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@kernel.org \
    --cc=yi1.lai@intel.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