From: Liu Yi L <yi.l.liu@intel.com>
To: baolu.lu@linux.intel.com, jacob.jun.pan@intel.com,
xin.zeng@intel.com, Kaijie.Guo@intel.com, will@kernel.org,
joro@8bytes.org
Cc: kevin.tian@intel.com, jun.j.tian@intel.com,
iommu@lists.linux-foundation.org, ashok.raj@intel.com
Subject: [PATCH 0/4] iommu/vtd-: Misc fixes on scalable mode
Date: Sun, 20 Dec 2020 08:03:49 +0800 [thread overview]
Message-ID: <20201220000352.183523-1-yi.l.liu@intel.com> (raw)
Hi,
This patchset aims to fix a bug regards to SVM usage on native, and
also several bugs around subdevice (attached to device via auxiliary
manner) tracking and ineffective device_tlb flush.
Regards,
Yi Liu
Liu Yi L (3):
iommu/vt-d: Move intel_iommu info from struct intel_svm to struct
intel_svm_dev
iommu/vt-d: Track device aux-attach with subdevice_domain_info.
iommu/vt-d: A fix to iommu_flush_dev_iotlb() for aux-domain
drivers/iommu/intel/iommu.c | 182 ++++++++++++++++++++++++++++++------
drivers/iommu/intel/svm.c | 9 +-
include/linux/intel-iommu.h | 13 ++-
3 files changed, 168 insertions(+), 36 deletions(-)
--
2.25.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-12-19 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 0:03 Liu Yi L [this message]
2020-12-20 0:03 ` [PATCH 1/3] iommu/vt-d: Move intel_iommu info from struct intel_svm to struct intel_svm_dev Liu Yi L
2020-12-19 6:50 ` Lu Baolu
2020-12-21 1:43 ` Guo, Kaijie
2020-12-20 0:03 ` [PATCH 2/3] iommu/vt-d: Track device aux-attach with subdevice_domain_info Liu Yi L
2020-12-19 6:52 ` Lu Baolu
2020-12-22 20:21 ` Jacob Pan
2020-12-23 3:59 ` Liu, Yi L
2020-12-20 0:03 ` [PATCH 3/3] iommu/vt-d: A fix to iommu_flush_dev_iotlb() for aux-domain Liu Yi L
2020-12-19 6:52 ` Lu Baolu
2020-12-22 18:17 ` [PATCH 0/4] iommu/vtd-: Misc fixes on scalable mode Jacob Pan
2020-12-23 3:57 ` Liu, Yi L
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=20201220000352.183523-1-yi.l.liu@intel.com \
--to=yi.l.liu@intel.com \
--cc=Kaijie.Guo@intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=joro@8bytes.org \
--cc=jun.j.tian@intel.com \
--cc=kevin.tian@intel.com \
--cc=will@kernel.org \
--cc=xin.zeng@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;
as well as URLs for NNTP newsgroup(s).