All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Tom Murphy <murphyt7@tcd.ie>,
	David Woodhouse <dwmw2@infradead.org>,
	Christoph Hellwig <hch@infradead.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	iommu@lists.linux-foundation.org, Ashok Raj <ashok.raj@intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/7] Convert the intel iommu driver to the dma-iommu api
Date: Fri, 20 Nov 2020 18:17:12 +0800	[thread overview]
Message-ID: <20201120101719.3172693-1-baolu.lu@linux.intel.com> (raw)

Hi Will,

The previous post of this series could be found here.

https://lore.kernel.org/linux-iommu/20200927063437.13988-1-baolu.lu@linux.intel.com/

Changes in this version:
- Add Tested-by: Logan Gunthorpe <logang@deltatee.com>
- Rebase to v5.10-rc3

Please review and consider it for iommu/next.

Best regards,
baolu

Lu Baolu (3):
  iommu: Add quirk for Intel graphic devices in map_sg
  iommu/vt-d: Update domain geometry in iommu_ops.at(de)tach_dev
  iommu/vt-d: Cleanup after converting to dma-iommu ops

Tom Murphy (4):
  iommu: Handle freelists when using deferred flushing in iommu drivers
  iommu: Add iommu_dma_free_cpu_cached_iovas()
  iommu: Allow the dma-iommu api to use bounce buffers
  iommu/vt-d: Convert intel iommu driver to the iommu ops

 .../admin-guide/kernel-parameters.txt         |   5 -
 drivers/iommu/dma-iommu.c                     | 228 ++++-
 drivers/iommu/intel/Kconfig                   |   1 +
 drivers/iommu/intel/iommu.c                   | 905 +++---------------
 include/linux/dma-iommu.h                     |   8 +
 include/linux/iommu.h                         |   1 +
 6 files changed, 336 insertions(+), 812 deletions(-)

-- 
2.25.1

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2020-11-20 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 10:17 Lu Baolu [this message]
2020-11-20 10:17 ` [PATCH v5 1/7] iommu: Handle freelists when using deferred flushing in iommu drivers Lu Baolu
2020-11-20 10:17 ` [PATCH v5 2/7] iommu: Add iommu_dma_free_cpu_cached_iovas() Lu Baolu
2020-11-20 10:17 ` [PATCH v5 3/7] iommu: Allow the dma-iommu api to use bounce buffers Lu Baolu
2020-11-23 10:08   ` Christoph Hellwig
2020-11-23 11:40     ` Lu Baolu
2020-11-23 11:47       ` Will Deacon
2020-11-23 11:56         ` Lu Baolu
2020-11-20 10:17 ` [PATCH v5 4/7] iommu: Add quirk for Intel graphic devices in map_sg Lu Baolu
2020-11-20 10:17 ` [PATCH v5 5/7] iommu/vt-d: Update domain geometry in iommu_ops.at(de)tach_dev Lu Baolu
2020-11-20 10:17 ` [PATCH v5 6/7] iommu/vt-d: Convert intel iommu driver to the iommu ops Lu Baolu
2020-11-20 10:17 ` [PATCH v5 7/7] iommu/vt-d: Cleanup after converting to dma-iommu ops Lu Baolu
2020-11-20 12:24 ` [PATCH v5 0/7] Convert the intel iommu driver to the dma-iommu api Chris Wilson
2020-11-20 13:39   ` Lu Baolu

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=20201120101719.3172693-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murphyt7@tcd.ie \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=will@kernel.org \
    /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.