From: Leon Romanovsky <leon@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Subject: Re: [PATCH] dma-mapping: reliably inform about DMA support for IOMMU
Date: Thu, 12 Sep 2024 13:50:09 +0300 [thread overview]
Message-ID: <20240912105009.GI4026@unreal> (raw)
In-Reply-To: <20240912072954.GC7614@lst.de>
On Thu, Sep 12, 2024 at 09:29:54AM +0200, Christoph Hellwig wrote:
> Thanks, I've applied this. I do like the flow of dma_supported even
> less with the duplicate condition now. Can I get a quick review for
> this incremental cleanup, please?
>
> ---
> From d311bfe189d12a836b4add55fdb946f37f8697fa Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig <hch@lst.de>
> Date: Thu, 12 Sep 2024 09:21:18 +0200
> Subject: dma-mapping: reflow dma_supported
>
> dma_supported has become too much spaghetti for my taste. Reflow it to
> remove the duplicate use_dma_iommu condition and make the main path more
> obvious.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> kernel/dma/mapping.c | 25 ++++++++++++++-----------
> 1 file changed, 14 insertions(+), 11 deletions(-)
Reviewed-by: Leon Romanovsky <leon@kernel.org>
>
> diff --git a/kernel/dma/mapping.c b/kernel/dma/mapping.c
> index 022d670f8cad29..cd2a97d362cd24 100644
> --- a/kernel/dma/mapping.c
> +++ b/kernel/dma/mapping.c
> @@ -841,20 +841,23 @@ static int dma_supported(struct device *dev, u64 mask)
> {
> const struct dma_map_ops *ops = get_dma_ops(dev);
>
> - if (WARN_ON(ops && use_dma_iommu(dev)))
> - return false;
> -
> - if (use_dma_iommu(dev))
> + if (use_dma_iommu(dev)) {
> + if (WARN_ON(ops))
> + return false;
> return true;
You can write it as "return !WARN_ON(ops);" if you want to be fancy, but
your version is perfectly fine too, so ignore this comment :).
> + }
> +
> /*
> - * ->dma_supported sets the bypass flag, so we must always call
> - * into the method here unless the device is truly direct mapped.
> + * ->dma_supported sets and clears the bypass flag, so ignore it here
> + * and always call into the method if there is one.
> */
> - if (!ops)
> - return dma_direct_supported(dev, mask);
> - if (!ops->dma_supported)
> - return 1;
> - return ops->dma_supported(dev, mask);
> + if (ops) {
> + if (!ops->dma_supported)
> + return 1;
Worth to change it to be "return true;"
> + return ops->dma_supported(dev, mask);
> + }
> +
> + return dma_direct_supported(dev, mask);
> }
>
> bool dma_pci_p2pdma_supported(struct device *dev)
> --
> 2.45.2
>
prev parent reply other threads:[~2024-09-12 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 10:15 [PATCH] dma-mapping: reliably inform about DMA support for IOMMU Leon Romanovsky
2024-09-11 12:54 ` Robin Murphy
2024-09-11 12:54 ` Nícolas F. R. A. Prado
2024-09-12 7:29 ` Christoph Hellwig
2024-09-12 10:50 ` Leon Romanovsky [this message]
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=20240912105009.GI4026@unreal \
--to=leon@kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nfraprado@collabora.com \
--cc=robin.murphy@arm.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