From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Kyung Min Park <kyung.min.park@intel.com>,
iommu@lists.linux-foundation.org,
Chuck Lever <chuck.lever@oracle.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 0/7] [PULL REQUEST] iommu/vt-d: Update for v5.12
Date: Thu, 4 Feb 2021 13:32:34 +0800 [thread overview]
Message-ID: <b3ccac0c-55e4-fced-f0e5-2ac11be0b58c@linux.intel.com> (raw)
In-Reply-To: <20210204014401.2846425-1-baolu.lu@linux.intel.com>
Hi Joerg,
I just received some internal comments on the last patch
[PATCH 7/7] iommu/vt-d: Apply SATC policy
We need some extra work on it and probably re-target it to v5.13.
Can you please only consider patch 1 ~ 6 for v5.12?
Sorry for the inconvenience.
Best regards,
baolu
On 2/4/21 9:43 AM, Lu Baolu wrote:
> Hi Joerg,
>
> The patches queued in this series is for v5.12. It includes:
>
> - Audit capability consistency among different IOMMUs
> - Add SATC reporting structure support
> - Add iotlb_sync_map callback support
> - Misc cleanup
>
> Please consider them for v5.12.
>
> Best regards,
> Lu Baolu
>
> Bjorn Helgaas (1):
> iommu/vt-d: Fix 'physical' typos
>
> Kyung Min Park (2):
> iommu/vt-d: Audit IOMMU Capabilities and add helper functions
> iommu/vt-d: Move capability check code to cap_audit files
>
> Lu Baolu (1):
> iommu/vt-d: Add iotlb_sync_map callback
>
> Yian Chen (3):
> iommu/vt-d: Add new enum value and structure for SATC
> iommu/vt-d: Parse SATC reporting structure
> iommu/vt-d: Apply SATC policy
>
> drivers/iommu/intel/Makefile | 2 +-
> drivers/iommu/intel/cap_audit.c | 205 +++++++++++++++++
> drivers/iommu/intel/cap_audit.h | 130 +++++++++++
> drivers/iommu/intel/dmar.c | 8 +
> drivers/iommu/intel/iommu.c | 337 +++++++++++++++++++---------
> drivers/iommu/intel/irq_remapping.c | 8 +
> include/acpi/actbl1.h | 11 +-
> include/linux/dmar.h | 2 +
> include/linux/intel-iommu.h | 41 ++--
> 9 files changed, 615 insertions(+), 129 deletions(-)
> create mode 100644 drivers/iommu/intel/cap_audit.c
> create mode 100644 drivers/iommu/intel/cap_audit.h
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-02-04 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 1:43 [PATCH 0/7] [PULL REQUEST] iommu/vt-d: Update for v5.12 Lu Baolu
2021-02-04 1:43 ` [PATCH 1/7] iommu/vt-d: Fix 'physical' typos Lu Baolu
2021-02-04 1:43 ` [PATCH 2/7] iommu/vt-d: Audit IOMMU Capabilities and add helper functions Lu Baolu
2021-02-04 1:43 ` [PATCH 3/7] iommu/vt-d: Move capability check code to cap_audit files Lu Baolu
2021-02-04 1:43 ` [PATCH 4/7] iommu/vt-d: Add iotlb_sync_map callback Lu Baolu
2021-02-04 1:43 ` [PATCH 5/7] iommu/vt-d: Add new enum value and structure for SATC Lu Baolu
2021-02-04 1:44 ` [PATCH 6/7] iommu/vt-d: Parse SATC reporting structure Lu Baolu
2021-02-04 1:44 ` [PATCH 7/7] iommu/vt-d: Apply SATC policy Lu Baolu
2021-02-04 5:32 ` Lu Baolu [this message]
2021-02-04 11:52 ` [PATCH 0/7] [PULL REQUEST] iommu/vt-d: Update for v5.12 Lu Baolu
2021-02-04 13:42 ` 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=b3ccac0c-55e4-fced-f0e5-2ac11be0b58c@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=chuck.lever@oracle.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kyung.min.park@intel.com \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).