linux-stable.git/arch/mips/kernel/setup.c, branch v5.2

mips: Manually call fdt_init_reserved_mem() method

2019-05-06T03:12:20+00:00

Since memblock-patchset was introduced the reserved-memory nodes are
supported being declared in dt-files. So these nodes are actually parsed
during the arch setup procedure when the early_init_fdt_scan_reserved_mem()
method is called. But due to the arch-specific boot mem_map container
utilization we need to manually call the fdt_init_reserved_mem() method
after all the available and reserved memory has been moved to memblock.
The first function call performed before bootmem_init() by the
early_init_fdt_scan_reserved_mem() routine fails due to the lack of any
memblock memory regions to allocate from at that stage.

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: Serge Semin 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Perform early low memory test

2019-05-03T22:26:10+00:00

memblock subsystem provides a method to optionally test the passed
memory region in case if it was requested via special kernel boot
argument. Lets add the function at the bottom of the arch_mem_init()
method. Testing at this point in the boot sequence should be safe since all
critical areas are now reserved and a minimum of allocations have been
done.

Reviewed-by: Matt Redfearn 
Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: Serge Semin 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Dump memblock regions for debugging

2019-05-03T22:24:12+00:00

It is useful to have the whole memblock memory space printed to console
when basic memlock initializations are done. It can be performed by
ready-to-use method memblock_dump_all(), which prints the available
and reserved memory spaces if memblock=debug kernel parameter is
specified. Lets call it at the very end of arch_mem_init() function,
when all memblock memory and reserved regions are defined, but before
any serious allocation is performed.

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: Serge Semin 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Add reserve-nomap memory type support

2019-05-02T18:27:11+00:00

It might be necessary to prevent the virtual mapping creation for a
requested memory region. For instance there is a "no-map" property
indicating exactly this feature. In this case we need to not only
reserve the specified region by pretending it doesn't exist in the
memory space, but completely remove the range from system just by
removing it from memblock. The same way it's done in default
early_init_dt_reserve_memory_arch() method.

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Matt Redfearn 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Use memblock to reserve the __nosave memory range

2019-05-02T18:24:34+00:00

Originally before legacy bootmem was removed, the memory for the range was
correctly reserved by reserve_bootmem_region(). But since memblock has been
selected for early memory allocation the function can be utilized only
after paging is fully initialized (as it is done by memblock_free_all()
function). So calling it from arch_mem_init() method is prone to errors,
and at this stage we need to reserve the memory in the memblock allocator.

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Matt Redfearn 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Discard post-CMA-init foreach loop

2019-05-02T18:22:37+00:00

Really the loop is pointless, since it walks over memblock-reserved
memory regions and mark them as reserved in memblock. Before
bootmem was removed from the kernel, this loop had been
used to map the memory reserved by CMA into the legacy bootmem
allocator. But now the early memory allocator is memblock,
which is used by CMA for reservation, so we don't need any mapping
anymore.

Reviewed-by: Matt Redfearn 
Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Reserve memory for the kernel image resources

2019-05-02T18:22:08+00:00

The reserved_end variable had been used by the bootmem_init() code
to find a lowest limit of memory available for memmap blob. The original
code just tried to find a free memory space higher than kernel was placed.
This limitation seems justified for the memmap ragion search process, but
I can't see any obvious reason to reserve the unused space below kernel
seeing some platforms place it much higher than standard 1MB. Moreover
the RELOCATION config enables it to be loaded at any memory address.
So lets reserve the memory occupied by the kernel only, leaving the region
below being free for allocations. After doing this we can now discard the
code freeing a space between kernel _text and VMLINUX_LOAD_ADDRESS symbols
since it's going to be free anyway (unless marked as reserved by
platforms).

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Matt Redfearn 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Combine memblock init and memory reservation loops

2019-04-24T22:24:58+00:00

Before bootmem was completely removed from the kernel, the last loop
in the bootmem_init() had been used to reserve the correspondingly
marked regions, initialize sparsemem sections and to free the low memory
pages, which then would be used for early memory allocations. After the
bootmem removing patchset had been merged the loop was left to do the first
two things only. But it didn't do them quite well.

First of all it leaves the BOOT_MEM_INIT_RAM memory types unreserved,
which is definitely bug (although it isn't noticeable due to being used
by the kernel region only, which is fully marked as reserved). Secondly
the reservation is supposed to be done for any memory including the
high one. (I couldn't figure out why the highmem was ignored in the first
place, since platforms and dts' may declare any memory region for
reservation) Thirdly the reserved_end variable had been used here to not
accidentally free memory occupied by kernel. Since we already reserved the
corresponding region higher in this method there is no need in using the
variable here anymore. Fourthly the sparsemem should be aware of all the
memory types in the system including the ROM_DATA even if it is going to
be reserved for the whole system uptime. Finally after all these notes are
fixed the loop of memory reservation can be freely merged into the memory
installation loop as it's done in this patch.

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Matt Redfearn 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Discard rudiments from bootmem_init

2019-04-24T22:24:55+00:00

There is a pointless code left in the bootmem_init() method since
the bootmem allocator removal. First part resides the PFN ranges
calculation loop. The conditional expressions and continue operator
are useless there, since nothing is done after them. Second part is
in RAM ranges installation loop. We can simplify the conditions cascade
a bit without much of the logic redefinition, so to reduce the code
length. In particular the end boundary value can be verified after
the possible reduction to be below max_low_pfn.

Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Matt Redfearn 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

mips: Make sure kernel .bss exists in boot mem pool

2019-04-24T22:24:43+00:00

Current MIPS platform code makes sure the kernel text, data and init
sections are added to the boot memory map pool right after the
arch-specific memory setup method has been executed. But for some reason
the MIPS platform code skipped the kernel .bss section, which definitely
should be in the boot mem pool as well in any case. Lets fix this just be
adding the space between __bss_start and __bss_stop.

Reviewed-by: Matt Redfearn 
Signed-off-by: Serge Semin 
Signed-off-by: Paul Burton 
Cc: Ralf Baechle 
Cc: James Hogan 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Michal Hocko 
Cc: Greg Kroah-Hartman 
Cc: Thomas Bogendoerfer 
Cc: Huacai Chen 
Cc: Stefan Agner 
Cc: Stephen Rothwell 
Cc: Alexandre Belloni 
Cc: Juergen Gross 
Cc: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org