linux-toradex.git/arch/microblaze/mm, branch v5.18

mm: remove redundant check about FAULT_FLAG_ALLOW_RETRY bit

2022-01-15T14:30:27+00:00

Since commit 4064b9827063 ("mm: allow VM_FAULT_RETRY for multiple
times") allowed VM_FAULT_RETRY for multiple times, the
FAULT_FLAG_ALLOW_RETRY bit of fault_flag will not be changed in the page
fault path, so the following check is no longer needed:

	flags & FAULT_FLAG_ALLOW_RETRY

So just remove it.

[akpm@linux-foundation.org: coding style fixes]

Link: https://lkml.kernel.org/r/20211110123358.36511-1-zhengqi.arch@bytedance.com
Signed-off-by: Qi Zheng 
Cc: Peter Zijlstra 
Cc: Ingo Molnar 
Cc: David Hildenbrand 
Cc: Kirill Shutemov 
Cc: Peter Xu 
Cc: Muchun Song 
Cc: Chengming Zhou 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

microblaze: use is_kernel_text() helper

2021-11-09T18:02:51+00:00

Use is_kernel_text() helper to simplify code.

Link: https://lkml.kernel.org/r/20210930071143.63410-11-wangkefeng.wang@huawei.com
Signed-off-by: Kefeng Wang 
Acked-by: Michal Simek 
Reviewed-by: Sergey Senozhatsky 
Cc: Alexander Potapenko 
Cc: Alexei Starovoitov 
Cc: Andrey Konovalov 
Cc: Andrey Ryabinin 
Cc: Arnd Bergmann 
Cc: Benjamin Herrenschmidt 
Cc: Borislav Petkov 
Cc: Christophe Leroy 
Cc: "David S. Miller" 
Cc: Dmitry Vyukov 
Cc: Ingo Molnar 
Cc: Ivan Kokshaysky 
Cc: Matt Turner 
Cc: Michael Ellerman 
Cc: Paul Mackerras 
Cc: Petr Mladek 
Cc: Richard Henderson 
Cc: Steven Rostedt 
Cc: Thomas Gleixner 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

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

microblaze/mm/highmem: Add dropped #ifdef back

2020-11-19T19:49:44+00:00

The conversion to generic kmap atomic broke microblaze by removing the
build fail.

Add it back.

Fixes: 7ac1b26b0a72 ("microblaze/mm/highmem: Switch to generic kmap atomic")
Reported-by: Randy Dunlap 
Signed-off-by: Thomas Gleixner 
Cc: Michal Simek

microblaze/mm/highmem: Switch to generic kmap atomic

2020-11-06T22:14:56+00:00

No reason having the same code in every architecture.

Signed-off-by: Thomas Gleixner 
Cc: Michal Simek 
Cc: Arnd Bergmann 
Link: https://lore.kernel.org/r/20201103095857.777445435@linutronix.de

Merge tag 'dma-mapping-5.10' of git://git.infradead.org/users/hch/dma-mapping

2020-10-15T21:43:29+00:00

Pull dma-mapping updates from Christoph Hellwig:

 - rework the non-coherent DMA allocator

 - move private definitions out of 

 - lower CMA_ALIGNMENT (Paul Cercueil)

 - remove the omap1 dma address translation in favor of the common code

 - make dma-direct aware of multiple dma offset ranges (Jim Quinlan)

 - support per-node DMA CMA areas (Barry Song)

 - increase the default seg boundary limit (Nicolin Chen)

 - misc fixes (Robin Murphy, Thomas Tai, Xu Wang)

 - various cleanups

* tag 'dma-mapping-5.10' of git://git.infradead.org/users/hch/dma-mapping: (63 commits)
  ARM/ixp4xx: add a missing include of dma-map-ops.h
  dma-direct: simplify the DMA_ATTR_NO_KERNEL_MAPPING handling
  dma-direct: factor out a dma_direct_alloc_from_pool helper
  dma-direct check for highmem pages in dma_direct_alloc_pages
  dma-mapping: merge  into 
  dma-mapping: move large parts of  to kernel/dma
  dma-mapping: move dma-debug.h to kernel/dma/
  dma-mapping: remove 
  dma-mapping: merge  into 
  dma-contiguous: remove dma_contiguous_set_default
  dma-contiguous: remove dev_set_cma_area
  dma-contiguous: remove dma_declare_contiguous
  dma-mapping: split 
  cma: decrease CMA_ALIGNMENT lower limit to 2
  firewire-ohci: use dma_alloc_pages
  dma-iommu: implement ->alloc_noncoherent
  dma-mapping: add new {alloc,free}_noncoherent dma_map_ops methods
  dma-mapping: add a new dma_alloc_pages API
  dma-mapping: remove dma_cache_sync
  53c700: convert to dma_alloc_noncoherent
  ...