From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Subject: Re: [PATCH v2 0/4] ARC: allow to use IOC and non-IOC DMA devices simultaneously
Date: Mon, 13 Aug 2018 17:27:19 +0000 [thread overview]
Message-ID: <1534181238.3962.74.camel@synopsys.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075012B08C82C@us01wembx1.internal.synopsys.com>
On Mon, 2018-08-13 at 16:19 +0000, Vineet Gupta wrote:
> On 07/30/2018 09:26 AM, Eugeniy Paltsev wrote:
> > The ARC HS processor provides an IOC port (I/O coherency bus
> > interface) that allows external devices such as DMA devices
> > to access memory through the cache hierarchy, providing
> > coherency between I/O transactions and the complete memory
> > hierarchy.
>
> You didn't pay attention to my previous comment on this !
> IOC port can be considered a micro-architecture optimization (an important one
> though). The main thing is hardware snooping DMA transactions which enabled IOC in
> first place.
Ok, I'll rewrite this commit message.
> > Some recent SoC with ARC HS (like HSDK) allow to select bus
> > port (IOC or non-IOC port) for connecting DMA devices in runtime.
>
> Again you mention the port but none of your 4 patches actually touch the port
> itself in programming it.
Ok.
>
> > With this patch we can use both HW-coherent and regular DMA
> > peripherals simultaneously.
> >
> > NOTE:
> > This patch series was stress tested on HSDK with iperf3 (ethernet)
> > and bonie++ (usb and sdio) in three configurations:
> > * IOC enabled globaly
> > * IOC disabled globaly
> > * IOC enabled partially (USB & SDIO are connected via IOC AXI port,
> > ethernet is connected to DDR AXI port (non-IOC port)
> >
> > NOTE:
> > If you want to test some device without IOC it is not enough
> > to remove "dma-coherent" property from dts. You had to remap this
> > device to regular DDR AXI port intead of IOC AXI port.
>
> Why are we not doing that for the GPU as part of this series.
We still need to upstream couple of minor changes in Vivante driver before enable
it for HSDK.
>
> > You also need to apply 3 following patches firstly:
> > https://www.mail-archive.com/linux-snps-arc@lists.infradead.org/msg03865.html
> > https://www.mail-archive.com/linux-snps-arc@lists.infradead.org/msg03889.html
> > https://www.mail-archive.com/linux-snps-arc@lists.infradead.org/msg03887.html
> >
> > NOTE:
> > We don't touch any aperture configuration in this patch series. So we
> > don't switch any devices between IOC and non-IOC AXI ports on any board.
> > It can be done later if it is required.
> >
> > Changes v1->v2 (Thanks to Christoph):
> > * Don't select DMA_DIRECT_OPS explicitly as it is already selected by
> > DMA_NONCOHERENT_OPS
> > * Remove check for HIGHMEM pages from arch_dma_{alloc, free}
> >
> > Eugeniy Paltsev (4):
> > ARC: DTS: mark DMA devices connected through IOC port as dma-coherent
> > ARC: allow to use IOC and non-IOC DMA devices simultaneously
> > ARC: IOC: panic if both IOC and ZONE_HIGHMEM enabled
> > ARC: don't check for HIGHMEM pages in arch_dma_alloc
> >
> > arch/arc/boot/dts/axc003.dtsi | 26 ++++++++++++++++
> > arch/arc/boot/dts/axc003_idu.dtsi | 26 ++++++++++++++++
> > arch/arc/boot/dts/hsdk.dts | 4 +++
> > arch/arc/include/asm/dma-mapping.h | 13 ++++++++
> > arch/arc/mm/cache.c | 30 +++++++++---------
> > arch/arc/mm/dma.c | 62 +++++++++++++++++++-------------------
> > 6 files changed, 115 insertions(+), 46 deletions(-)
> > create mode 100644 arch/arc/include/asm/dma-mapping.h
> >
>
>
--
Eugeniy Paltsev
next prev parent reply other threads:[~2018-08-13 17:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 16:26 [PATCH v2 0/4] ARC: allow to use IOC and non-IOC DMA devices simultaneously Eugeniy Paltsev
2018-07-30 16:26 ` Eugeniy Paltsev
2018-07-30 16:26 ` [PATCH v2 1/4] ARC: DTS: mark DMA devices connected through IOC port as dma-coherent Eugeniy Paltsev
2018-07-30 16:26 ` Eugeniy Paltsev
2018-07-30 16:26 ` [PATCH v2 2/4] ARC: allow to use IOC and non-IOC DMA devices simultaneously Eugeniy Paltsev
2018-07-30 16:26 ` Eugeniy Paltsev
2018-08-13 16:24 ` Vineet Gupta
2018-08-13 16:24 ` Vineet Gupta
2018-08-13 17:08 ` Eugeniy Paltsev
2018-08-13 17:08 ` Eugeniy Paltsev
2018-08-20 22:34 ` Vineet Gupta
2018-08-20 22:34 ` Vineet Gupta
2018-08-22 18:40 ` Eugeniy Paltsev
2018-08-22 18:40 ` Eugeniy Paltsev
2018-08-23 14:05 ` hch
2018-08-23 14:05 ` hch
2018-09-04 18:13 ` Vineet Gupta
2018-09-04 18:13 ` Vineet Gupta
2018-07-30 16:26 ` [PATCH v2 3/4] ARC: IOC: panic if both IOC and ZONE_HIGHMEM enabled Eugeniy Paltsev
2018-07-30 16:26 ` Eugeniy Paltsev
2018-07-30 16:26 ` [PATCH v2 4/4] ARC: don't check for HIGHMEM pages in arch_dma_alloc Eugeniy Paltsev
2018-07-30 16:26 ` Eugeniy Paltsev
2018-07-31 8:08 ` Christoph Hellwig
2018-07-31 8:08 ` Christoph Hellwig
2018-08-13 16:19 ` [PATCH v2 0/4] ARC: allow to use IOC and non-IOC DMA devices simultaneously Vineet Gupta
2018-08-13 16:19 ` Vineet Gupta
2018-08-13 17:27 ` Eugeniy Paltsev [this message]
2018-08-13 17:27 ` Eugeniy Paltsev
2018-08-13 17:39 ` Vineet Gupta
2018-08-13 17:39 ` Vineet Gupta
2018-09-04 20:14 ` Vineet Gupta
2018-09-04 20:14 ` Vineet Gupta
2018-09-04 21:11 ` Christoph Hellwig
2018-09-04 21:11 ` Christoph Hellwig
2018-09-04 21:34 ` Vineet Gupta
2018-09-04 21:34 ` Vineet Gupta
2018-09-04 21:38 ` Christoph Hellwig
2018-09-04 21:38 ` 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=1534181238.3962.74.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).