public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	iommu@lists.linux.dev, Jason Gunthorpe <jgg@nvidia.com>,
	Joerg Roedel <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	dmaengine@vger.kernel.org, vkoul@kernel.org,
	Will Deacon <will@kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Raj Ashok <ashok.raj@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Tony Luck <tony.luck@intel.com>,
	"Zanussi, Tom" <tom.zanussi@intel.com>,
	rex.zhang@intel.com, xiaochen.shen@intel.com,
	narayan.ranganathan@intel.com, jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v9 0/7] Re-enable IDXD kernel workqueue under DMA API
Date: Tue, 11 Jul 2023 22:51:11 -0700	[thread overview]
Message-ID: <20230711225111.567894c8@jacob-builder> (raw)
In-Reply-To: <d6399f56-0528-d923-910c-822611137e2d@linux.intel.com>

Hi Baolu,

On Tue, 11 Jul 2023 10:29:10 +0800, Baolu Lu <baolu.lu@linux.intel.com>
wrote:

> >> Changelog:
> >> v9:
> >> 	- Fix an IDXD driver issue where user interrupt enable bit got
> >> cleared during device enable/disable cycle. Reported and tested by
> >> 	  Tony Zhu<tony.zhu@intel.com>
> >> 	- Rebased to v6.4-rc7  
> 
> Thanks for fixing this.
> 
> It seems that you missed some review comments for v8. I can help to test
> and merge when all comments are addressed.
Right, I missed the max_pasid = 0 case as you pointed out. Let me respin
the set and do some testing on my side as well.

Thanks,

Jacob

      reply	other threads:[~2023-07-12  5:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 20:59 [PATCH v9 0/7] Re-enable IDXD kernel workqueue under DMA API Jacob Pan
2023-06-21 20:59 ` [PATCH v9 1/7] iommu: Generalize PASID 0 for normal DMA w/o PASID Jacob Pan
2023-06-21 20:59 ` [PATCH v9 2/7] iommu: Move global PASID allocation from SVA to core Jacob Pan
2023-06-21 20:59 ` [PATCH v9 3/7] iommu/vt-d: Add domain_flush_pasid_iotlb() Jacob Pan
2023-06-21 20:59 ` [PATCH v9 4/7] iommu/vt-d: Remove pasid_mutex Jacob Pan
2023-06-21 20:59 ` [PATCH v9 5/7] iommu/vt-d: Make prq draining code generic Jacob Pan
2023-06-21 20:59 ` [PATCH v9 6/7] iommu/vt-d: Add set_dev_pasid callback for dma domain Jacob Pan
2023-06-21 20:59 ` [PATCH v9 7/7] dmaengine/idxd: Re-enable kernel workqueue under DMA API Jacob Pan
2023-07-10 17:18 ` [PATCH v9 0/7] Re-enable IDXD " Jacob Pan
2023-07-11  2:29   ` Baolu Lu
2023-07-12  5:51     ` Jacob Pan [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=20230711225111.567894c8@jacob-builder \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux.dev \
    --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=narayan.ranganathan@intel.com \
    --cc=rex.zhang@intel.com \
    --cc=robin.murphy@arm.com \
    --cc=tom.zanussi@intel.com \
    --cc=tony.luck@intel.com \
    --cc=vkoul@kernel.org \
    --cc=will@kernel.org \
    --cc=xiaochen.shen@intel.com \
    --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