From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2.1] PPC: KVM: Fix g3beige and mac99 when HV is loaded
Date: Thu, 24 Jul 2014 16:11:18 +0200 [thread overview]
Message-ID: <53D11406.1020008@redhat.com> (raw)
In-Reply-To: <53D11009.4040704@suse.de>
Il 24/07/2014 15:54, Alexander Graf ha scritto:
>>>
>> Why should anything except pseries ever use HV KVM?
>
> Because there are no other Book3S machines :). And for BookE we don't
> implement kvm_type != 0 because we only support either PR or HV
> depending on the host platform.
Yeah, what I meant was (in a rather Socratic way): why should the
default for kvm_type == NULL be anything but PR?
All 2.2 stuff, of course.
Paolo
next prev parent reply other threads:[~2014-07-24 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 8:52 [Qemu-devel] [PATCH 2.1] PPC: KVM: Fix g3beige and mac99 when HV is loaded Alexander Graf
2014-07-24 13:44 ` Paolo Bonzini
2014-07-24 13:54 ` Alexander Graf
2014-07-24 14:11 ` Paolo Bonzini [this message]
2014-07-24 14:13 ` Alexander Graf
2014-07-24 14:55 ` Paolo Bonzini
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=53D11406.1020008@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).