From: Lu Baolu <baolu.lu@linux.intel.com>
To: Jacob jun Pan <jacob.jun.pan@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Ashok Raj <ashok.raj@intel.com>, Liu Yi L <yi.l.liu@intel.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v2 0/4] iommu/vt-d: Some fine tuning of SVA
Date: Thu, 21 Apr 2022 19:35:54 +0800 [thread overview]
Message-ID: <20220421113558.3504874-1-baolu.lu@linux.intel.com> (raw)
Hi folks,
This includes several tunings of Intel SVA implementation. I plan to
target them for v5.19. Please help to review.
Best regards,
baolu
Change log:
v2:
- Move snoop control capability check into a separated patch.
- Return false if the caller opt-in setting PGSNP with a flag.
- Add a Fixes tag for "iommu/vt-d: Drop stop marker messages" as it is
required by the iopf framework.
v1: initial post
- https://lore.kernel.org/linux-iommu/20220416123049.879969-1-baolu.lu@linux.intel.com/
Lu Baolu (4):
iommu/vt-d: Check before setting PGSNP bit in pasid table entry
iommu/vt-d: Set PGSNP bit in pasid table entry for SVA binding
iommu/vt-d: Drop stop marker messages
iommu/vt-d: Size Page Request Queue to avoid overflow condition
include/linux/intel-svm.h | 2 +-
drivers/iommu/intel/pasid.c | 13 ++++++++++---
drivers/iommu/intel/svm.c | 13 ++++++++++---
3 files changed, 21 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-21 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 11:35 Lu Baolu [this message]
2022-04-21 11:35 ` [PATCH v2 1/4] iommu/vt-d: Check before setting PGSNP bit in pasid table entry Lu Baolu
2022-04-22 2:47 ` Tian, Kevin
2022-04-22 13:04 ` Lu Baolu
2022-04-24 3:37 ` Tian, Kevin
2022-04-24 4:37 ` Lu Baolu
2022-04-24 5:55 ` Tian, Kevin
2022-04-24 6:23 ` Lu Baolu
2022-04-21 11:35 ` [PATCH v2 2/4] iommu/vt-d: Set PGSNP bit in pasid table entry for SVA binding Lu Baolu
2022-04-22 3:05 ` Tian, Kevin
2022-04-22 13:13 ` Lu Baolu
2022-04-21 11:35 ` [PATCH v2 3/4] iommu/vt-d: Drop stop marker messages Lu Baolu
2022-04-22 3:05 ` Tian, Kevin
2022-04-23 7:32 ` Lu Baolu
2022-04-21 11:35 ` [PATCH v2 4/4] iommu/vt-d: Size Page Request Queue to avoid overflow condition Lu Baolu
2022-04-22 3:07 ` Tian, Kevin
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=20220421113558.3504874-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@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