From: Scott Wood <oss@buserror.net>
To: luigi burdo <intermediadc@hotmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "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: Tue, 08 Mar 2016 18:37:44 -0600 [thread overview]
Message-ID: <1457483864.5360.128.camel@buserror.net> (raw)
In-Reply-To: <DUB117-W1369999A718E6C0B33E4DC8C8B30@phx.gbl>
On Wed, 2016-03-09 at 01:27 +0100, luigi burdo wrote:
> Hi Scott, thanks for the reply,
> about: I don't know what you mean by "working only on emb side".
> thru qemu 2.5 i can use only ppcemb as kvm not ppc64 or ppc
Oh, you mean the QEMU target... "ppc64" should work.
> Dont have the Kvm-pr is a really unhappy news, it means we will not have the
> opportunity to run
> for example Mol-kvm on this machine.
Right. KVM on book3e does not allow making the CPU look like a different type
of PPC. It just lets you create virtual instances of the same CPU.
> about:KVM for e5500 uses hardware hypervisor features
> look like hypervisor is disabled because the main Hardware is too young and
> need a better knowledge.
Not sure what you mean here.
-Scott
next prev parent reply other threads:[~2016-03-09 0:37 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 [this message]
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
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=1457483864.5360.128.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).