From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-kernel@vger.kernel.org, Cai Huoqing <caihuoqing@baidu.com>,
Paul Mackerras <paulus@samba.org>,
Peter Huewe <peterhuewe@gmx.de>,
linuxppc-dev@lists.ozlabs.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: ibmvtpm: Make use of dma_alloc_coherent()
Date: Tue, 12 Oct 2021 20:40:32 +0300 [thread overview]
Message-ID: <c36327cce24449b3eb79209c374514e750b38eb4.camel@kernel.org> (raw)
In-Reply-To: <20211012154325.GI2688930@ziepe.ca>
On Tue, 2021-10-12 at 12:43 -0300, Jason Gunthorpe wrote:
> On Tue, Oct 12, 2021 at 06:29:58PM +0300, Jarkko Sakkinen wrote:
> > On Mon, 2021-10-11 at 00:01 +0800, Cai Huoqing wrote:
> > > Replacing kmalloc/kfree/get_zeroed_page/free_page/dma_map_single/
> > ~~~~~~~~~
> > Replace
> >
> > > dma_unmap_single() with dma_alloc_coherent/dma_free_coherent()
> > > helps to reduce code size, and simplify the code, and coherent
> > > DMA will not clear the cache every time.
> > >
> > > Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> >
> > If this does not do functionally anything useful, there's no
> > reason to apply this.
>
> At least in this case it looks like the ibmvtpm is not using the DMA
> API properly. There is no sync after each data transfer. Replacing
> this wrong usage with the coherent API is reasonable.
Thank you. As long as this is documented to the commit message,
I'm cool with the change itself.
E.g. something like this would be perfectly fine replacement for the
current commit message:
"The current usage pattern for the DMA API is inappropriate, as
data transfers are not synced. Replace the existing DMA code
with the coherent DMA API."
/Jarkko
next prev parent reply other threads:[~2021-10-12 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 16:01 [PATCH] tpm: ibmvtpm: Make use of dma_alloc_coherent() Cai Huoqing
2021-10-12 15:29 ` Jarkko Sakkinen
2021-10-12 15:43 ` Jason Gunthorpe
2021-10-12 17:40 ` Jarkko Sakkinen [this message]
2021-10-12 21:01 ` David Laight
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=c36327cce24449b3eb79209c374514e750b38eb4.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=caihuoqing@baidu.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=peterhuewe@gmx.de \
/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).