From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
<xen-devel@lists.xensource.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <konrad.wilk@oracle.com>,
<Ian.Campbell@citrix.com>, <will.deacon@arm.com>
Subject: Re: [PATCH v2 RFC 2/8] arm: introduce a global dma_ops pointer
Date: Fri, 2 Aug 2013 12:42:16 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1308021238570.4893@kaball.uk.xensource.com> (raw)
In-Reply-To: <20130731200135.GZ24642@n2100.arm.linux.org.uk>
On Wed, 31 Jul 2013, Russell King - ARM Linux wrote:
> On Wed, Jul 31, 2013 at 08:54:06PM +0100, Stefano Stabellini wrote:
> > Initially set dma_ops to arm_dma_ops.
> > Use dma_ops instead of arm_dma_ops in dmabounce.
> >
> > Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > CC: will.deacon@arm.com
> > CC: linux@arm.linux.org.uk
>
> If you're using swiotlb, there's little point in converting dmabounce
> to be able to use it, because it's basically providing the same
> functionality - dmabounce is there to do software buffer bouncing within
> the DMA to move streaming buffers from DMA-inaccessible memory into
> DMA-accessible memory.
>
> It's original use is with older SoCs with buggy DMA (eg, those which
> can only address alternate 1MB chunks of memory for example) but also
> got used in situations where alternative solutions would've been better
> (like using swiotlb.) I've been discouraging its use as it's suffered
> from memory exhaustion problems (there's a number of threads and bug
> reports which were never solved about IXP4xx(?) platforms suffering
> this due to this bouncing.)
OK, I'll let dmabounce keep using arm_dma_ops directly (instead of
dma_ops).
Should I add "depends on !DMABOUNCE" to the SWIOTLB Kconfig entry too?
next prev parent reply other threads:[~2013-08-02 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 19:52 [PATCH v2 RFC 0/8] enable swiotlb-xen on arm and arm64 Stefano Stabellini
2013-07-31 19:54 ` [PATCH v2 RFC 1/8] arm: make SWIOTLB available Stefano Stabellini
2013-07-31 19:54 ` [PATCH v2 RFC 2/8] arm: introduce a global dma_ops pointer Stefano Stabellini
2013-07-31 20:01 ` Russell King - ARM Linux
2013-08-02 11:42 ` Stefano Stabellini [this message]
2013-07-31 19:54 ` [PATCH v2 RFC 3/8] arm64: do not initialize arm64_swiotlb if dma_ops is already set Stefano Stabellini
2013-07-31 19:54 ` [PATCH v2 RFC 4/8] xen/arm,arm64: move Xen initialization earlier Stefano Stabellini
2013-07-31 19:54 ` [PATCH v2 RFC 5/8] xen: introduce XENMEM_get_dma_buf and xen_put_dma_buf Stefano Stabellini
2013-07-31 19:54 ` [PATCH v2 RFC 6/8] xen: make xen_create_contiguous_region return the dma address Stefano Stabellini
2013-07-31 19:54 ` [PATCH v2 RFC 7/8] swiotlb-xen: support autotranslate guests Stefano Stabellini
2013-08-01 12:19 ` David Vrabel
2013-07-31 19:54 ` [PATCH v2 RFC 8/8] xen/arm,arm64: enable SWIOTLB_XEN Stefano Stabellini
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=alpine.DEB.2.02.1308021238570.4893@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xensource.com \
/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
all inboxes | Powered by JetHome®