From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Cc: "Greg Kurz" <groug@kaod.org>, "Thomas Huth" <thuth@redhat.com>,
sursingh@redhat.com, joserz@linux.vnet.ibm.com,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Cédric Le Goater" <clg@kaod.org>,
sbobroff@redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1
Date: Fri, 30 Jun 2017 10:52:44 +0200 [thread overview]
Message-ID: <c783b94e-e656-da3d-3372-5350cf80915e@redhat.com> (raw)
In-Reply-To: <20170630071218.GE13989@umbus.fritz.box>
On 30/06/2017 09:12, David Gibson wrote:
> On Thu, Jun 29, 2017 at 03:42:03PM +1000, Suraj Jitindar Singh wrote:
>> On Thu, 2017-06-29 at 15:37 +1000, Suraj Jitindar Singh wrote:
>>> On Wed, 2017-06-28 at 18:41 +0200, Greg Kurz wrote:
...
>>> That makes the assumption that DD2 doesn't require any work arounds
>>> which TCG can't handle.
>>
>> Actually TCG is really a non-issue since we'll just go into the POWER9
>> architected mode.
>>
>> Can't we just have -cpu POWER9 alias to DD1 for now and add DD2 when we
>> know the pvr?
>
> No, because calling what qemu does DD1 is simply not accurate, in
> important and guest-visible ways.
>
> What we should do is add in DD2.0 - we know the PVR, even if the
> chip's not out yet. Then alias POWER9 to that.
>
OK, I have patch that define v1.0 to DD1, v2 to DD2, and set the POWER9
alias to v2, but:
- on a DD1 host and KVM HV, "-cpu host" works well and "cpu POWER9"
(that select then the v1.0) boots the kernel and hangs at early boot of
the kernel (first display)
- in TCG mode, boot by default with v2, but some services does not start
correctly, and I have never the console login (perhaps because of some
time out: I test TCG on the POWER9 host, I should test on a x86 one).
I'm trying for the moment to understand why "-cpu POWER9" hangs while
"-cpu host" works.
Thanks,
Laurent
next prev parent reply other threads:[~2017-06-30 8:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 11:26 [Qemu-devel] [PATCH] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1 Laurent Vivier
2017-06-22 11:31 ` Thomas Huth
2017-06-23 9:21 ` David Gibson
2017-06-23 14:10 ` Laurent Vivier
2017-06-28 1:42 ` [Qemu-devel] [Qemu-ppc] " joserz
2017-06-28 7:09 ` Thomas Huth
2017-06-28 8:18 ` David Gibson
2017-06-28 9:11 ` Cédric Le Goater
2017-06-28 9:18 ` Laurent Vivier
2017-06-28 10:23 ` Cédric Le Goater
2017-06-28 11:59 ` Greg Kurz
2017-06-28 16:18 ` Laurent Vivier
2017-06-28 16:41 ` Greg Kurz
2017-06-29 5:37 ` Suraj Jitindar Singh
2017-06-29 5:42 ` Suraj Jitindar Singh
2017-06-30 7:12 ` David Gibson
2017-06-30 8:52 ` Laurent Vivier [this message]
2017-06-29 6:44 ` Thomas Huth
2017-06-29 15:05 ` Eric Blake
2017-06-30 7:14 ` David Gibson
2017-06-30 7:56 ` Cédric Le Goater
2017-06-30 10:36 ` Michael Ellerman
2017-06-28 10:59 ` Laurent Vivier
2017-06-23 16:05 ` [Qemu-devel] " Thomas Huth
2017-06-28 0:58 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
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=c783b94e-e656-da3d-3372-5350cf80915e@redhat.com \
--to=lvivier@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=joserz@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbobroff@redhat.com \
--cc=sjitindarsingh@gmail.com \
--cc=sursingh@redhat.com \
--cc=thuth@redhat.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).