From: Avi Kivity <avi@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, blauwirbel@gmail.com,
agraf@suse.de, David Gibson <david@gibson.dropbear.id.au>,
"Marcelo Tosatti (supporter:Overall)" <mtosatti@redhat.com>,
open@suse.de, "list@suse.de:Overall" <kvm@vger.kernel.org>
Subject: Re: [PATCH 08/20] target-ppc: Add hooks for handling tcg and kvm limitations
Date: Mon, 16 Apr 2012 15:31:43 +0300 [thread overview]
Message-ID: <4F8C112F.1070502@redhat.com> (raw)
In-Reply-To: <4F8BF242.2080807@suse.de>
On 04/16/2012 01:19 PM, Andreas Färber wrote:
> Am 16.04.2012 12:13, schrieb Avi Kivity:
> > On 04/15/2012 09:38 PM, Andreas Färber wrote:
> >> From: David Gibson <david@gibson.dropbear.id.au>
> >>
> >> On target-ppc, our table of CPU types and features encodes the features as
> >> found on the hardware, regardless of whether these features are actually
> >> usable under TCG or KVM. We already have cases where the information from
> >> the cpu table must be fixed up to account for limitations in the emulation
> >> method we're using. e.g. TCG does not support the DFP and VSX instructions
> >> and KVM needs different numbering of the CPUs in order to tell it the
> >> correct thread to core mappings.
> >>
> >> This patch cleans up these hacks to handle emulation limitations by
> >> consolidating them into a pair of functions specifically for the purpose.
> >>
> >> env->check_pow = def->check_pow;
> >> +
> >> + if (kvm_enabled()) {
> >> + if (kvmppc_fixup_cpu(env) != 0) {
> >> + fprintf(stderr, "Unable to virtualize selected CPU with KVM\n");
> >> + exit(1);
> >> + }
> >> + } else {
> >> + if (ppc_fixup_cpu(env) != 0) {
> >> + fprintf(stderr, "Unable to emulate selected CPU with TCG\n");
> >> + exit(1);
> >> + }
> >> + }
> >> +
> >>
> >
> > I wish we had an error like that for x86. Right now we silently add and
> > drop cpu features.
>
> x86 has an ,+enforce option for that, doesn't it?
>
So it does. And one day it will be the default.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-04-16 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334515144-26485-1-git-send-email-afaerber@suse.de>
2012-04-15 18:38 ` [PATCH 08/20] target-ppc: Add hooks for handling tcg and kvm limitations Andreas Färber
2012-04-16 10:13 ` Avi Kivity
2012-04-16 10:19 ` Andreas Färber
2012-04-16 12:31 ` Avi Kivity [this message]
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=4F8C112F.1070502@redhat.com \
--to=avi@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=open@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.