From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "hch@lst.de" <hch@lst.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 3/4] ARC: refactor arch/arc/mm/dma.c
Date: Mon, 30 Jul 2018 10:34:20 +0000 [thread overview]
Message-ID: <1532946859.3059.8.camel@synopsys.com> (raw)
In-Reply-To: <20180726091731.GC24209@lst.de>
On Thu, 2018-07-26 at 11:17 +0200, Christoph Hellwig wrote:
> On Tue, Jul 24, 2018 at 01:10:00PM +0300, Eugeniy Paltsev wrote:
> > Refactoring, no functional change intended.
> >
[snip]
> >
> > *dma_handle = paddr;
> >
> > + /*
> > + * - A coherent buffer needs MMU mapping to enforce non-cachability
> > + * - A highmem page needs a virtual handle (hence MMU mapping)
> > + * independent of cachability.
> > + * kvaddr is kernel Virtual address (0x7000_0000 based)
> > + */
> > + if (PageHighMem(page) || need_coh) {
>
> dma_alloc_attrs clears __GFP_HIGHMEM from the passed in gfp mask, so
> you'll never get a highmem page here.
>
Nice catch, thanks.
Will remove check for highmem page in next patch version.
> That also means you can merge this conditional with the one for the cache
> writeback and invalidation and kill the need_coh flag entirely.
>
> > kvaddr = ioremap_nocache(paddr, size);
> > if (kvaddr == NULL) {
> > __free_pages(page, order);
> > @@ -81,11 +75,9 @@ void arch_dma_free(struct device *dev, size_t size, void *vaddr,
> > {
> > phys_addr_t paddr = dma_handle;
> > struct page *page = virt_to_page(paddr);
> > - int is_non_coh = 1;
> > -
> > - is_non_coh = (attrs & DMA_ATTR_NON_CONSISTENT);
> > + bool is_coh = !(attrs & DMA_ATTR_NON_CONSISTENT);
> >
> > - if (PageHighMem(page) || !is_non_coh)
> > + if (PageHighMem(page) || is_coh)
> > iounmap((void __force __iomem *)vaddr);
> >
>
> Same here.
>
> Also if you clean this up it would be great to take the per-device pfn offset
> into account, even if that isn't used anywhere on arc yet, that is call
> phys_to_dma and dma_to_phys to convert to an from the dma address.
Ok, I'll look at it.
Probably I'll implement it as a separate patch as it is irrelevant to this
patch series topic.
--
Eugeniy Paltsev
next prev parent reply other threads:[~2018-07-30 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 10:09 [PATCH 0/4] ARC: allow to use IOC and non-IOC DMA devices simultaneously Eugeniy Paltsev
2018-07-24 10:09 ` [PATCH 1/4] ARC: DTS: mark DMA devices connected through IOC port as dma-coherent Eugeniy Paltsev
2018-07-24 10:09 ` [PATCH 2/4] ARC: allow to use IOC and non-IOC DMA devices simultaneously Eugeniy Paltsev
2018-07-26 9:13 ` Christoph Hellwig
2018-07-24 10:10 ` [PATCH 3/4] ARC: refactor arch/arc/mm/dma.c Eugeniy Paltsev
2018-07-26 9:17 ` Christoph Hellwig
2018-07-30 10:34 ` Eugeniy Paltsev [this message]
2018-07-24 10:10 ` [PATCH 4/4] ARC: IOC: panic if both IOC and ZONE_HIGHMEM enabled Eugeniy Paltsev
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=1532946859.3059.8.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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).