From: Scott Wood <scottwood@freescale.com>
To: "tiejun.chen" <tiejun.chen@windriver.com>
Cc: linuxppc-dev@lists.ozlabs.org, Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
Subject: Re: Generating elf kernel ?
Date: Fri, 17 Sep 2010 12:44:48 -0500 [thread overview]
Message-ID: <20100917124448.255b08cc@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <4C92CB51.5010008@windriver.com>
On Fri, 17 Sep 2010 09:58:41 +0800
"tiejun.chen" <tiejun.chen@windriver.com> wrote:
> Scott Wood wrote:
> > The guest OS *is* the same as native Linux, as far as TLB handling is
> > concerned.
>
> Looks you means the TLB exception handler should be same between the native and
> the guest OS. Right?
Yes.
> Here I assume we're talking about e500mc since as far as I know for Freescale
> only e500mc is designed to support virtual machine based on ISA 2.0.6.
Yes, though there's nothing preventing virtualization on cores without
category E.HV (KVM supports this) -- it's just slower.
> I also know all TLB exceptions can direct to the guest OS when we enable
> EPCR[DTLBGS|ITLBGS|DSIGS|ISIGS]. But some TLB instructions (i.e. tlbwe )are the
> privileged instructions. So the guest OS always trap into the hypervisor and
> then the hypervisor should complete the real action with appropriate physical
> address.
Yes, of course. But that's not the point. I was just using it as a
convenient example because that's what I've recently done ELF loading
with... There's no reason U-Boot couldn't do the same if its ELF
loader were updated to support device trees. Currently U-Boot loads
bootwrapperless uImages to physical address zero.
And FWIW, we have run setups where our hv loads Linux to true
physical zero (with the hv living elsewhere), not just guest physical.
-Scott
next prev parent reply other threads:[~2010-09-17 17:45 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
2010-09-16 17:09 ` Scott Wood
2010-09-17 1:58 ` tiejun.chen
2010-09-17 17:44 ` Scott Wood [this message]
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=20100917124448.255b08cc@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tiejun.chen@windriver.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).