public inbox for iommu@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
	Kyung Min Park <kyung.min.park@intel.com>,
	iommu@lists.linux-foundation.org, Longpeng <longpeng2@huawei.com>
Subject: Re: [PATCH 0/9] [PULL REQUEST] Intel IOMMU Updates for Linux v5.16
Date: Mon, 18 Oct 2021 20:33:43 +0200	[thread overview]
Message-ID: <YW2+B2+glskmqzgC@8bytes.org> (raw)
In-Reply-To: <20211014053839.727419-1-baolu.lu@linux.intel.com>

On Thu, Oct 14, 2021 at 01:38:30PM +0800, Lu Baolu wrote:
> Fenghua Yu (1):
>   iommu/vt-d: Clean up unused PASID updating functions
> 
> Kyung Min Park (1):
>   iommu/vt-d: Dump DMAR translation structure when DMA fault occurs
> 
> Longpeng(Mike) (2):
>   iommu/vt-d: Convert the return type of first_pte_in_page to bool
>   iommu/vt-d: Avoid duplicate removing in __domain_mapping()
> 
> Lu Baolu (4):
>   iommu/vt-d: Remove duplicate identity domain flag
>   iommu/vt-d: Check FL and SL capability sanity in scalable mode
>   iommu/vt-d: Use second level for GPA->HPA translation
>   iommu/vt-d: Delete dev_has_feat callback
> 
> Tvrtko Ursulin (1):
>   iommu/vt-d: Do not falsely log intel_iommu is unsupported kernel
>     option
> 
>  include/linux/dmar.h            |   8 ++
>  include/linux/intel-iommu.h     |  13 +-
>  arch/x86/include/asm/fpu/api.h  |   2 -
>  drivers/iommu/intel/cap_audit.h |   1 +
>  drivers/iommu/intel/cap_audit.c |  13 ++
>  drivers/iommu/intel/dmar.c      |  10 +-
>  drivers/iommu/intel/iommu.c     | 213 ++++++++++++++++++++++----------
>  drivers/iommu/intel/svm.c       |  24 +---
>  drivers/iommu/intel/Kconfig     |   4 +
>  9 files changed, 188 insertions(+), 100 deletions(-)

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

      parent reply	other threads:[~2021-10-18 18:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  5:38 [PATCH 0/9] [PULL REQUEST] Intel IOMMU Updates for Linux v5.16 Lu Baolu
2021-10-14  5:38 ` [PATCH 1/9] iommu/vt-d: Do not falsely log intel_iommu is unsupported kernel option Lu Baolu
2021-10-14  5:38 ` [PATCH 2/9] iommu/vt-d: Dump DMAR translation structure when DMA fault occurs Lu Baolu
2021-10-14  5:38 ` [PATCH 3/9] iommu/vt-d: Remove duplicate identity domain flag Lu Baolu
2021-10-14  5:38 ` [PATCH 4/9] iommu/vt-d: Check FL and SL capability sanity in scalable mode Lu Baolu
2021-10-14  5:38 ` [PATCH 5/9] iommu/vt-d: Use second level for GPA->HPA translation Lu Baolu
2021-10-14  5:38 ` [PATCH 6/9] iommu/vt-d: Delete dev_has_feat callback Lu Baolu
2021-10-14  5:38 ` [PATCH 7/9] iommu/vt-d: Clean up unused PASID updating functions Lu Baolu
2021-10-14  5:38 ` [PATCH 8/9] iommu/vt-d: Convert the return type of first_pte_in_page to bool Lu Baolu
2021-10-14  5:38 ` [PATCH 9/9] iommu/vt-d: Avoid duplicate removing in __domain_mapping() Lu Baolu
2021-10-18 18:33 ` Joerg Roedel [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=YW2+B2+glskmqzgC@8bytes.org \
    --to=joro@8bytes.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=kevin.tian@intel.com \
    --cc=kyung.min.park@intel.com \
    --cc=longpeng2@huawei.com \
    --cc=tvrtko.ursulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox