From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Jonathan Richardson <jonathan.richardson@broadcom.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, akpm@linux-foundation.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: cma can't activate area on arm64
Date: Fri, 28 Feb 2020 21:16:27 +0100 [thread overview]
Message-ID: <13501c8a45e8fd8d98d727f036e96c54faa8425a.camel@suse.de> (raw)
In-Reply-To: <CAHrpVsXuTEQR7GG6pS4AVjU=ABvmpec7wx3trZuoHz1yf97SVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Fri, 2020-02-28 at 11:56 -0800, Jonathan Richardson wrote:
> This is stingray (arch/arm64/boot/dts/broadcom/stingray/bcm958742k.dts).
> cma is specified on cmdline as "cma=1G". The full boot log was in the
> attachment.
Would you mind attaching it again, I was added to the conversation later.
> > you use a fixed base? Also, do you want the CMA in ZONE_DMA or
> > ZONE_DMA32?
>
> I'm not sure which zone we want it in. I'm assuming ZONE_DMA32. Before
> that change there was only one zone. If I disable ZONE_DMA I don't see
> the error, though I haven't tested anything. I don't really understand why
> ZONE_DMA is enabled by default if it's a requirement for Rpi only.
> I'm assuming it should work as is with both zones enabled but not clear how
> cma spans the two zones. Was there a reason for having both zones enabled as
> the default?
It's enabled by default to be able to boot all boards with a common kernel
image.
IIRC the allocation algo for CMA placement tries to fit it as high as possible
in ZONE_DMA32, but I can't really say much more without the logs.
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-28 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 23:42 Jonathan Richardson
2020-02-27 9:56 ` Vlastimil Babka
2020-02-27 17:48 ` Catalin Marinas
2020-02-28 19:56 ` Jonathan Richardson
2020-02-28 20:16 ` Nicolas Saenz Julienne [this message]
2020-02-28 20:34 ` Jonathan Richardson
2020-02-28 21:00 ` Robin Murphy
2020-02-28 23:04 ` Jonathan Richardson
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=13501c8a45e8fd8d98d727f036e96c54faa8425a.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=jonathan.richardson@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=robin.murphy@arm.com \
--cc=vbabka@suse.cz \
/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