All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Robin Murphy <robin.murphy@arm.com>, joro@8bytes.org, will@kernel.org
Cc: baolu.lu@linux.intel.com, iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, suravee.suthikulpanit@amd.com,
	john.garry@huawei.com, dianders@chromium.org
Subject: Re: [PATCH 18/23] iommu: Express DMA strictness via the domain type
Date: Mon, 26 Jul 2021 19:31:30 +0800	[thread overview]
Message-ID: <832b7db0-4eb2-9151-c2b3-db709aee3230@linux.intel.com> (raw)
In-Reply-To: <77057c4b-479b-c5b8-4666-f16e294552d1@arm.com>

On 2021/7/26 16:27, Robin Murphy wrote:
> On 2021-07-24 06:29, Lu Baolu wrote:
>> Hi Robin,
>>
>> On 2021/7/22 2:20, Robin Murphy wrote:
>>> Eliminate the iommu_get_dma_strict() indirection and pipe the
>>> information through the domain type from the beginning. Besides
>>> the flow simplification this also has several nice side-effects:
>>>
>>>   - Automatically implies strict mode for untrusted devices by
>>>     virtue of their IOMMU_DOMAIN_DMA override.
>>>   - Ensures that we only ends up using flush queues for drivers
>>>     which are aware of them and can actually benefit.
>>
>> Is this expressed by vendor iommu driver has ops->flush_iotlb_all?
> 
> No, it's literally whether ->domain_alloc accepts the DMA_DOMAIN_FQ type 
> or not.

Get it. Thank you!

Best regards,
baolu

WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Robin Murphy <robin.murphy@arm.com>, joro@8bytes.org, will@kernel.org
Cc: linux-kernel@vger.kernel.org, dianders@chromium.org,
	iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 18/23] iommu: Express DMA strictness via the domain type
Date: Mon, 26 Jul 2021 19:31:30 +0800	[thread overview]
Message-ID: <832b7db0-4eb2-9151-c2b3-db709aee3230@linux.intel.com> (raw)
In-Reply-To: <77057c4b-479b-c5b8-4666-f16e294552d1@arm.com>

On 2021/7/26 16:27, Robin Murphy wrote:
> On 2021-07-24 06:29, Lu Baolu wrote:
>> Hi Robin,
>>
>> On 2021/7/22 2:20, Robin Murphy wrote:
>>> Eliminate the iommu_get_dma_strict() indirection and pipe the
>>> information through the domain type from the beginning. Besides
>>> the flow simplification this also has several nice side-effects:
>>>
>>>   - Automatically implies strict mode for untrusted devices by
>>>     virtue of their IOMMU_DOMAIN_DMA override.
>>>   - Ensures that we only ends up using flush queues for drivers
>>>     which are aware of them and can actually benefit.
>>
>> Is this expressed by vendor iommu driver has ops->flush_iotlb_all?
> 
> No, it's literally whether ->domain_alloc accepts the DMA_DOMAIN_FQ type 
> or not.

Get it. Thank you!

Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Robin Murphy <robin.murphy@arm.com>, joro@8bytes.org, will@kernel.org
Cc: baolu.lu@linux.intel.com, iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, suravee.suthikulpanit@amd.com,
	john.garry@huawei.com, dianders@chromium.org
Subject: Re: [PATCH 18/23] iommu: Express DMA strictness via the domain type
Date: Mon, 26 Jul 2021 19:31:30 +0800	[thread overview]
Message-ID: <832b7db0-4eb2-9151-c2b3-db709aee3230@linux.intel.com> (raw)
In-Reply-To: <77057c4b-479b-c5b8-4666-f16e294552d1@arm.com>

On 2021/7/26 16:27, Robin Murphy wrote:
> On 2021-07-24 06:29, Lu Baolu wrote:
>> Hi Robin,
>>
>> On 2021/7/22 2:20, Robin Murphy wrote:
>>> Eliminate the iommu_get_dma_strict() indirection and pipe the
>>> information through the domain type from the beginning. Besides
>>> the flow simplification this also has several nice side-effects:
>>>
>>>   - Automatically implies strict mode for untrusted devices by
>>>     virtue of their IOMMU_DOMAIN_DMA override.
>>>   - Ensures that we only ends up using flush queues for drivers
>>>     which are aware of them and can actually benefit.
>>
>> Is this expressed by vendor iommu driver has ops->flush_iotlb_all?
> 
> No, it's literally whether ->domain_alloc accepts the DMA_DOMAIN_FQ type 
> or not.

Get it. Thank you!

