qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4932] Preliminary PPC64/Linux host support
Date: Thu, 24 Jul 2008 21:41:20 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807242138150.4577@linmac.oyster.ru> (raw)
In-Reply-To: <48881ACB.9080007@exactcode.de>

On Thu, 24 Jul 2008, Ren Rebe wrote:

> Hi,
>
> malc wrote:
>> Revision: 4932
>>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4932
>> Author:   malc
>> Date:     2008-07-23 19:17:46 +0000 (Wed, 23 Jul 2008)
>> 
>> Log Message:
>> -----------
>> Preliminary PPC64/Linux host support
>> 
>> ppc64.ld from Heikki Lindholm's patch
>> http://marc.info/?l=qemu-devel&m=114086179024634&w=2
>> 
>> Issues:
>> x86_64 tripple faults shortly after decompressing the kernel
>> No immediate versions of most 64 bit operations
>> 
> Nice! I already spent some hours fixing a previous ppc64 patch that
> was sent to the list like half a year ago, which was pre TCG and
> did not work with relocations generated by latest toolchains.
>
> I'll definetly give this patch a try ASAP and try to find some time
> slots to help streamlining it.

That would be great. One thing i failed to mention in the commit
message is that linux-user support seems completely broken on ppc64,
i.e. doesn't even compile and error messages are frightening (or
maybe it was the amount of them that scared me)

-- 
mailto:av1474@comtv.ru

  reply	other threads:[~2008-07-24 17:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 19:17 [Qemu-devel] [4932] Preliminary PPC64/Linux host support malc
2008-07-24  6:01 ` René Rebe
2008-07-24 17:41   ` malc [this message]
2008-07-24 18:42     ` Andreas Färber
2008-07-25  8:41     ` René Rebe
2008-07-25 18:15       ` malc
2008-07-26 19:32         ` René Rebe
2008-07-27 18:17           ` malc
     [not found] ` <1964D914-95C1-4A3E-AE40-2DE082D40C24@hotmail.com>
2008-07-24 23:33   ` C.W. Betts
2008-07-25 18:18     ` malc
2008-07-26 13:08       ` Andreas Färber
     [not found]         ` <F41A287D-66CA-42E4-A191-CD5381987301@hotmail.com>
2008-07-26 17:36           ` C.W. Betts
2008-07-26 18:00             ` Andreas Färber
2008-07-26 18:54         ` malc
2008-07-26 20:42           ` Andreas Färber
2008-07-27 18:14             ` malc
2008-07-29 16:28               ` [Qemu-devel] Mac OS X PPC host support (was: [4932] Preliminary PPC64/Linux host support) Andreas Färber
2008-07-29 20:23                 ` malc
2008-07-30 18:45                   ` Blue Swirl
2008-07-31 17:15                     ` malc
2008-07-31 18:57                     ` malc
2008-07-31 21:50                       ` Andreas Färber
2008-08-01 18:52                         ` malc
2008-08-02 21:29                           ` Andreas Färber
2008-08-03 18:56                             ` malc
2008-08-02 16:35                         ` Andreas Färber
     [not found]                           ` <E3E8B39E-1924-465D-AA4A-9250D835C932@hotmail.com>
2008-08-02 19:43                             ` C.W. Betts
2008-07-26 13:39     ` [Qemu-devel] [4932] Preliminary PPC64/Linux host support Andreas Färber
     [not found]       ` <1D9DD99A-96CE-4570-B8EE-428CDBAE5FE3@hotmail.com>
2008-07-26 17:13         ` C.W. Betts

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=Pine.LNX.4.64.0807242138150.4577@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --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 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).