public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Tina Zhang <tina.zhang@intel.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] [PULL REQUEST] iommu/vt-d: Fixes for v6.2-rc8
Date: Thu, 16 Feb 2023 21:08:12 +0800	[thread overview]
Message-ID: <20230216130816.151824-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

Below iommu/vt-d fixes are queued for your fixes branch.

- Two performance optimizations
- Fix PASID directory pointer coherency
- Fix missed rollbacks in error path

Please consider it for the iommu/fixes branch.

Best regards,
Lu Baolu

Jacob Pan (2):
  iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode
  iommu/vt-d: Fix PASID directory pointer coherency

Lu Baolu (1):
  iommu/vt-d: Fix error handling in sva enable/disable paths

Tina Zhang (1):
  iommu/vt-d: Allow to use flush-queue when first level is default

 drivers/iommu/intel/iommu.c | 26 ++++++++++++++++++++------
 drivers/iommu/intel/pasid.c |  7 +++++++
 2 files changed, 27 insertions(+), 6 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-02-16 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 13:08 Lu Baolu [this message]
2023-02-16 13:08 ` [PATCH 1/4] iommu/vt-d: Fix error handling in sva enable/disable paths Lu Baolu
2023-02-16 13:08 ` [PATCH 2/4] iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode Lu Baolu
2023-02-16 13:08 ` [PATCH 3/4] iommu/vt-d: Fix PASID directory pointer coherency Lu Baolu
2023-02-16 13:08 ` [PATCH 4/4] iommu/vt-d: Allow to use flush-queue when first level is default Lu Baolu
2023-02-16 13:42 ` [PATCH 0/4] [PULL REQUEST] iommu/vt-d: Fixes for v6.2-rc8 Joerg Roedel
2023-02-16 13:45   ` Baolu Lu

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=20230216130816.151824-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tina.zhang@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