mbox series

[0/2] fdt: A couple of no-map fixes

Message ID 20210115114544.1830068-1-qperret@google.com
Headers show
Series fdt: A couple of no-map fixes | expand

Message

Quentin Perret Jan. 15, 2021, 11:45 a.m. UTC 
In the context of a KVM/arm64 thread [1], it became apparent that the
difference in behaviour of EFI and DT with respect to no-map regions was
something worth fixing.

Rob pointed out in that thread that a couple of patches in this area had
been sent but still needed to be integrated together, which is basically
what this series attempts to do.

 - Patch 01 is a generic fix that should make sense on its own;

 - Patch 02 allows the kernel to have a saner behaviour with a broken DT.
   This one had a small rebase conflict (caused by patch 01). I tested
   it in qemu and everything is looking good, the error message shows up
   in dmesg when it should.

Thanks,
Quentin

[1] https://lore.kernel.org/kvmarm/20210108121524.656872-1-qperret@google.com/

KarimAllah Ahmed (1):
  fdt: Properly handle "no-map" field in the memory region

Nicolas Boichat (1):
  of/fdt: Make sure no-map does not remove already reserved regions

 drivers/of/fdt.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

Comments

Rob Herring Jan. 15, 2021, 5:29 p.m. UTC | #1 
On Fri, 15 Jan 2021 11:45:43 +0000, Quentin Perret wrote:
> From: KarimAllah Ahmed <karahmed@amazon.de>
> 
> Mark the memory region with NOMAP flag instead of completely removing it
> from the memory blocks. That makes the FDT handling consistent with the EFI
> memory map handling.
> 
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: devicetree@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: KarimAllah Ahmed <karahmed@amazon.de>
> Signed-off-by: Quentin Perret <qperret@google.com>
> ---
>  drivers/of/fdt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied, thanks!