From: Bart Van Assche <bvanassche@acm.org>
To: John Garry <john.garry@huawei.com>,
damien.lemoal@opensource.wdc.com, joro@8bytes.org,
will@kernel.org, jejb@linux.ibm.com, martin.petersen@oracle.com,
hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-scsi@vger.kernel.org, liyihang6@hisilicon.com,
chenxiang66@hisilicon.com, thunder.leizhen@huawei.com
Subject: Re: [PATCH v3 3/4] scsi: core: Cap shost max_sectors according to DMA optimum mapping limits
Date: Thu, 9 Jun 2022 13:34:31 -0700 [thread overview]
Message-ID: <23bf4427-41c3-bf1d-903a-75928bb47627@acm.org> (raw)
In-Reply-To: <9b1d155e-28cc-08dc-5a5a-8580132575e7@huawei.com>
On 6/9/22 10:54, John Garry wrote:
> ok, but do you have a system where the UFS host controller is behind an
> IOMMU? I had the impression that UFS controllers would be mostly found
> in embedded systems and IOMMUs are not as common on there.
Modern phones have an IOMMU. Below one can find an example from a Pixel
6 phone. The UFS storage controller is not controller by the IOMMU as
far as I can see but I wouldn't be surprised if the security team would
ask us one day to enable the IOMMU for the UFS controller.
# (cd /sys/class/iommu && ls */devices)
1a090000.sysmmu/devices:
19000000.aoc
1a510000.sysmmu/devices:
1a440000.lwis_csi
1a540000.sysmmu/devices:
1aa40000.lwis_pdp
1a880000.sysmmu/devices:
1a840000.lwis_g3aa
1ad00000.sysmmu/devices:
1ac40000.lwis_ipp 1ac80000.lwis_gtnr_align
1b080000.sysmmu/devices:
1b450000.lwis_itp
1b780000.sysmmu/devices:
1b7b0000.sysmmu/devices:
1b760000.lwis_mcsc
1b7e0000.sysmmu/devices:
1baa0000.sysmmu/devices:
1a4e0000.lwis_votf 1ba40000.lwis_gdc
1bad0000.sysmmu/devices:
1ba60000.lwis_gdc
1bb00000.sysmmu/devices:
1ba80000.lwis_scsc
1bc70000.sysmmu/devices:
1bc40000.lwis_gtnr_merge
1bca0000.sysmmu/devices:
1bcd0000.sysmmu/devices:
1bd00000.sysmmu/devices:
1bd30000.sysmmu/devices:
1c100000.sysmmu/devices:
1c300000.drmdecon 1c302000.drmdecon
1c110000.sysmmu/devices:
1c120000.sysmmu/devices:
1c660000.sysmmu/devices:
1c640000.g2d
1c690000.sysmmu/devices:
1c710000.sysmmu/devices:
1c700000.smfc
1c870000.sysmmu/devices:
1c8d0000.MFC-0 mfc
1c8a0000.sysmmu/devices:
1ca40000.sysmmu/devices:
1cb00000.bigocean
1cc40000.sysmmu/devices:
1ce00000.abrolhos
Bart.
next prev parent reply other threads:[~2022-06-09 20:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 9:30 [PATCH v3 0/4] DMA mapping changes for SCSI core John Garry
2022-06-06 9:30 ` [PATCH v3 1/4] dma-mapping: Add dma_opt_mapping_size() John Garry
2022-06-08 17:27 ` Bart Van Assche
2022-06-06 9:30 ` [PATCH v3 2/4] dma-iommu: Add iommu_dma_opt_mapping_size() John Garry
2022-06-08 17:26 ` Bart Van Assche
2022-06-08 17:39 ` John Garry
2022-06-14 13:12 ` John Garry
2022-06-23 8:38 ` John Garry
2022-06-06 9:30 ` [PATCH v3 3/4] scsi: core: Cap shost max_sectors according to DMA optimum mapping limits John Garry
2022-06-08 17:33 ` Bart Van Assche
2022-06-08 17:50 ` John Garry
2022-06-08 21:07 ` Bart Van Assche
2022-06-09 8:00 ` John Garry
2022-06-09 17:18 ` Bart Van Assche
2022-06-09 17:54 ` John Garry
2022-06-09 20:34 ` Bart Van Assche [this message]
2022-06-10 15:37 ` John Garry
2022-06-23 8:36 ` John Garry
2022-06-06 9:30 ` [PATCH v3 4/4] libata-scsi: Cap ata_device->max_sectors according to shost->max_sectors John Garry
2022-06-07 22:43 ` [PATCH v3 0/4] DMA mapping changes for SCSI core Bart Van Assche
2022-06-08 10:14 ` John Garry
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=23bf4427-41c3-bf1d-903a-75928bb47627@acm.org \
--to=bvanassche@acm.org \
--cc=chenxiang66@hisilicon.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liyihang6@hisilicon.com \
--cc=m.szyprowski@samsung.com \
--cc=martin.petersen@oracle.com \
--cc=robin.murphy@arm.com \
--cc=thunder.leizhen@huawei.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 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).