From: Leon Romanovsky <leon@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
Jason Gunthorpe <jgg@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 2/2] dma: add IOMMU static calls with clear default ops
Date: Mon, 22 Jul 2024 19:05:55 +0300 [thread overview]
Message-ID: <20240722160555.GB7022@unreal> (raw)
In-Reply-To: <20240722154929.GA26317@lst.de>
On Mon, Jul 22, 2024 at 05:49:29PM +0200, Christoph Hellwig wrote:
> On Mon, Jul 22, 2024 at 06:44:58PM +0300, Leon Romanovsky wrote:
> > On Mon, Jul 22, 2024 at 05:10:37PM +0200, Christoph Hellwig wrote:
> > > On Sun, Jul 21, 2024 at 10:49:11AM +0300, Leon Romanovsky wrote:
> > > > -static void iommu_dma_free_noncontiguous(struct device *dev, size_t size,
> > > > - struct sg_table *sgt, enum dma_data_direction dir)
> > > > +void iommu_dma_free_noncontiguous(struct device *dev, size_t size,
> > > > + struct sg_table *sgt,
> > > > + enum dma_data_direction dir)
> > >
> > > Why are you reformatting these to a much less readable coding style?
> >
> > I'm relying on clang-formatter to format the code, see .clang-format
> > file in the kernel root directory.
>
> Well, that uses a really horrible default then. Aligning to the opening
> brace not only is hard to read, but requireѕ reformatting with every
> addition and removal of a static like here, or when trivially changing
> the function name.
Should I need to reformat the code to your preferred style?
I can do it, but it will be manual work :(.
>
> > > > +static inline void dma_common_free_pages(struct device *dev, size_t size,
> > > > + struct page *vaddr,
> > > > + dma_addr_t dma_handle,
> > > > + enum dma_data_direction dir)
> > > > +{
> > > > +}
> > >
> > > dma-iommu very much depends on these. So we'll need to also
> > > build ops_helpers.o if dma-iommu is enabled. So we'll probably need
> > > a separate Kconfig option for it that the various users select.
> > >
> >
> > I removed them from dma-iommu.c and there are no calls to them in that file.
> > ➜ kernel git:(m/dma-v2) git grep dma_common_alloc_pages drivers/iommu/ | wc -l
>
> Well, you replaced them with direct calls from mapping.c, which now
> needs them if dma-iommu is supported. So while strictly speaking
> dma-iommu doesn't need them, proper operation with dma-iommu still
> needs them.
No problem, I can add.
Thanks
>
next prev parent reply other threads:[~2024-07-22 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 7:49 [PATCH v3 0/2] DMA IOMMU static calls Leon Romanovsky
2024-07-21 7:49 ` [PATCH v3 1/2] dma: call unconditionally to unmap_page and unmap_sg callbacks Leon Romanovsky
2024-07-21 7:49 ` [PATCH v3 2/2] dma: add IOMMU static calls with clear default ops Leon Romanovsky
2024-07-22 15:10 ` Christoph Hellwig
2024-07-22 15:44 ` Leon Romanovsky
2024-07-22 15:49 ` Christoph Hellwig
2024-07-22 16:05 ` Leon Romanovsky [this message]
2024-07-22 23:16 ` Christoph Hellwig
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=20240722160555.GB7022@unreal \
--to=leon@kernel.org \
--cc=eahariha@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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