qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: davidm@hpl.hp.com, qemu-devel@nongnu.org
Cc: davidm@napali.hpl.hp.com
Subject: Re: [Qemu-devel] ia64-enablement patch
Date: Fri, 08 Apr 2005 00:22:12 +0200	[thread overview]
Message-ID: <4255B294.7080701@bellard.org> (raw)
In-Reply-To: <200502180825.j1I8P0QD019790@napali.hpl.hp.com>

David Mosberger wrote:
> The patch below makes qemu work on ia64 linux.  Most of the patch is
> straight-forward, but there are perhaps some controversial bits and
> pieces (in particular the linux-user/syscall.c changes need
> consideration).  I'm mostly throwing this out there to get some
> reactions.  If it looks generally OK, I can split it up into separate
> pieces (generic cleanups & bug fixes, syscall-cleanup, ia64-specific
> stuff).
> 
> I haven't done a huge amount of testing.  i386-softmmu/qemu boots the
> minimal linux.img fine and Mandrake/x86 seems to be booting too.
> i386-user/qemu runs basic x86 binaries such as "ls" and "nvi" fine,
> but more complex stuff fails possibly because of lack of futex.  I
> wasn't able to test any other target architectures for lack of images
> (the only non-x86 image I found was for PPC and for some reason
> ppc-softmmu/qemu didn't get built for me.
> 
> Enjoy,
> 
> 	--david

I applied most of your patch, except in linux-user/syscall.c. You should 
make the minimum amount of changes in this file.

Fabrice.

  reply	other threads:[~2005-04-07 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18  8:25 [Qemu-devel] ia64-enablement patch David Mosberger
2005-04-07 22:22 ` Fabrice Bellard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-18  8:47 David Mosberger

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=4255B294.7080701@bellard.org \
    --to=fabrice@bellard.org \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.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 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).