On Tue, 26 Nov 2019 07:10:28 +0900, Richard Weinberger wrote: > > On Fri, Nov 8, 2019 at 6:03 AM Hajime Tazaki <thehajime@xxxxxxxxx> wrote: > > > > From: Octavian Purdila <tavi.purdila@xxxxxxxxx> > > > > LKL is a non MMU architecture and hence there is not much work left to > > do other than initializing the boot allocator and providing the page > > and page table definitions. > > > > The backstore memory is allocated via a host operation and the memory > > size to be used is specified when the kernel is started, in the > > lkl_start_kernel call. > > > > Signed-off-by: H.K. Jerry Chu <hkchu@xxxxxxxxxx> > > Signed-off-by: Hajime Tazaki <thehajime@xxxxxxxxx> > > Signed-off-by: Levente Kurusa <levex@xxxxxxxxx> > > Signed-off-by: Yuan Liu <liuyuan@xxxxxxxxxx> > > Signed-off-by: Octavian Purdila <tavi.purdila@xxxxxxxxx> > > --- > > arch/um/lkl/include/asm/page.h | 14 ++++++ > > arch/um/lkl/include/asm/pgtable.h | 62 +++++++++++++++++++++++ > > arch/um/lkl/include/uapi/asm/host_ops.h | 5 ++ > > arch/um/lkl/mm/bootmem.c | 66 +++++++++++++++++++++++++ > > This is also something which needs unification with UML. > UML in NOMMU mode would be LKL then... At this moment, I leave those part as is; changing LKL to MMU mode makes less possibility to host various underlying environments (non-Linux hosts, non-x86 subarchs). If you have nice suggestions (such as adding texts to docs), it would be definitely helpful. -- Hajime
