From: Robin Murphy <robin.murphy@arm.com>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, kernel-team@android.com,
iommu@lists.linux.dev, Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Petr Tesarik <petr.tesarik1@huawei-partners.com>,
Dexuan Cui <decui@microsoft.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v6 6/6] swiotlb: Reinstate page-alignment for mappings >= PAGE_SIZE
Date: Fri, 8 Mar 2024 17:17:51 +0000 [thread overview]
Message-ID: <9597a3ea-b71f-46bd-bc72-1d19e81dcfb5@arm.com> (raw)
In-Reply-To: <20240308173816.5351ea58@meshulam.tesarici.cz>
On 2024-03-08 4:38 pm, Petr Tesařík wrote:
> On Fri, 8 Mar 2024 16:08:01 +0000
> Robin Murphy <robin.murphy@arm.com> wrote:
>
>> On 2024-03-08 3:28 pm, Will Deacon wrote:
>>> For swiotlb allocations >= PAGE_SIZE, the slab search historically
>>> adjusted the stride to avoid checking unaligned slots. This had the
>>> side-effect of aligning large mapping requests to PAGE_SIZE, but that
>>> was broken by 0eee5ae10256 ("swiotlb: fix slot alignment checks").
>>>
>>> Since this alignment could be relied upon drivers, reinstate PAGE_SIZE
>>> alignment for swiotlb mappings >= PAGE_SIZE.
>>
>> This seems clear enough to keep me happy now, thanks! And apologies that
>> I managed to confuse even myself in the previous thread...
>>
>> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
>
> I thought we agreed that this stricter alignment is unnecessary:
>
> https://lore.kernel.org/linux-iommu/20240305140833.GC3659@lst.de/
No, that was about dma_alloc_coherent() again (and TBH I'm not sure we
should actually relax it anyway, since there definitely are callers who
rely on size-alignment beyond PAGE_SIZE, however they're typically going
to be using the common implementations which end up in alloc_pages() or
CMA and so do offer that, rather than the oddball ones which don't -
e.g. we're never going to be allocating SMMUv3 Stream Tables out of some
restricted pool via the emergency swiotlb_alloc() path). If anywhere,
the place to argue that point would be patch #3 (which as mentioned I'd
managed to forget about before...)
This one's just about preserving a SWIOTLB-specific behaviour which has
the practical effect of making SWIOTLB a bit less visible to dma_map_*()
callers. The impact of keeping this is fairly low, so seems preferable
to the risk of facing issues 2 or 3 years down the line when someone
finally upgrades their distro and their data gets eaten because it turns
out some obscure driver should really have been updated to use
min_align_mask.
Thanks,
Robin.
> But if everybody else wants to have it...
>
> Petr T
>
>>> Reported-by: Michael Kelley <mhklinux@outlook.com>
>>> Signed-off-by: Will Deacon <will@kernel.org>
>>> ---
>>> kernel/dma/swiotlb.c | 18 +++++++++++-------
>>> 1 file changed, 11 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/kernel/dma/swiotlb.c b/kernel/dma/swiotlb.c
>>> index c381a7ed718f..c5851034523f 100644
>>> --- a/kernel/dma/swiotlb.c
>>> +++ b/kernel/dma/swiotlb.c
>>> @@ -992,6 +992,17 @@ static int swiotlb_search_pool_area(struct device *dev, struct io_tlb_pool *pool
>>> BUG_ON(!nslots);
>>> BUG_ON(area_index >= pool->nareas);
>>>
>>> + /*
>>> + * Historically, swiotlb allocations >= PAGE_SIZE were guaranteed to be
>>> + * page-aligned in the absence of any other alignment requirements.
>>> + * 'alloc_align_mask' was later introduced to specify the alignment
>>> + * explicitly, however this is passed as zero for streaming mappings
>>> + * and so we preserve the old behaviour there in case any drivers are
>>> + * relying on it.
>>> + */
>>> + if (!alloc_align_mask && !iotlb_align_mask && alloc_size >= PAGE_SIZE)
>>> + alloc_align_mask = PAGE_SIZE - 1;
>>> +
>>> /*
>>> * Ensure that the allocation is at least slot-aligned and update
>>> * 'iotlb_align_mask' to ignore bits that will be preserved when
>>> @@ -1006,13 +1017,6 @@ static int swiotlb_search_pool_area(struct device *dev, struct io_tlb_pool *pool
>>> */
>>> stride = get_max_slots(max(alloc_align_mask, iotlb_align_mask));
>>>
>>> - /*
>>> - * For allocations of PAGE_SIZE or larger only look for page aligned
>>> - * allocations.
>>> - */
>>> - if (alloc_size >= PAGE_SIZE)
>>> - stride = umax(stride, PAGE_SHIFT - IO_TLB_SHIFT + 1);
>>> -
>>> spin_lock_irqsave(&area->lock, flags);
>>> if (unlikely(nslots > pool->area_nslabs - area->used))
>>> goto not_found;
>>
>
next prev parent reply other threads:[~2024-03-08 17:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 15:28 [PATCH v6 0/6] Fix double allocation in swiotlb_alloc() Will Deacon
2024-03-08 15:28 ` [PATCH v6 1/6] swiotlb: Fix double-allocation of slots due to broken alignment handling Will Deacon
2024-03-18 3:39 ` Michael Kelley
2024-03-18 12:36 ` Petr Tesařík
2024-03-08 15:28 ` [PATCH v6 2/6] swiotlb: Enforce page alignment in swiotlb_alloc() Will Deacon
2024-03-08 15:28 ` [PATCH v6 3/6] swiotlb: Honour dma_alloc_coherent() " Will Deacon
2024-03-08 15:28 ` [PATCH v6 4/6] swiotlb: Fix alignment checks when both allocation and DMA masks are present Will Deacon
2024-03-11 20:05 ` Petr Tesařík
2024-03-11 21:36 ` Michael Kelley
2024-03-11 22:49 ` Will Deacon
2024-03-12 8:52 ` Petr Tesařík
2024-03-12 9:38 ` Robin Murphy
2024-03-12 9:51 ` Petr Tesařík
2024-03-12 12:57 ` Robin Murphy
2024-03-12 0:52 ` Nicolin Chen
2024-03-12 10:44 ` Petr Tesařík
2024-03-08 15:28 ` [PATCH v6 5/6] iommu/dma: Force swiotlb_max_mapping_size on an untrusted device Will Deacon
2024-03-08 15:28 ` [PATCH v6 6/6] swiotlb: Reinstate page-alignment for mappings >= PAGE_SIZE Will Deacon
2024-03-08 16:08 ` Robin Murphy
2024-03-08 16:38 ` Petr Tesařík
2024-03-08 16:50 ` Christoph Hellwig
2024-03-08 17:22 ` Petr Tesařík
2024-03-08 17:17 ` Robin Murphy [this message]
2024-03-08 18:08 ` Petr Tesařík
2024-03-08 17:28 ` Petr Tesařík
2024-03-08 19:02 ` Michael Kelley
2024-03-08 19:21 ` [PATCH v6 0/6] Fix double allocation in swiotlb_alloc() Michael Kelley
2024-03-11 13:36 ` Christoph Hellwig
2024-03-11 23:19 ` Will Deacon
2024-03-11 22:55 ` Nicolin Chen
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=9597a3ea-b71f-46bd-bc72-1d19e81dcfb5@arm.com \
--to=robin.murphy@arm.com \
--cc=decui@microsoft.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mhklinux@outlook.com \
--cc=nicolinc@nvidia.com \
--cc=petr.tesarik1@huawei-partners.com \
--cc=petr@tesarici.cz \
--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
Powered by JetHome