lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 20 Nov 2020 11:39:34 +0000
From:   Catalin Marinas <>
To:     Nicolas Saenz Julienne <>,,,,
Cc:     Will Deacon <>,,,,,,,,,,,
Subject: Re: [PATCH v7 0/7] arm64: Default to 32-bit wide ZONE_DMA

On Thu, 19 Nov 2020 18:53:52 +0100, Nicolas Saenz Julienne wrote:
> Using two distinct DMA zones turned out to be problematic. Here's an
> attempt go back to a saner default.
> I tested this on both a RPi4 and QEMU.

Applied to arm64 (for-next/zone-dma-default-32-bit), thanks!

[1/7] arm64: mm: Move reserve_crashkernel() into mem_init()
[2/7] arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()
[3/7] of/address: Introduce of_dma_get_max_cpu_address()
[4/7] of: unittest: Add test for of_dma_get_max_cpu_address()
[5/7] arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges
[6/7] arm64: mm: Set ZONE_DMA size based on early IORT scan
[7/7] mm: Remove examples from enum zone_type comment


Powered by blists - more mailing lists