From: Robin Murphy <robin.murphy@arm.com>
To: Jonathan Richardson <jonathan.richardson@broadcom.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
akpm@linux-foundation.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org
Subject: Re: cma can't activate area on arm64
Date: Fri, 28 Feb 2020 21:00:41 +0000 [thread overview]
Message-ID: <f0b19db7-96d0-a94b-d313-0112f6cbbdba@arm.com> (raw)
In-Reply-To: <CAHrpVsUctu3_V_vqruzP0c6SpcRzWE-5Us7OHEFXHU5hQv5MBQ@mail.gmail.com>
On 2020-02-28 8:34 pm, Jonathan Richardson wrote:
> On Fri, Feb 28, 2020 at 12:16 PM Nicolas Saenz Julienne
> <nsaenzjulienne@suse.de> wrote:
>>
>> 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.
>
> Sure, it is attached. Thanks for taking a look. This is a boot with
> "arch/arm64/configs/defconfig" and the previously mentioned dtb.
[ 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.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-28 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHrpVsXay=8q6a9Vee3wnLVAKHdd_c5+miHbvz+1uqJAEoRZ0A@mail.gmail.com>
2020-02-27 9:56 ` cma can't activate area on arm64 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 [this message]
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=f0b19db7-96d0-a94b-d313-0112f6cbbdba@arm.com \
--to=robin.murphy@arm.com \
--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=nsaenzjulienne@suse.de \
--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