Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Joerg Roedel <joro@8bytes.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	Robin Murphy <robin.murphy@arm.com>
Cc: baolu.lu@linux.intel.com, Jason Gunthorpe <jgg@nvidia.com>,
	Will Deacon <will@kernel.org>, "Liu, Yi L" <yi.l.liu@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [PATCH v10 3/7] iommu/vt-d: Add domain_flush_pasid_iotlb()
Date: Fri, 14 Jul 2023 14:02:19 +0800	[thread overview]
Message-ID: <2753b770-564a-b141-1505-94f08016abc5@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB5276DBFD837A82AF61DF00D28C34A@BN9PR11MB5276.namprd11.prod.outlook.com>

On 2023/7/14 11:51, Tian, Kevin wrote:
>> From: Baolu Lu <baolu.lu@linux.intel.com>
>> Sent: Friday, July 14, 2023 11:37 AM
>>
>> On 2023/7/13 15:52, Tian, Kevin wrote:
>>>> From: Jacob Pan <jacob.jun.pan@linux.intel.com>
>>>> Sent: Thursday, July 13, 2023 12:34 AM
>>>> +static void domain_flush_pasid_iotlb(struct intel_iommu *iommu,
>>>> +				     struct dmar_domain *domain, u64 addr,
>>>> +				     unsigned long npages, bool ih)
>>>> +{
>>>> +	u16 did = domain_id_iommu(domain, iommu);
>>>> +	unsigned long flags;
>>>> +
>>>> +	spin_lock_irqsave(&domain->lock, flags);
>>>> +	if (!list_empty(&domain->devices))
>>>> +		qi_flush_piotlb(iommu, did, IOMMU_NO_PASID, addr,
>>>> npages, ih);
>>>> +	spin_unlock_irqrestore(&domain->lock, flags);
>>>
>>> btw I gave a comment before that the check of list_empty() changes
>>> the semantics instead of just creating a helper.
>>>
>>> If it's the right thing to do please split it into a separate fix patch.
>>
>> Perhaps move it into patch 6?
>>
> 
> I still prefer to putting it in a separate patch since it changes the
> behavior in existing path. It's not really about dev_pasid which
> patch6 is trying to support.

Okay, that will also be fine to me.

Best regards,
baolu

  reply	other threads:[~2023-07-14  6:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 16:33 [PATCH v10 0/7] Re-enable IDXD kernel workqueue under DMA API Jacob Pan
2023-07-12 16:33 ` [PATCH v10 1/7] iommu: Generalize PASID 0 for normal DMA w/o PASID Jacob Pan
2023-07-12 16:33 ` [PATCH v10 2/7] iommu: Move global PASID allocation from SVA to core Jacob Pan
2023-07-13  7:42   ` Tian, Kevin
2023-07-13 16:00     ` Jacob Pan
2023-07-12 16:33 ` [PATCH v10 3/7] iommu/vt-d: Add domain_flush_pasid_iotlb() Jacob Pan
2023-07-13  7:45   ` Tian, Kevin
2023-07-13  7:52   ` Tian, Kevin
2023-07-14  3:36     ` Baolu Lu
2023-07-14  3:51       ` Tian, Kevin
2023-07-14  6:02         ` Baolu Lu [this message]
2023-07-12 16:33 ` [PATCH v10 4/7] iommu/vt-d: Remove pasid_mutex Jacob Pan
2023-07-13  7:46   ` Tian, Kevin
2023-07-12 16:33 ` [PATCH v10 5/7] iommu/vt-d: Make prq draining code generic Jacob Pan
2023-07-13  7:49   ` Tian, Kevin
2023-07-14  3:28     ` Baolu Lu
2023-07-14  3:49       ` Tian, Kevin
2023-07-14  5:47         ` Baolu Lu
2023-07-19  5:39           ` Tian, Kevin
2023-07-19  7:40             ` Baolu Lu
2023-07-12 16:33 ` [PATCH v10 6/7] iommu/vt-d: Add set_dev_pasid callback for dma domain Jacob Pan
2023-07-13  7:56   ` Tian, Kevin
2023-07-14  3:34     ` Baolu Lu
2023-07-14  3:50       ` Tian, Kevin
2023-07-14  6:00         ` Baolu Lu
2023-07-19  5:39           ` Tian, Kevin
2023-07-12 16:33 ` [PATCH v10 7/7] dmaengine/idxd: Re-enable kernel workqueue under DMA API Jacob Pan

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=2753b770-564a-b141-1505-94f08016abc5@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jean-philippe@linaro.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tony.luck@intel.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@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