From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
Subject: Re: Generating elf kernel ?
Date: Thu, 16 Sep 2010 10:37:32 +0800 [thread overview]
Message-ID: <4C9182EC.5030900@windriver.com> (raw)
In-Reply-To: <20100915114912.06bc7ed1@schlenkerla.am.freescale.net>
Scott Wood wrote:
> On Wed, 15 Sep 2010 16:27:10 +0800
> "tiejun.chen" <tiejun.chen@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
>
>
next prev parent reply other threads:[~2010-09-16 2:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 8:53 Generating elf kernel ? Guillaume Dargaud
2010-09-14 10:08 ` tiejun.chen
2010-09-14 11:27 ` Guillaume Dargaud
2010-09-14 12:57 ` Baurzhan Ismagulov
2010-09-15 8:07 ` Guillaume Dargaud
2010-09-15 8:27 ` tiejun.chen
2010-09-15 14:51 ` Guillaume Dargaud
2010-09-16 3:02 ` tiejun.chen
2010-09-16 7:25 ` Guillaume Dargaud
2010-09-16 7:51 ` tiejun.chen
2010-09-17 9:27 ` Initial kernel command string (Was: Generating elf kernel ?) Guillaume Dargaud
2010-09-17 9:46 ` tiejun.chen
2010-09-20 7:21 ` Guillaume Dargaud
2010-09-20 8:10 ` tiejun.chen
2010-09-15 16:49 ` Generating elf kernel ? Scott Wood
2010-09-16 2:37 ` tiejun.chen [this message]
2010-09-16 17:09 ` Scott Wood
2010-09-17 1:58 ` tiejun.chen
2010-09-17 17:44 ` Scott Wood
2010-09-19 1:40 ` tiejun.chen
2010-09-20 15:43 ` Scott Wood
2010-09-21 1:00 ` Chen, Tiejun
2010-09-21 17:00 ` Scott Wood
2010-09-21 23:35 ` Chen, Tiejun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C9182EC.5030900@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).