From: Lu Baolu <baolu.lu@linux.intel.com>
To: "Liu, Yi L" <yi.l.liu@intel.com>, Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>
Cc: "Raj, Ashok" <ashok.raj@intel.com>,
"Kumar, Sanjay K" <sanjay.k.kumar@intel.com>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Sun, Yi Y" <yi.y.sun@intel.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [RFC PATCH 05/10] iommu/vt-d: Setup DMA remapping for mediated devices
Date: Tue, 24 Jul 2018 10:29:15 +0800 [thread overview]
Message-ID: <5B568EFB.2040908@linux.intel.com> (raw)
In-Reply-To: <A2975661238FB949B60364EF0F2C257439CA1449@SHSMSX104.ccr.corp.intel.com>
Hi,
On 07/23/2018 12:44 PM, Liu, Yi L wrote:
>> From: Lu Baolu [mailto:baolu.lu@linux.intel.com]
>> Sent: Sunday, July 22, 2018 2:09 PM
>>
>> This configures the second level page table when external components request to
>> allocate a domain for a mediated device.
> I think it should be the time when adding a mediate device to the domain.
You are right. Will correct it.
>
>> Cc: Ashok Raj <ashok.raj@intel.com>
>> Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
>> Cc: Kevin Tian <kevin.tian@intel.com>
>> Cc: Liu Yi L <yi.l.liu@intel.com>
>> Signed-off-by: Sanjay Kumar <sanjay.k.kumar@intel.com>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> ---
>> drivers/iommu/intel-iommu.c | 73
>> ++++++++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 66 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c index
>> 57ccfc4..b6e9ea8 100644
>> --- a/drivers/iommu/intel-iommu.c
>> +++ b/drivers/iommu/intel-iommu.c
>> @@ -2569,8 +2569,9 @@ static struct dmar_domain
>> *dmar_insert_one_dev_info(struct intel_iommu *iommu,
>> if (dev)
>> dev->archdata.iommu = info;
>>
>> - if (dev && dev_is_pci(dev) && sm_supported(iommu)) {
>> - bool pass_through;
>> + if (dev && sm_supported(iommu)) {
>> + bool pass_through = hw_pass_through &&
>> + domain_type_is_si(domain);
>>
>> ret = intel_pasid_alloc_table(dev);
>> if (ret) {
>> @@ -2579,12 +2580,21 @@ static struct dmar_domain
>> *dmar_insert_one_dev_info(struct intel_iommu *iommu,
>> return NULL;
>> }
>>
>> - /* Setup the PASID entry for requests without PASID: */
>> - pass_through = hw_pass_through && domain_type_is_si(domain);
>> spin_lock(&iommu->lock);
>> - intel_pasid_setup_second_level(iommu, domain, dev,
>> - PASID_RID2PASID,
>> - pass_through);
>> +
>> + /* Setup the PASID entry for requests without PASID: */
>> + if (dev_is_pci(dev))
>> + intel_pasid_setup_second_level(iommu, domain, dev,
>> + PASID_RID2PASID,
> can domain->default_pasid be initialized to be PASID_RID2PASID if the domain
> is not a domain used by mediated device?
PASID_RID2PASID is 0 as well.
>
>> + pass_through);
>> + /* Setup the PASID entry for mediated devices: */
>> + else if (dev_is_mdev(dev))
>> + intel_pasid_setup_second_level(iommu, domain, dev,
>> + domain->default_pasid,
>> + false);
>> + else
>> + pr_err("Unsupported device %s\n", dev_name(dev));
>> +
>> spin_unlock(&iommu->lock);
>> }
>> spin_unlock_irqrestore(&device_domain_lock, flags); @@ -4937,6 +4947,32
>> @@ static void domain_context_clear(struct intel_iommu *iommu, struct device
>> *dev)
>> pci_for_each_dma_alias(to_pci_dev(dev), &domain_context_clear_one_cb,
>> iommu); }
>>
>> +static void
>> +iommu_flush_ext_iotlb(struct intel_iommu *iommu, u16 did, u32 pasid,
> Per latest VT-d spec, its new name is pasid-based-iotlb. Pls update the naming
> accordingly. :)
Okay.
Best regards,
Lu Baolu
>
> Regards,
> Yi Liu
>
>> +u64 gran) {
>> + struct qi_desc desc;
>> +
>> + desc.high = 0;
>> + desc.low = QI_EIOTLB_PASID(pasid) | QI_EIOTLB_DID(did) |
>> + QI_EIOTLB_GRAN(gran) | QI_EIOTLB_TYPE;
>> +
>> + qi_submit_sync(&desc, iommu);
>> +}
>> +
>> +static void iommu_flush_pasid_dev_iotlb(struct intel_iommu *iommu,
>> + struct device *dev, int sid, int pasid) {
>> + struct qi_desc desc;
>> + struct pci_dev *pdev = to_pci_dev(dev);
>> + int qdep = pci_ats_queue_depth(pdev);
>> +
>> + desc.low = QI_DEV_EIOTLB_PASID(pasid) | QI_DEV_EIOTLB_SID(sid) |
>> + QI_DEV_EIOTLB_QDEP(qdep) | QI_DEIOTLB_TYPE;
>> + desc.high = QI_DEV_EIOTLB_ADDR(-1ULL >> 1) | QI_DEV_EIOTLB_SIZE;
>> +
>> + qi_submit_sync(&desc, iommu);
>> +}
>> +
>> static void __dmar_remove_one_dev_info(struct device_domain_info *info) {
>> struct intel_iommu *iommu;
>> @@ -4949,6 +4985,29 @@ static void __dmar_remove_one_dev_info(struct
>> device_domain_info *info)
>>
>> iommu = info->iommu;
>>
>> + if (dev_is_mdev(info->dev)) {
>> + struct dmar_domain *domain = info->domain;
>> + int did = domain->iommu_did[iommu->seq_id];
>> + int sid = info->bus << 8 | info->devfn;
>> + struct device *dev = info->dev;
>> +
>> + intel_pasid_clear_entry(dev, domain->default_pasid);
>> +
>> + /* Flush IOTLB including PASID Cache: */
>> + iommu->flush.flush_iotlb(iommu, did, 0, 0, DMA_TLB_DSI_FLUSH);
>> +
>> + /*
>> + * Flush EIOTLB. The only way to flush global mappings within
>> + * a PASID is to use QI_GRAN_ALL_ALL.
>> + */
>> + iommu_flush_ext_iotlb(iommu, did, domain->default_pasid,
>> + QI_GRAN_ALL_ALL);
>> +
>> + /* Flush Dev TLB: */
>> + iommu_flush_pasid_dev_iotlb(iommu, dev_mdev_parent(dev), sid,
>> + domain->default_pasid);
>> + }
>> +
>> if (info->dev) {
>> iommu_disable_dev_iotlb(info);
>> domain_context_clear(iommu, info->dev);
>> --
>> 2.7.4
>
next prev parent reply other threads:[~2018-07-24 2:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 6:09 [RFC PATCH 00/10] vfio/mdev: IOMMU aware mediated device Lu Baolu
2018-07-22 6:09 ` Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 01/10] iommu/vt-d: Get iommu device for a " Lu Baolu
2018-07-23 4:44 ` Liu, Yi L
[not found] ` <A2975661238FB949B60364EF0F2C257439CA141D-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-07-24 2:06 ` Lu Baolu
2018-07-24 2:06 ` Lu Baolu
[not found] ` <1532239773-15325-2-git-send-email-baolu.lu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-07-24 18:50 ` Alex Williamson
2018-07-24 18:50 ` Alex Williamson
[not found] ` <20180724125056.4ae477c9-1yVPhWWZRC1BDLzU/O5InQ@public.gmane.org>
2018-07-25 1:18 ` Lu Baolu
2018-07-25 1:18 ` Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 02/10] iommu/vt-d: Alloc domain " Lu Baolu
2018-07-23 4:44 ` Liu, Yi L
[not found] ` <A2975661238FB949B60364EF0F2C257439CA1432-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-07-24 2:09 ` Lu Baolu
2018-07-24 2:09 ` Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 03/10] iommu/vt-d: Allocate groups for mediated devices Lu Baolu
[not found] ` <1532239773-15325-4-git-send-email-baolu.lu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-07-23 4:44 ` Liu, Yi L
2018-07-23 4:44 ` Liu, Yi L
[not found] ` <A2975661238FB949B60364EF0F2C257439CA143E-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-07-24 2:22 ` Lu Baolu
2018-07-24 2:22 ` Lu Baolu
2018-07-24 11:30 ` Jean-Philippe Brucker
2018-07-24 19:51 ` Alex Williamson
2018-07-25 2:06 ` Lu Baolu
[not found] ` <ccf6890a-30c6-770b-4299-8cabfdc32f2b-5wv7dgnIgG8@public.gmane.org>
2018-07-25 2:16 ` Tian, Kevin
2018-07-25 2:16 ` Tian, Kevin
2018-07-25 2:35 ` Liu, Yi L
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D19127FB9E@SHSMSX101.ccr.corp.intel.com>
2018-07-25 6:19 ` Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D19127FF05-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-07-25 19:19 ` Jean-Philippe Brucker
2018-07-25 19:19 ` Jean-Philippe Brucker
[not found] ` <a530c220-9bf1-05ec-5698-526ccbea127f-5wv7dgnIgG8@public.gmane.org>
2018-07-26 3:03 ` Tian, Kevin
2018-07-26 3:03 ` Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D1912826A4-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-07-26 15:09 ` Jean-Philippe Brucker
2018-07-26 15:09 ` Jean-Philippe Brucker
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D1912826AE@SHSMSX101.ccr.corp.intel.com>
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D1912826AE-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-07-26 3:28 ` Tian, Kevin
2018-07-26 3:28 ` Tian, Kevin
2018-07-26 15:09 ` Jean-Philippe Brucker
2018-07-22 6:09 ` [RFC PATCH 04/10] iommu/vt-d: Get pasid table for a mediated device Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 05/10] iommu/vt-d: Setup DMA remapping for mediated devices Lu Baolu
2018-07-23 4:44 ` Liu, Yi L
2018-07-24 2:29 ` Lu Baolu [this message]
2018-07-22 6:09 ` [RFC PATCH 06/10] iommu: Add iommu_set_bus API interface Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 07/10] iommu/vt-d: Add set_bus iommu ops Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 08/10] vfio/mdev: Set iommu ops for mdev bus Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 09/10] vfio/mdev: Add mediated device domain type Lu Baolu
2018-07-22 6:09 ` [RFC PATCH 10/10] vfio/type1: Allocate domain for mediated device Lu Baolu
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=5B568EFB.2040908@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=sanjay.k.kumar@intel.com \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.