linux.git/arch/microblaze/mm/init.c, branch for-next

microblaze: don't treat zero reserved memory regions as error

2024-08-25T22:26:30+00:00

Before commit 721f4a6526da ("mm/memblock: remove empty dummy entry") the
check for non-zero of memblock.reserved.cnt in mmu_init() would always
be true either because  memblock.reserved.cnt is initialized to 1 or
because there were memory reservations earlier.

The removal of dummy empty entry in memblock caused this check to fail
because now memblock.reserved.cnt is initialized to 0.

Remove the check for non-zero of memblock.reserved.cnt because it's
perfectly fine to have an empty memblock.reserved array that early in
boot.

Reported-by: Guenter Roeck 
Signed-off-by: Mike Rapoport 
Reviewed-by: Wei Yang 
Tested-by: Guenter Roeck 
Link: https://lore.kernel.org/r/20240729053327.4091459-1-rppt@kernel.org
Signed-off-by: Guenter Roeck

microblaze: Remove zalloc_maybe_bootmem()

2023-08-23T07:35:22+00:00

Last user of zalloc_maybe_bootmem() was removed by
commit 4308e3c9e1ea ("microblaze/PCI: Remove unused allocation & free
of PCI host bridge structure")

Remove it.

Signed-off-by: Christophe Leroy 
Link: https://lore.kernel.org/r/bfb1601cac24d7ef8e741c83f9301e4a5a87a0b5.1692124505.git.christophe.leroy@csgroup.eu
Signed-off-by: Michal Simek

microblaze/mm: enable ARCH_HAS_VM_GET_PAGE_PROT

2022-07-18T00:14:38+00:00

This enables ARCH_HAS_VM_GET_PAGE_PROT on the platform and exports
standard vm_get_page_prot() implementation via DECLARE_VM_GET_PAGE_PROT,
which looks up a private and static protection_map[] array.  Subsequently
all __SXXX and __PXXX macros can be dropped which are no longer needed.

Link: https://lkml.kernel.org/r/20220711070600.2378316-9-anshuman.khandual@arm.com
Signed-off-by: Anshuman Khandual 
Cc: Michal Simek 
Cc: Arnd Bergmann 
Cc: Brian Cain 
Cc: Catalin Marinas 
Cc: Christophe Leroy 
Cc: Christoph Hellwig 
Cc: Christoph Hellwig 
Cc: Chris Zankel 
Cc: "David S. Miller" 
Cc: Dinh Nguyen 
Cc: Geert Uytterhoeven 
Cc: Guo Ren 
Cc: Heiko Carstens 
Cc: Huacai Chen 
Cc: Ingo Molnar 
Cc: "James E.J. Bottomley" 
Cc: Jeff Dike 
Cc: Jonas Bonn 
Cc: Michael Ellerman 
Cc: Nicholas Piggin 
Cc: Palmer Dabbelt 
Cc: Paul Mackerras 
Cc: Paul Walmsley 
Cc: Richard Henderson 
Cc: Rich Felker 
Cc: Russell King 
Cc: Sam Ravnborg 
Cc: Stafford Horne 
Cc: Thomas Bogendoerfer 
Cc: Thomas Gleixner 
Cc: Vasily Gorbik 
Cc: Vineet Gupta 
Cc: WANG Xuerui 
Cc: Will Deacon 
Cc: Yoshinori Sato 
Signed-off-by: Andrew Morton

microblaze: Add support for reserved memory defined by DT

2022-04-21T08:54:57+00:00

In DT reserved memory nodes can be added as is described by
Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
but Microblaze didn't have a support for it. The similar change was done
for ARC by commit 1b10cb21d888 ("ARC: add support for reserved memory
defined by device tree"). It is pretty much enough to call
early_init_fdt_scan_reserved_mem().
Microblaze is not using initial_boot_params that's why there is no need to
call early_init_fdt_reserve_self().

Signed-off-by: Michal Simek 
Link: https://lore.kernel.org/r/da4395776bf0de7207767abcc8a5df05bf411816.1645795048.git.michal.simek@xilinx.com

microblaze: Wire memblock_dump_all()

2022-04-21T08:54:57+00:00

Wire memblock_dump_all() to be able to see the whole memblock allocation.
Dumps are enabled by passing memblock=debug via kernel command line.

Signed-off-by: Michal Simek 
Link: https://lore.kernel.org/r/6f480b6010068872f429df69c8894cc3f1f38f46.1645795048.git.michal.simek@xilinx.com

microblaze: simplify pte_alloc_one_kernel()

2021-09-03T16:58:15+00:00

The microblaze's implementation of pte_alloc_one_kernel() used
memblock_alloc_try_nid_raw() along with clear_page() to allocated a zeroed
page during early setup.

Replace calls of these functions with a call to memblock_alloc_try_nid()
that already returns zeroed page and respects the same allocation limits
as memblock_alloc_try_nid_raw().

While on it drop early_get_page() wrapper that was only used in
pte_alloc_one_kernel().

Link: https://lkml.kernel.org/r/20210714123739.16493-3-rppt@kernel.org
Signed-off-by: Mike Rapoport 
Reviewed-by: David Hildenbrand 
Cc: Michal Simek 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mm: move mem_init_print_info() into mm_init()

2021-04-30T18:20:42+00:00

mem_init_print_info() is called in mem_init() on each architecture, and
pass NULL argument, so using void argument and move it into mm_init().

Link: https://lkml.kernel.org/r/20210317015210.33641-1-wangkefeng.wang@huawei.com
Signed-off-by: Kefeng Wang 
Acked-by: Dave Hansen 	[x86]
Reviewed-by: Christophe Leroy 	[powerpc]
Acked-by: David Hildenbrand 
Tested-by: Anatoly Pugachev 	[sparc64]
Acked-by: Russell King 	[arm]
Acked-by: Mike Rapoport 
Cc: Catalin Marinas 
Cc: Richard Henderson 
Cc: Guo Ren 
Cc: Yoshinori Sato 
Cc: Huacai Chen 
Cc: Jonas Bonn 
Cc: Palmer Dabbelt 
Cc: Heiko Carstens 
Cc: "David S. Miller" 
Cc: "Peter Zijlstra" 
Cc: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

microblaze: tag highmem_setup() with __meminit

2021-03-02T13:26:40+00:00

With commit a0cd7a7c4bc0 ("mm: simplify free_highmem_page() and
free_reserved_page()") the kernel test robot complains about a warning:

WARNING: modpost: vmlinux.o(.text.unlikely+0x23ac): Section mismatch in
  reference from the function highmem_setup() to the function
  .meminit.text:memblock_is_reserved()

This has been broken ever since microblaze added highmem support,
because memblock_is_reserved() was already tagged with "__init" back then -
most probably the function always got inlined, so we never stumbled over
it.

We need __meminit because __init_memblock defaults to that without
CONFIG_ARCH_KEEP_MEMBLOCK" and __init_memblock is not used outside memblock
code.

Reported-by: kernel test robot 
Fixes: 2f2f371f8907 ("microblaze: Highmem support")
Cc: Andrew Morton 
Cc: Michal Simek 
Cc: Mike Rapoport 
Cc: Andrew Morton 
Cc: Thomas Gleixner 
Cc: Arvind Sankar 
Cc: Ira Weiny 
Cc: Randy Dunlap 
Cc: Oscar Salvador 
Cc: Anshuman Khandual 
Signed-off-by: David Hildenbrand 
Reviewed-by: Oscar Salvador 
Link: https://lore.kernel.org/r/20210301114749.47914-1-david@redhat.com
Signed-off-by: Michal Simek

Merge tag 'microblaze-v5.11' of git://git.monstr.eu/linux-2.6-microblaze

2020-12-16T20:04:39+00:00

Pull microblaze updates from Michal Simek:
 "The biggest change is to remove support for noMMU configuration.

  FPGAs are bigger so people use Microblaze with MMU for a lot of years
  and there is likely no user of this code anymore. No one is updating
  libraries for this configuration either.

   - Remove noMMU support

   - Add support for TIF_NOTIFY_SIGNAL

   - Small header fix"

* tag 'microblaze-v5.11' of git://git.monstr.eu/linux-2.6-microblaze:
  microblaze: Remove noMMU code
  microblaze: add support for TIF_NOTIFY_SIGNAL
  microblaze: Replace  by

microblaze: Remove noMMU code

2020-11-26T15:39:35+00:00

This configuration is obsolete and likely none is really using it. That's
why remove it to simplify code.

Note about CONFIG_MMU in hw_exception_handler.S is left intentionally
for better comment understanding.

Cc: Mike Rapoport 
Cc: Arnd Bergmann 
Signed-off-by: Michal Simek 
Acked-by: Mike Rapoport 
Acked-by: Arnd Bergmann 
Link: https://lore.kernel.org/r/43486cab370e0c0a79860120b71e0caac75a7e44.1606397528.git.michal.simek@xilinx.com