From: Peter Hurley <peter@hurleysoftware.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
David Woodhouse <dwmw2@infradead.org>,
Don Dutile <ddutile@redhat.com>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, iommu@lists.linux-foundation.org,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH v3 0/5] enhance DMA CMA on x86
Date: Tue, 30 Sep 2014 21:49:54 -0400 [thread overview]
Message-ID: <542B5DC2.8020806@hurleysoftware.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1410010131380.4455@nanos>
On 09/30/2014 07:45 PM, Thomas Gleixner wrote:
> Whether the proposed patchset is the correct solution to support it is
> a completely different question.
This patchset has been in mainline since 3.16 and has already caused
regressions, so the question of whether this is the correct solution has
already been answered.
> So either you stop this right now and help Akinobu to find the proper
> solution
If this is only a test platform for ARM parts then I don't think it
unreasonable to suggest forking x86 swiotlb support into a iommu=cma
selector that gets DMA mapping working for this test platform and doesn't
cause a bunch of breakage.
Which is different than if the plan is to ship production units for x86;
then a general purpose solution will be required.
As to the good design of a general purpose solution for allocating and
mapping huge order pages, you are certainly more qualified to help Akinobu
than I am.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-10-01 1:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:08 [PATCH v3 0/5] enhance DMA CMA on x86 Akinobu Mita
2014-04-15 13:08 ` [PATCH v3 1/5] x86: make dma_alloc_coherent() return zeroed memory if CMA is enabled Akinobu Mita
2014-04-16 19:44 ` Andrew Morton
2014-04-17 15:40 ` Akinobu Mita
2014-04-15 13:08 ` [PATCH v3 2/5] x86: enable DMA CMA with swiotlb Akinobu Mita
2014-04-15 13:08 ` [PATCH v3 3/5] intel-iommu: integrate DMA CMA Akinobu Mita
2014-04-15 13:08 ` [PATCH v3 4/5] memblock: introduce memblock_alloc_range() Akinobu Mita
2014-04-15 13:08 ` [PATCH v3 5/5] cma: add placement specifier for "cma=" kernel parameter Akinobu Mita
2014-09-27 14:30 ` [PATCH v3 0/5] enhance DMA CMA on x86 Peter Hurley
2014-09-28 0:31 ` Akinobu Mita
2014-09-29 12:09 ` Peter Hurley
2014-09-29 14:32 ` Akinobu Mita
2014-09-30 14:34 ` Peter Hurley
2014-09-30 23:23 ` Akinobu Mita
2014-09-30 23:45 ` Thomas Gleixner
2014-09-30 23:49 ` Peter Hurley
2014-10-01 1:49 ` Peter Hurley [this message]
2014-10-01 9:05 ` Thomas Gleixner
2014-10-02 16:41 ` Konrad Rzeszutek Wilk
2014-10-02 22:03 ` Peter Hurley
2014-10-02 23:08 ` Akinobu Mita
2014-10-03 13:40 ` Konrad Rzeszutek Wilk
2014-10-03 14:27 ` Peter Hurley
2014-10-03 16:06 ` Akinobu Mita
2014-10-03 16:33 ` konrad wilk
2014-10-03 16:39 ` Peter Hurley
2014-10-05 6:01 ` Akinobu Mita
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=542B5DC2.8020806@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).