From: Jerone Young <jyoung5@us.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
hollisb <hollisb@linux.vnet.ibm.com>,
Avi Kivity <avi@qumranet.com>
Subject: Re: [RFC] Qemu powerpc work around
Date: Wed, 13 Feb 2008 14:29:26 -0600 [thread overview]
Message-ID: <1202934566.13883.1.camel@thinkpad.austin.ibm.com> (raw)
In-Reply-To: <47B33D20.7030709@codemonkey.ws>
This works better. Not sure why but when I had fake-exec in target-ppc,
the build system was complaining that it could not find fake-exec.d. So
then I just decided to move it to fake-exec-ppc.c.
This patch works fine for powerpc.
On Wed, 2008-02-13 at 12:55 -0600, Anthony Liguori wrote:
> Jerone Young wrote:
> > On Wed, 2008-02-13 at 09:29 +0200, Avi Kivity wrote:
> >
> >> Jerone Young wrote:
> >>
> >>> So the recent code in qemu cvs has problem powerpc. So what I have done
> >>> is mainly work around this in the build system, by creating
> >>> ppcemb_kvm-sofmmu target. Along with this is a fake-exec.c that stubs
> >>> out the functions that are no longer defined (something done by Anthony
> >>> Liguori attempting to fix qemu_cvs). What do folks think about this
> >>> approach, for us all we really need is a qemu that is not built with tcg
> >>> dependency.
> >>>
> >>>
> >>>
> >> Since a target in qemu is a cpu type, how the instructions are executed
> >> (kvm, kqemu, dyngen, or tcg) shouldn't come into it. Instead we can
> >> have a --without-cpu-emulation or --no-tcg which would simply disable
> >> those parts.
> >>
> >
> > Actually this much much more sensible solution. So I took some time and
> > implemented it.
> >
>
> Funny enough, I was thinking the same thing last night :-)
>
> Please move fake-exec.c to target-ppc/fake-exec.c as it contains PPC
> specific code. Otherwise, this patch is much better!
>
> Regards,
>
> Anthony Liguori
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-13 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 21:37 [RFC] Qemu powerpc work around Jerone Young
2008-02-12 21:44 ` Anthony Liguori
2008-02-12 21:53 ` Jerone Young
2008-02-12 22:03 ` Anthony Liguori
2008-02-12 22:50 ` Jerone Young
2008-02-13 0:47 ` Anthony Liguori
2008-02-13 7:29 ` Avi Kivity
2008-02-13 17:39 ` Jerone Young
2008-02-13 18:55 ` Anthony Liguori
2008-02-13 19:27 ` [PATCH] " Jerone Young
2008-02-13 20:20 ` Anthony Liguori
2008-02-13 20:29 ` Jerone Young [this message]
2008-02-14 9:33 ` [RFC] " Avi Kivity
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=1202934566.13883.1.camel@thinkpad.austin.ibm.com \
--to=jyoung5@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=hollisb@linux.vnet.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
/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