From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux.dev, "Lu Baolu" <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>,
Jean-Philippe Brucker <jean-philippe@linaro.com>,
"Robin Murphy" <robin.murphy@arm.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>, "Will Deacon" <will@kernel.org>,
"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
Tony Luck <tony.luck@intel.com>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v11 0/8] Re-enable IDXD kernel workqueue under DMA API
Date: Wed, 2 Aug 2023 07:53:57 -0700 [thread overview]
Message-ID: <20230802075357.536a8508@jacob-builder> (raw)
In-Reply-To: <20230724222538.3902553-1-jacob.jun.pan@linux.intel.com>
Hi Joerg/Baolu,
Any more comments on this series? Thanks
On Mon, 24 Jul 2023 15:25:30 -0700, Jacob Pan
<jacob.jun.pan@linux.intel.com> wrote:
> Hi Joerg and all,
>
> IDXD kernel work queues were disabled due to the flawed use of kernel VA
> and SVA API.
> Link:
> https://lore.kernel.org/linux-iommu/20210511194726.GP1002214@nvidia.com/
>
> The solution is to enable it under DMA API where IDXD shared workqueue
> users can use ENQCMDS to submit work on buffers mapped by DMA API.
>
> This patchset adds support for attaching PASID to the device's default
> domain and the ability to allocate global PASIDs from IOMMU APIs. IDXD
> driver can then re-enable the kernel work queues and use them under DMA
> API.
>
> This depends on the IOASID removal series. (merged)
> https://lore.kernel.org/all/ZCaUBJvUMsJyD7EW@8bytes.org/
>
>
> Thanks,
>
> Jacob
>
> ---
> Changelog:
> v11:
> - Rebased onto Joerg's next tree (v6.5-rc1)
> - Split RIDPASID check in invalidation code into patch (6/8)
> - Renamed iommu_alloc_global_pasid_dev to
> iommu_alloc_global_pasid (2/8)
> - Added WARN_ON if no dev_pasid is found during remove (7/8)
> v10:
> - Fix global PASID alloc function with device's max_pasid=0
> 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
> v8:
> - further vt-d driver refactoring (3-6) around set/remove device
> PASID (Baolu)
> - make consistent use of NO_PASID in SMMU code (Jean)
> - fix off-by-one error in max PASID check (Kevin)
> v7:
> - renamed IOMMU_DEF_RID_PASID to be IOMMU_NO_PASID to be more
> generic (Jean)
> - simplify range checking for sva PASID (Baolu)
> v6:
> - use a simplified version of vt-d driver change for
> set_device_pasid from Baolu.
> - check and rename global PASID allocation base
> v5:
> - exclude two patches related to supervisor mode, taken by VT-d
> maintainer Baolu.
> - move PASID range check into allocation API so that device
> drivers only need to pass in struct device*. (Kevin)
> - factor out helper functions in device-domain attach (Baolu)
> - make explicit use of RID_PASID across architectures
> v4:
> - move dummy functions outside ifdef CONFIG_IOMMU_SVA (Baolu)
> - dropped domain type check while disabling idxd system PASID
> (Baolu)
>
> v3:
> - moved global PASID allocation API from SVA to IOMMU (Kevin)
> - remove #ifdef around global PASID reservation during boot
> (Baolu)
> - remove restriction on PASID 0 allocation (Baolu)
> - fix a bug in sysfs domain change when attaching devices
> - clear idxd user interrupt enable bit after disabling device(
> Fenghua) v2:
> - refactored device PASID attach domain ops based on Baolu's
> early patch
> - addressed TLB flush gap
> - explicitly reserve RID_PASID from SVA PASID number space
> - get dma domain directly, avoid checking domain types
>
>
>
> Jacob Pan (3):
> iommu: Generalize PASID 0 for normal DMA w/o PASID
> iommu: Move global PASID allocation from SVA to core
> dmaengine/idxd: Re-enable kernel workqueue under DMA API
>
> Lu Baolu (5):
> iommu/vt-d: Add domain_flush_pasid_iotlb()
> iommu/vt-d: Remove pasid_mutex
> iommu/vt-d: Make prq draining code generic
> iommu/vt-d: Prepare for set_dev_pasid callback
> iommu/vt-d: Add set_dev_pasid callback for dma domain
>
> drivers/dma/idxd/device.c | 39 ++---
> drivers/dma/idxd/dma.c | 5 +-
> drivers/dma/idxd/idxd.h | 9 +
> drivers/dma/idxd/init.c | 54 +++++-
> drivers/dma/idxd/sysfs.c | 7 -
> .../iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c | 2 +-
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 16 +-
> drivers/iommu/intel/iommu.c | 157 +++++++++++++++---
> drivers/iommu/intel/iommu.h | 9 +
> drivers/iommu/intel/pasid.c | 2 +-
> drivers/iommu/intel/pasid.h | 2 -
> drivers/iommu/intel/svm.c | 62 +------
> drivers/iommu/iommu-sva.c | 29 ++--
> drivers/iommu/iommu.c | 28 ++++
> include/linux/iommu.h | 11 ++
> 15 files changed, 287 insertions(+), 145 deletions(-)
>
Thanks,
Jacob
prev parent reply other threads:[~2023-08-02 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 22:25 [PATCH v11 0/8] Re-enable IDXD kernel workqueue under DMA API Jacob Pan
2023-07-24 22:25 ` [PATCH v11 1/8] iommu: Generalize PASID 0 for normal DMA w/o PASID Jacob Pan
2023-07-24 22:25 ` [PATCH v11 2/8] iommu: Move global PASID allocation from SVA to core Jacob Pan
2023-08-02 14:48 ` Jason Gunthorpe
2023-08-02 20:55 ` Jacob Pan
2023-07-24 22:25 ` [PATCH v11 3/8] iommu/vt-d: Add domain_flush_pasid_iotlb() Jacob Pan
2023-07-24 22:25 ` [PATCH v11 4/8] iommu/vt-d: Remove pasid_mutex Jacob Pan
2023-07-24 22:25 ` [PATCH v11 5/8] iommu/vt-d: Make prq draining code generic Jacob Pan
2023-07-27 5:48 ` Tian, Kevin
2023-07-24 22:25 ` [PATCH v11 6/8] iommu/vt-d: Prepare for set_dev_pasid callback Jacob Pan
2023-07-27 5:48 ` Tian, Kevin
2023-07-24 22:25 ` [PATCH v11 7/8] iommu/vt-d: Add set_dev_pasid callback for dma domain Jacob Pan
2023-07-27 5:48 ` Tian, Kevin
2023-07-24 22:25 ` [PATCH v11 8/8] dmaengine/idxd: Re-enable kernel workqueue under DMA API Jacob Pan
2023-08-02 14:51 ` Jason Gunthorpe
2023-08-02 14:52 ` [PATCH v11 0/8] Re-enable IDXD " Jason Gunthorpe
2023-08-02 14:53 ` 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=20230802075357.536a8508@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.