From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: relax conditions required for enabling Contiguous Memory Allocator
Date: Tue, 21 Aug 2012 13:12:56 +0100 [thread overview]
Message-ID: <20120821121256.GT18957@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201208202001.23443.arnd@arndb.de>
On Mon, Aug 20, 2012 at 08:01:23PM +0000, Arnd Bergmann wrote:
> The patch looks simple, but I want a better explanation for it.
> When we went through all possible cases, we decided that:
>
> * ARMv6+ need CMA to avoid the double mapping problem.
> * ARMv4/v5 cannot generally use CMA because it doesn't work
> together with DMABOUNCE. I don't remember if it was the
> only problem, but I definitely remember this was intentional.
> * We want a common kernel for all ARMv6+ eventually, and a
> separate kernel for all ARMv4/v5 ones.
>
> If the reasoning has changed, please try to explain the full
> situation.
Indeed.
> On a related topic, what happened to the idea that
> ARMv6+ is broken without CMA? I noticed that it's optional
> now.
With Marek's patch, it's always selected for MMU-based builds (it can't
be disabled). Before the patch, it was always selected for V6 and later
CPUs.
And the description doesn't make sense:
"Contiguous Memory Allocator requires only paging and MMU enabled not
particular CPU architectures,"
what does "only paging and MMU enabled" mean? Are you trying to say that
CMA only requires a kernel with MMU support?
next prev parent reply other threads:[~2012-08-21 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 6:16 [PATCH] ARM: relax conditions required for enabling Contiguous Memory Allocator Marek Szyprowski
2012-08-20 11:29 ` Prabhakar Lad
2012-08-20 20:01 ` Arnd Bergmann
2012-08-21 12:12 ` Russell King - ARM Linux [this message]
2012-08-21 14:47 ` Marek Szyprowski
2012-08-21 14:46 ` Marek Szyprowski
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=20120821121256.GT18957@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@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).