[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9208de061fe2b9ee7b74206b3cd52cc116e43ac0.camel@suse.de>
Date: Mon, 21 Oct 2019 19:55:25 +0200
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Qian Cai <cai@....pw>
Cc: f.fainelli@...il.com, mbrugger@...e.com, marc.zyngier@....com,
catalin.marinas@....com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Rob Herring <robh+dt@...nel.org>,
linux-rpi-kernel@...ts.infradead.org, m.szyprowski@...sung.com,
Robin Murphy <Robin.Murphy@....com>, phill@...pberrypi.org,
will@...nel.org, Christoph Hellwig <hch@....de>,
linux-arm-kernel@...ts.infradead.org, wahrenst@....net
Subject: Re: [PATCH v6 3/4] arm64: use both ZONE_DMA and ZONE_DMA32
On Mon, 2019-10-21 at 13:25 -0400, Qian Cai wrote:
> > On Oct 21, 2019, at 1:01 PM, Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
> > wrote:
> >
> > Could you enable CMA debugging to see if anything interesting comes out of
> > it.
>
> I did but nothing interesting came out. Did you use the same config I gave?
Yes, aside from enabling ZONE_DMA.
> Also, it has those cmdline.
>
> page_poison=on page_owner=on numa_balancing=enable \
> systemd.unified_cgroup_hierarchy=1 debug_guardpage_minorder=1 \
> page_alloc.shuffle=1
No luck, still works for me even after adding those extra flags. IIRC most of
them (if not all) are not even parsed by the time CMA is configured.
So, can you confirm the zones setup you're seeing is similar to this one:
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] DMA [mem 0x00000000802f0000-0x00000000bfffffff]
[ 0.000000][ T0] DMA32 [mem 0x00000000c0000000-0x00000000ffffffff]
[ 0.000000][ T0] Normal [mem 0x0000000100000000-0x00000093fcffffff]
Maybe your memory starts between 0xe0000000-0xffffffff. That would be
problematic (although somewhat unwarranted).
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists