forked from Minki/linux
c2edb35ae3
KIO region placement may be specified in the device tree, that's why it's initialized with the rest of MMU after the early_init_devtree. In order to support KASAN the MMU must be initialized earlier. Separate KIO initialization from the rest of MMU initialization. Reinitialize KIO if its location is specified in the device tree. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
35 lines
641 B
C
35 lines
641 B
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
static inline void init_mmu(void)
|
|
{
|
|
}
|
|
|
|
static inline void init_kio(void)
|
|
{
|
|
}
|
|
|
|
static inline void enter_lazy_tlb(struct mm_struct *mm, struct task_struct *tsk)
|
|
{
|
|
}
|
|
|
|
static inline int init_new_context(struct task_struct *tsk,struct mm_struct *mm)
|
|
{
|
|
return 0;
|
|
}
|
|
|
|
static inline void destroy_context(struct mm_struct *mm)
|
|
{
|
|
}
|
|
|
|
static inline void activate_mm(struct mm_struct *prev, struct mm_struct *next)
|
|
{
|
|
}
|
|
|
|
static inline void switch_mm(struct mm_struct *prev, struct mm_struct *next,
|
|
struct task_struct *tsk)
|
|
{
|
|
}
|
|
|
|
static inline void deactivate_mm(struct task_struct *tsk, struct mm_struct *mm)
|
|
{
|
|
}
|