Best regards,
baolu

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-07-26 11:31 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 18:20 [PATCH 00/23] iommu: Refactor DMA domain strictness Robin Murphy
2021-07-21 18:20 ` Robin Murphy
2021-07-21 18:20 ` Robin Murphy
2021-07-21 18:20 ` [PATCH 01/23] iommu: Pull IOVA cookie management into the core Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 02/23] iommu/amd: Drop IOVA cookie management Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 03/23] iommu/arm-smmu: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 04/23] iommu/vt-d: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 05/23] iommu/exynos: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 06/23] iommu/ipmmu-vmsa: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 07/23] iommu/mtk: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 08/23] iommu/rockchip: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 09/23] iommu/sprd: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 10/23] iommu/sun50i: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 11/23] iommu/virtio: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 12/23] iommu/dma: Unexport " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 13/23] iommu/dma: Remove redundant "!dev" checks Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-26  8:28   ` John Garry
2021-07-26  8:28     ` John Garry
2021-07-26  8:28     ` John Garry
2021-07-21 18:20 ` [PATCH 14/23] iommu: Introduce explicit type for non-strict DMA domains Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 15/23] iommu/amd: Prepare for multiple DMA domain types Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 16/23] iommu/arm-smmu: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-26 12:46   ` Joerg Roedel
2021-07-26 12:46     ` Joerg Roedel
2021-07-26 12:46     ` Joerg Roedel
2021-07-26 13:09     ` Robin Murphy
2021-07-26 13:09       ` Robin Murphy
2021-07-26 13:09       ` Robin Murphy
2021-07-26 18:43       ` Joerg Roedel
2021-07-26 18:43         ` Joerg Roedel
2021-07-26 18:43         ` Joerg Roedel
2021-07-21 18:20 ` [PATCH 17/23] iommu/vt-d: " Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-22 16:44   ` kernel test robot
2021-07-22 16:44     ` kernel test robot
2021-07-22 16:44     ` kernel test robot
2021-07-22 16:44     ` kernel test robot
2021-07-22 17:30     ` Robin Murphy
2021-07-22 17:30       ` Robin Murphy
2021-07-22 17:30       ` Robin Murphy
2021-07-22 17:30       ` Robin Murphy
2021-07-22 18:44   ` kernel test robot
2021-07-22 18:44     ` kernel test robot
2021-07-22 18:44     ` kernel test robot
2021-07-22 18:44     ` kernel test robot
2021-07-24  5:23   ` Lu Baolu
2021-07-24  5:23     ` Lu Baolu
2021-07-24  5:23     ` Lu Baolu
2021-07-26  8:30     ` Robin Murphy
2021-07-26  8:30       ` Robin Murphy
2021-07-26  8:30       ` Robin Murphy
2021-07-21 18:20 ` [PATCH 18/23] iommu: Express DMA strictness via the domain type Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-24  5:29   ` Lu Baolu
2021-07-24  5:29     ` Lu Baolu
2021-07-24  5:29     ` Lu Baolu
2021-07-26  8:27     ` Robin Murphy
2021-07-26  8:27       ` Robin Murphy
2021-07-26  8:27       ` Robin Murphy
2021-07-26 11:31       ` Lu Baolu [this message]
2021-07-26 11:31         ` Lu Baolu
2021-07-26 11:31         ` Lu Baolu
2021-07-26 12:29       ` Lu Baolu
2021-07-26 12:29         ` Lu Baolu
2021-07-26 12:29         ` Lu Baolu
2021-07-26 12:43         ` Robin Murphy
2021-07-26 12:43           ` Robin Murphy
2021-07-26 12:43           ` Robin Murphy
2021-07-21 18:20 ` [PATCH 19/23] iommu: Expose DMA domain strictness via sysfs Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 20/23] iommu: Allow choosing DMA strictness at build time Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 21/23] iommu/dma: Factor out flush queue init Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 22/23] iommu: Allow enabling non-strict mode dynamically Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20 ` [PATCH 23/23] iommu/arm-smmu: Allow non-strict in pgtable_quirks interface Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-21 18:20   ` Robin Murphy
2021-07-26  8:13 ` [PATCH 00/23] iommu: Refactor DMA domain strictness John Garry
2021-07-26  8:13   ` John Garry
2021-07-26  8:13   ` John Garry
2021-07-26 12:06   ` Robin Murphy
2021-07-26 12:06     ` Robin Murphy
2021-07-26 12:06     ` Robin Murphy
2021-07-26 13:02 ` Joerg Roedel
2021-07-26 13:02   ` Joerg Roedel
2021-07-26 13:02   ` Joerg Roedel

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=832b7db0-4eb2-9151-c2b3-db709aee3230@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=dianders@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=john.garry@huawei.com \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=will@kernel.org \
    /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.