From: Hollis Blanchard <hollisb@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
jyoung5@us.ibm.com, qemu-devel@nongnu.org,
Jocelyn Mayer <l_indien@magic.fr>
Subject: Re: [kvm-ppc-devel] [Qemu-devel] TCG code in qemu has broken
Date: Thu, 21 Feb 2008 22:11:37 +0000 [thread overview]
Message-ID: <1203631897.21867.1.camel@basalt> (raw)
In-Reply-To: <200802212027.18977.paul@codesourcery.com>
On Thu, 2008-02-21 at 20:27 +0000, Paul Brook wrote:
> On Thursday 21 February 2008, Jerone Young wrote:
> > The recent TCG code to replace dyngen code in qemu cvs has broken
> > PowerPC host support (or from what is appears...anyone else who is not
> > x86 or x86-64). Is anyone working to fix this ? Is there a plan to fix
> > all the other hosts?
>
> As far as plans go, I expect they'll get fixed when someone implements them.
> Someone posed (incomplete) sparc host support fairly recently.
>
> Your best bet is probably just to follow this list, and post here when you
> start working on a particular target.
I'm not really familiar with the qemu development process; is this
usually how it works? People are free to break things and assume others
will fix it?
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
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-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
WARNING: multiple messages have this Message-ID (diff)
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
jyoung5@us.ibm.com, qemu-devel@nongnu.org,
Jocelyn Mayer <l_indien@magic.fr>
Subject: Re: [kvm-ppc-devel] [Qemu-devel] TCG code in qemu has broken PPC host support .... anyone working on this?
Date: Thu, 21 Feb 2008 16:11:37 -0600 [thread overview]
Message-ID: <1203631897.21867.1.camel@basalt> (raw)
In-Reply-To: <200802212027.18977.paul@codesourcery.com>
On Thu, 2008-02-21 at 20:27 +0000, Paul Brook wrote:
> On Thursday 21 February 2008, Jerone Young wrote:
> > The recent TCG code to replace dyngen code in qemu cvs has broken
> > PowerPC host support (or from what is appears...anyone else who is not
> > x86 or x86-64). Is anyone working to fix this ? Is there a plan to fix
> > all the other hosts?
>
> As far as plans go, I expect they'll get fixed when someone implements them.
> Someone posed (incomplete) sparc host support fairly recently.
>
> Your best bet is probably just to follow this list, and post here when you
> start working on a particular target.
I'm not really familiar with the qemu development process; is this
usually how it works? People are free to break things and assume others
will fix it?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-02-21 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 19:43 [kvm-ppc-devel] TCG code in qemu has broken PPC host support Jerone Young
2008-02-21 19:43 ` [Qemu-devel] TCG code in qemu has broken PPC host support .... anyone working on this? Jerone Young
2008-02-21 20:27 ` [kvm-ppc-devel] [Qemu-devel] TCG code in qemu has broken PPC Paul Brook
2008-02-21 20:27 ` [Qemu-devel] TCG code in qemu has broken PPC host support .... anyone working on this? Paul Brook
2008-02-21 22:11 ` Hollis Blanchard [this message]
2008-02-21 22:11 ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-21 22:23 ` [kvm-ppc-devel] [Qemu-devel] TCG code in qemu has broken PPC Paul Brook
2008-02-21 22:23 ` [kvm-ppc-devel] [Qemu-devel] TCG code in qemu has broken PPC host support .... anyone working on this? Paul Brook
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=1203631897.21867.1.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=l_indien@magic.fr \
--cc=paul@codesourcery.com \
--cc=qemu-devel@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.