From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org
Subject: [PULL REQUEST] iommu/vt-d: patches for v5.6
Date: Thu, 2 Jan 2020 08:18:01 +0800 [thread overview]
Message-ID: <20200102001823.21976-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
Below patches have been piled up for v5.6.
- Some preparation patches for VT-d nested mode support
- VT-d Native Shared virtual memory cleanup and fixes
- Use 1st-level for IOVA translation
- VT-d debugging and tracing
- Extend map_sg trace event for more information
- Add debugfs support to show page table internals
- Kconfig option for the default status of scalable mode
- Some miscellaneous cleanups.
Please consider them for the iommu/vt-d branch.
Best regards,
-baolu
Jacob Pan (8):
iommu/vt-d: Fix CPU and IOMMU SVM feature matching checks
iommu/vt-d: Match CPU and IOMMU paging mode
iommu/vt-d: Reject SVM bind for failed capability check
iommu/vt-d: Avoid duplicated code for PASID setup
iommu/vt-d: Fix off-by-one in PASID allocation
iommu/vt-d: Replace Intel specific PASID allocator with IOASID
iommu/vt-d: Avoid sending invalid page response
iommu/vt-d: Misc macro clean up for SVM
Lu Baolu (14):
iommu/vt-d: Add Kconfig option to enable/disable scalable mode
iommu/vt-d: trace: Extend map_sg trace event
iommu/vt-d: Avoid iova flush queue in strict mode
iommu/vt-d: Loose requirement for flush queue initializaton
iommu/vt-d: Identify domains using first level page table
iommu/vt-d: Add set domain DOMAIN_ATTR_NESTING attr
iommu/vt-d: Add PASID_FLAG_FL5LP for first-level pasid setup
iommu/vt-d: Setup pasid entries for iova over first level
iommu/vt-d: Flush PASID-based iotlb for iova over first level
iommu/vt-d: Make first level IOVA canonical
iommu/vt-d: Update first level super page capability
iommu/vt-d: Use iova over first level
iommu/vt-d: debugfs: Add support to show page table internals
iommu/vt-d: Add a quirk flag for scope mismatched devices
drivers/iommu/Kconfig | 13 ++
drivers/iommu/dmar.c | 78 +++++--
drivers/iommu/intel-iommu-debugfs.c | 75 +++++++
drivers/iommu/intel-iommu.c | 305 +++++++++++++++++++++++-----
drivers/iommu/intel-pasid.c | 97 +++------
drivers/iommu/intel-pasid.h | 6 +
drivers/iommu/intel-svm.c | 171 +++++++++-------
include/linux/intel-iommu.h | 25 ++-
include/trace/events/intel_iommu.h | 48 ++++-
9 files changed, 593 insertions(+), 225 deletions(-)
--
2.17.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-01-02 0:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 0:18 Lu Baolu [this message]
2020-01-02 0:18 ` [PATCH 01/22] iommu/vt-d: Add Kconfig option to enable/disable scalable mode Lu Baolu
2020-01-02 0:18 ` [PATCH 02/22] iommu/vt-d: Fix CPU and IOMMU SVM feature matching checks Lu Baolu
2020-01-02 0:18 ` [PATCH 03/22] iommu/vt-d: Match CPU and IOMMU paging mode Lu Baolu
2020-01-02 0:18 ` [PATCH 04/22] iommu/vt-d: Reject SVM bind for failed capability check Lu Baolu
2020-01-02 0:18 ` [PATCH 05/22] iommu/vt-d: Avoid duplicated code for PASID setup Lu Baolu
2020-01-02 0:18 ` [PATCH 06/22] iommu/vt-d: Fix off-by-one in PASID allocation Lu Baolu
2020-01-02 0:18 ` [PATCH 07/22] iommu/vt-d: Replace Intel specific PASID allocator with IOASID Lu Baolu
2020-01-02 0:18 ` [PATCH 08/22] iommu/vt-d: Avoid sending invalid page response Lu Baolu
2020-01-02 0:18 ` [PATCH 09/22] iommu/vt-d: Misc macro clean up for SVM Lu Baolu
2020-01-02 0:18 ` [PATCH 10/22] iommu/vt-d: trace: Extend map_sg trace event Lu Baolu
2020-01-02 0:18 ` [PATCH 11/22] iommu/vt-d: Avoid iova flush queue in strict mode Lu Baolu
2020-01-02 0:18 ` [PATCH 12/22] iommu/vt-d: Loose requirement for flush queue initializaton Lu Baolu
2020-01-02 0:18 ` [PATCH 13/22] iommu/vt-d: Identify domains using first level page table Lu Baolu
2020-01-02 0:18 ` [PATCH 14/22] iommu/vt-d: Add set domain DOMAIN_ATTR_NESTING attr Lu Baolu
2020-01-02 0:18 ` [PATCH 15/22] iommu/vt-d: Add PASID_FLAG_FL5LP for first-level pasid setup Lu Baolu
2020-01-02 0:18 ` [PATCH 16/22] iommu/vt-d: Setup pasid entries for iova over first level Lu Baolu
2020-01-02 0:18 ` [PATCH 17/22] iommu/vt-d: Flush PASID-based iotlb " Lu Baolu
2020-01-02 0:18 ` [PATCH 18/22] iommu/vt-d: Make first level IOVA canonical Lu Baolu
2020-01-02 0:18 ` [PATCH 19/22] iommu/vt-d: Update first level super page capability Lu Baolu
2020-01-02 0:18 ` [PATCH 20/22] iommu/vt-d: Use iova over first level Lu Baolu
2020-01-02 0:18 ` [PATCH 21/22] iommu/vt-d: debugfs: Add support to show page table internals Lu Baolu
2020-01-02 0:18 ` [PATCH 22/22] iommu/vt-d: Add a quirk flag for scope mismatched devices Lu Baolu
2020-01-02 2:11 ` Roland Dreier via iommu
2020-01-02 2:14 ` Lu Baolu
2020-01-02 2:25 ` Roland Dreier via iommu
2020-01-02 2:34 ` Lu Baolu
2020-01-03 0:32 ` Lu Baolu
2020-01-04 16:52 ` Roland Dreier via iommu
2020-01-05 3:43 ` Lu Baolu
2020-01-06 17:05 ` Jerry Snitselaar
2020-01-07 0:35 ` Lu Baolu
2020-01-07 1:30 ` Jerry Snitselaar
2020-01-07 1:47 ` Lu Baolu
2020-01-09 0:12 ` Roland Dreier via iommu
2020-01-08 14:16 ` Christoph Hellwig
2020-01-08 23:28 ` Lu Baolu
2020-01-09 7:06 ` Christoph Hellwig
2020-01-09 8:53 ` Lu Baolu
2020-01-09 8:56 ` 答复: " Jim,Yan
2020-01-07 13:06 ` [PULL REQUEST] iommu/vt-d: patches for v5.6 Joerg Roedel
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=20200102001823.21976-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox