From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Aditya Srivastava <yashsri421@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
YueHaibing <yuehaibing@huawei.com>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
iommu@lists.linux-foundation.org,
Colin Ian King <colin.king@canonical.com>,
Will Deacon <will@kernel.org>
Subject: [PATCH 00/23] [PULL REQUEST] Intel IOMMU Updates for Linux v5.14
Date: Thu, 10 Jun 2021 10:00:52 +0800 [thread overview]
Message-ID: <20210610020115.1637656-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The patches queued in this series are for v5.14.
It includes:
- Convert Intel IOMMU to use sva_lib helpers in iommu core
- ftrace and debugfs supports for page fault handling
- Support asynchronous nested capabilities
- Various misc cleanups
Please pull.
Best regards,
Baolu
Aditya Srivastava (1):
iommu/vt-d: Fix kernel-doc syntax in file header
Colin Ian King (1):
iommu/vt-d: Remove redundant assignment to variable agaw
Gustavo A. R. Silva (1):
iommu/vt-d: Fix out-bounds-warning in intel/svm.c
Lu Baolu (14):
iommu/vt-d: Tweak the description of a DMA fault
iommu/vt-d: Select PCI_ATS explicitly
iommu/vt-d: Support asynchronous IOMMU nested capabilities
iommu/vt-d: Add pasid private data helpers
iommu/vt-d: Use iommu_sva_alloc(free)_pasid() helpers
iommu/vt-d: Use common helper to lookup svm devices
iommu/vt-d: Refactor prq_event_thread()
iommu/vt-d: Allocate/register iopf queue for sva devices
iommu/vt-d: Report prq to io-pgfault framework
iommu/vt-d: Add prq_report trace event
iommu/vt-d: Add common code for dmar latency performance monitors
iommu/vt-d: Expose latency monitor data through debugfs
iommu/vt-d: Add cache invalidation latency sampling
iommu/vt-d: Add PRQ handling latency sampling
Parav Pandit (5):
iommu/vt-d: Use bitfields for DMAR capabilities
iommu/vt-d: Removed unused iommu_count in dmar domain
iommu/vt-d: Remove unnecessary braces
iommu/vt-d: Define counter explicitly as unsigned int
iommu/vt-d: No need to typecast
YueHaibing (1):
iommu/vt-d: Use DEVICE_ATTR_RO macro
include/linux/intel-iommu.h | 44 +-
drivers/iommu/intel/perf.h | 73 ++++
include/trace/events/intel_iommu.h | 37 ++
drivers/iommu/intel/debugfs.c | 111 +++++
drivers/iommu/intel/dmar.c | 54 ++-
drivers/iommu/intel/iommu.c | 163 +++++---
drivers/iommu/intel/pasid.c | 2 +-
drivers/iommu/intel/perf.c | 166 ++++++++
drivers/iommu/intel/svm.c | 643 ++++++++++++++---------------
drivers/iommu/intel/Kconfig | 6 +
drivers/iommu/intel/Makefile | 1 +
11 files changed, 894 insertions(+), 406 deletions(-)
create mode 100644 drivers/iommu/intel/perf.h
create mode 100644 drivers/iommu/intel/perf.c
--
2.25.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2021-06-10 2:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 2:00 Lu Baolu [this message]
2021-06-10 2:00 ` [PATCH 01/23] iommu/vt-d: Remove redundant assignment to variable agaw Lu Baolu
2021-06-10 2:00 ` [PATCH 02/23] iommu/vt-d: Fix kernel-doc syntax in file header Lu Baolu
2021-06-10 2:00 ` [PATCH 03/23] iommu/vt-d: Tweak the description of a DMA fault Lu Baolu
2021-06-10 2:00 ` [PATCH 04/23] iommu/vt-d: Select PCI_ATS explicitly Lu Baolu
2021-06-10 2:00 ` [PATCH 05/23] iommu/vt-d: Support asynchronous IOMMU nested capabilities Lu Baolu
2021-06-10 2:00 ` [PATCH 06/23] iommu/vt-d: Add pasid private data helpers Lu Baolu
2021-06-10 2:00 ` [PATCH 07/23] iommu/vt-d: Use iommu_sva_alloc(free)_pasid() helpers Lu Baolu
2021-06-10 2:01 ` [PATCH 08/23] iommu/vt-d: Use common helper to lookup svm devices Lu Baolu
2021-06-10 2:01 ` [PATCH 09/23] iommu/vt-d: Refactor prq_event_thread() Lu Baolu
2021-06-10 2:01 ` [PATCH 10/23] iommu/vt-d: Allocate/register iopf queue for sva devices Lu Baolu
2021-06-10 2:01 ` [PATCH 11/23] iommu/vt-d: Report prq to io-pgfault framework Lu Baolu
2021-06-10 2:01 ` [PATCH 12/23] iommu/vt-d: Add prq_report trace event Lu Baolu
2021-06-10 2:01 ` [PATCH 13/23] iommu/vt-d: Add common code for dmar latency performance monitors Lu Baolu
2021-06-10 2:01 ` [PATCH 14/23] iommu/vt-d: Expose latency monitor data through debugfs Lu Baolu
2021-06-10 2:01 ` [PATCH 15/23] iommu/vt-d: Add cache invalidation latency sampling Lu Baolu
2021-06-10 2:01 ` [PATCH 16/23] iommu/vt-d: Add PRQ handling " Lu Baolu
2021-06-10 2:01 ` [PATCH 17/23] iommu/vt-d: Fix out-bounds-warning in intel/svm.c Lu Baolu
2021-06-10 2:01 ` [PATCH 18/23] iommu/vt-d: Use DEVICE_ATTR_RO macro Lu Baolu
2021-06-10 2:01 ` [PATCH 19/23] iommu/vt-d: Use bitfields for DMAR capabilities Lu Baolu
2021-06-10 2:01 ` [PATCH 20/23] iommu/vt-d: Removed unused iommu_count in dmar domain Lu Baolu
2021-06-10 2:01 ` [PATCH 21/23] iommu/vt-d: Remove unnecessary braces Lu Baolu
2021-06-10 2:01 ` [PATCH 22/23] iommu/vt-d: Define counter explicitly as unsigned int Lu Baolu
2021-06-10 2:01 ` [PATCH 23/23] iommu/vt-d: No need to typecast Lu Baolu
2021-06-10 7:13 ` [PATCH 00/23] [PULL REQUEST] Intel IOMMU Updates for Linux v5.14 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=20210610020115.1637656-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=colin.king@canonical.com \
--cc=fenghua.yu@intel.com \
--cc=gustavoars@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=rdunlap@infradead.org \
--cc=will@kernel.org \
--cc=yashsri421@gmail.com \
--cc=yuehaibing@huawei.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.