From: Scott Wood <oss@buserror.net>
To: luigi burdo <intermediadc@hotmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"matthew@a-eon.com" <matthew@a-eon.com>,
Trevor Dickinson <contact@a-eon.com>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: Freescale P5020 cpu will be kvm-pr?
Date: Wed, 16 Mar 2016 22:47:25 -0500 [thread overview]
Message-ID: <1458186445.19333.3.camel@buserror.net> (raw)
In-Reply-To: <DUB406-EAS2759FE0784777D029FB586BC88A0@phx.gbl>
On Wed, 2016-03-16 at 07:24 +0100, luigi burdo wrote:
> hi Scott,
> the P5020 mmu is signed by the kernel no book3e found
I don't understand this sentence.
> kvm ppc64 crash if run by qemu.
You didn't show that log.
> in the kernel( 4.5 too)all is enabled we had a base .config by freescale/nix
> where kvm options and book3e where enabled.
You should start with corenet64_smp_defconfig, and enable KVM options plus
PPC_QEMU_E500.
> my suspect is this can be an generated issue by the host uboot
Host U-Boot has nothing to do with KVM.
> or a missed tdb parameter and not a linux kernel problem.
What is tdb?
-Scott
next prev parent reply other threads:[~2016-03-17 3:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 19:03 Freescale P5020 cpu will be kvm-pr? luigi burdo
2016-03-09 0:10 ` Scott Wood
2016-03-09 0:27 ` luigi burdo
2016-03-09 0:37 ` Scott Wood
2016-03-10 10:22 ` luigi burdo
2016-03-15 22:37 ` Scott Wood
2016-03-16 6:24 ` luigi burdo
2016-03-17 3:47 ` Scott Wood [this message]
2016-03-17 6:07 ` luigi burdo
2016-03-17 13:38 ` luigi burdo
2016-03-17 16:23 ` Scott Wood
2016-03-17 18:25 ` luigi burdo
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=1458186445.19333.3.camel@buserror.net \
--to=oss@buserror.net \
--cc=chzigotzky@xenosoft.de \
--cc=contact@a-eon.com \
--cc=intermediadc@hotmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew@a-eon.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).