Re: cma can't activate area on arm64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> [    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




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux