Scott Wood wrote: > On Wed, 15 Sep 2010 16:27:10 +0800 > "tiejun.chen" <tiejun.c...@windriver.com> wrote: > >> It's impossible to boot PPC vmlinux format directly if you only change the >> original entry point address, 0xc0000000. > > Why? That's pretty much what the bootwrapper does. Our hypervisor has > directly booted vmlinux this way.
Maybe you misunderstand what I mean. Although you can change entry point of vmlinux 1> can you load the Linux vmlinux directly to the physical address '0' on current bootloader? 2> additionally you have to find a way to pass dtb to the native vmlinux. I believe the hypervisor can boot vmlinux directly. But your so-called vmlinux should be guest OS. And the hypervisor will handle/assit TLB exception for the guest OS on MMU. Right? So you can use the hypervisor to load vmlinux to any physical address as you expect. But the guest OS should not be same as the native Linux. > > Note that in recent kernels physaddr is even set to zero, allowing the > ELF loader to just use that instead of magically knowing the kernel > wants to go at address zero. Sure. > >> For kernel the following is as default: >> v:0xc0000000 --> p:0x0 > > That mapping is set up by code at the entry point of vmlinux, not by > the bootwrapper. Absolutely. Tiejun > > -Scott > > _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
