From: Scott Wood <oss@buserror.net>
To: luigi burdo <intermediadc@hotmail.com>
Cc: Trevor Dickinson <contact@a-eon.com>,
"matthew@a-eon.com" <matthew@a-eon.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: Freescale P5020 cpu will be kvm-pr?
Date: Thu, 17 Mar 2016 11:23:10 -0500 [thread overview]
Message-ID: <1458231790.19333.7.camel@buserror.net> (raw)
In-Reply-To: <DUB117-W90A8E7C5DFE0D4D6781F55C88B0@phx.gbl>
On Thu, 2016-03-17 at 14:38 +0100, luigi burdo wrote:
> Hi Scott,
> this is my Kernel 4.5 dmesg
>
> dmesg | grep -i MMU
> [ 0.000000] MMU: Supported page sizes
> [ 0.000000] MMU: Book3E HW tablewalk not supported
> [ 0.000000] mmu_features = 0x000a0010
> [ 0.000000] MMU: Allocated 2112 bytes of context maps for 255 contexts
>
> dmesg | grep -i e500
> [ 0.001787] e500 family performance monitor hardware support registered
>
>
> dmesg | grep -i hypervisor
>
> [ 0.396726] ePAPR hypervisor byte channel driver
> [ 3.240020] Freescale hypervisor management driver
> [ 3.240024] fsl-hv: no hypervisor found
None of these messages are a problem.
"Book3E HW tablewalk" is for e6500, not e5500. fsl-hv is for the Freescale
Embedded Hypervisor (Topaz), not KVM.
> i attached my kenrel .config
>
> My qemu-ppc-64 crash, note i have the same crash
>
> qemu: fatal: This KVM version does not support PAPR
You need to tell QEMU to use the appropriate CPU type (e5500) and platform
(ppce500). PAPR is for book3s, which is what QEMU defaults to.
-Scott
next prev parent reply other threads:[~2016-03-17 16:23 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
2016-03-17 6:07 ` luigi burdo
2016-03-17 13:38 ` luigi burdo
2016-03-17 16:23 ` Scott Wood [this message]
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=1458231790.19333.7.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).