qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: linux user problems
Date: Tue, 18 Sep 2007 00:25:33 +0200	[thread overview]
Message-ID: <1190067933.14938.209.camel@rapid> (raw)
In-Reply-To: <200709172310.04652.paul@codesourcery.com>

On Mon, 2007-09-17 at 23:10 +0100, Paul Brook wrote:
> On Monday 17 September 2007, J. Mayer wrote:
> > It seems to me that there are many problems in linux-user/syscall.c
> > - problems for 64 bits targets:
> > it seems that do_syscall and child functions should take target_long /
> > target_ulong arguments instead of long / unsigned long. This would make
> > a chance for 64 bits targets to be ran on 32 bits hosts (even if, yes,
> > there would also be other problems to fix elsewhere...).
> 
> IIRC most of code predates target_long. I'm surprised 64-bit targets work at 
> all.

Well, in fact I already did this (mostly alpha emulation). But running
on a 64 bits host platform, which may explain I've been able to start
running anything !...
I'd like to make this more reliable in order to test some PowerPC 64
code without the need of the full MMU emulation (which is not complete
and far from being debugged...) and any firmware.

> > there should be a target_short definition: are we sure short on the host
> > is always the same size than target_short ?
> 
> Short is the same 16-bit type on every host or target we're even vaguely 
> likely to care about.
> 
> I can only think of one system (a weird and fairly obscure DSP) where this is 
> not true. You'd definitely not be running linux, and almost certainly not be 
> running qemu on it.

OK, so there's no issue with this. But there always seem to be an issue
confusing short with long or target_long...

I go on checking the syscall.c code, converting long to target_long when
it seems correct and preparing remarks and/or questions for all other
cases.

Regards.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

      reply	other threads:[~2007-09-17 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 21:04 [Qemu-devel] RFC: linux user problems J. Mayer
2007-09-17 22:10 ` Paul Brook
2007-09-17 22:25   ` J. Mayer [this message]

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=1190067933.14938.209.camel@rapid \
    --to=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 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).