From: Jonathan Richardson <jonathan.richardson@broadcom.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Catalin Marinas <catalin.marinas@arm.com>,
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>
Subject: Re: cma can't activate area on arm64
Date: Fri, 28 Feb 2020 15:04:02 -0800 [thread overview]
Message-ID: <CAHrpVsUGQ31yd_h8AEPzaecHMvjt+5cqDWmPs1qTaL=NeuFwYA@mail.gmail.com> (raw)
In-Reply-To: <f0b19db7-96d0-a94b-d313-0112f6cbbdba@arm.com>
> [ 0.000000] efi: SMBIOS=0x85c90000 SMBIOS 3.0=0x85a20000 ACPI
> 2.0=0x85d50000 MEMATTR=0x8945e118 MEMRESERVE=0x85f85018
> [ 0.000000] crashkernel reserved: 0x00000000e0000000 -
> 0x0000000100000000 (512 MB)
> [ 0.000000] cma: Reserved 1024 MiB at 0x00000000a0000000
> ...
> [ 0.000000] Zone ranges:
> [ 0.000000] DMA [mem 0x0000000080000000-0x00000000bfffffff]
> [ 0.000000] DMA32 [mem 0x00000000c0000000-0x00000000ffffffff]
>
> Well there's your problem - both zones are only nominally 1GB to begin
> with, and both have stuff in them before we even get to placing CMA. To
> be honest, even without ZONE_DMA that looks pretty tight.
>
> Robin.
OK I see. I don't get the zone range debugs with my working vs generic
defconfig. I'm not sure why. We have quite a bit reserved memory. I
understand better what's happening now, thank you.
Jon
prev parent reply other threads:[~2020-02-28 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 23:42 cma can't activate area on arm64 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
2020-02-28 20:34 ` Jonathan Richardson
2020-02-28 21:00 ` Robin Murphy
2020-02-28 23:04 ` Jonathan Richardson [this message]
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='CAHrpVsUGQ31yd_h8AEPzaecHMvjt+5cqDWmPs1qTaL=NeuFwYA@mail.gmail.com' \
--to=jonathan.richardson@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=nsaenzjulienne@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).