qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jocelyn Mayer <jma@netgem.com>
To: qemu mailing list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM
Date: 09 Jul 2003 21:53:53 +0200	[thread overview]
Message-ID: <1057780432.10296.72.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <20030709183518.GA24671@nevyn.them.org>

On Wed, 2003-07-09 at 20:35, Daniel Jacobowitz wrote:
> I was just playing with the ARM support, it's great to see it taking
> shape :)  Fabrice, are you still investigating it, or does it work for
> you?  My local ARM setup crashes a few hundred instructions into ld.so;
> a loop runs for too long and hits the top of the stack.

Hello,

Maybe a flag problem..
As I was looking the overflow flag calculation, while trying to fix it
in my PPC emulation, I noticed that this flag should be masked with (1
<< 31) to be correct.
Fabrice, could you confirm this point ?
It seems to work well in my PPC code...

It may also comes from the fact that the qemu Elf loader builds a
"buggy" stack. I don't known anything about the ABI for the ARM, but I
noticed that the stack wasn't aligned properly on PPC and that some
informations were missing, but I don't really know if those infos are
vital or not. 
Even in x86 emulation, the stack is really different from the one built
by the Linux kernel (I compared with a linux-2.4.21 kernel).
I fixed some crashes, changing this code to do the same as the kernel,
but dynamic x86 loading is now buggy with that patch...

Regards.

-- 
Jocelyn Mayer <jma@netgem.com>

  parent reply	other threads:[~2003-07-09 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 18:35 [Qemu-devel] ARM Daniel Jacobowitz
2003-07-09 19:49 ` Fabrice Bellard
2003-07-10 16:17   ` Daniel Jacobowitz
2003-07-10 20:10     ` Fabrice Bellard
2003-07-10 23:24       ` Daniel Jacobowitz
2003-07-10 16:45   ` Laurent Desnogues
2003-07-10 23:17     ` Daniel Jacobowitz
2003-07-09 19:53 ` Jocelyn Mayer [this message]
2003-07-10  8:44   ` Fabrice Bellard

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=1057780432.10296.72.camel@jma1.dev.netgem.com \
    --to=jma@netgem.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).