qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Emerson <qemu@mail.nosreme.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stuff.
Date: Fri, 7 May 2004 12:33:42 +0100	[thread overview]
Message-ID: <20040507113341.GA28776@ixion.tartarus.org> (raw)
In-Reply-To: <1083706269.26125.1150.camel@imladris.demon.co.uk>

On Tue, May 04, 2004 at 10:31:09PM +0100, David Woodhouse wrote:
> Has anyone considered the possibility of emulating libc, rather than
> emulating system calls? That's what em86 used to do for emulating i386
> code on Alpha -- rather than letting it run a 'real' non-native libc
> and then emulating only syscalls. 

I did this with my own i386-on-ppc emulator.  It's a larger and less
well documented ABI, and can get quite messy.  OTOH, most of the
functions are easy and could be generated.

> I appreciate that syscalls are a far more stable ABI to be emulating,
> and there are far fewer structures to convert -- but wouldn't it be
> faster to emulate the library itself?

Probably, but I'd be interested to see some profiling data showing how
much time is actually spent emulating the libc etc. first.

> It's cute that I have i386 acroread running in a Mozilla window
> through mozplugger.

Ooh, I'll have to look into that.  Maybe I can have Flash on Linux/PPC
after all...

> It'd be cuter if I could get Mozilla plugins running in the _same_
> process, rather than in a separate process. 

You'd need to know the prototypes of all the functions you're calling
ahead of time, though...

Chris

      parent reply	other threads:[~2004-05-07 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 21:31 [Qemu-devel] Stuff David Woodhouse
2004-05-05 12:15 ` Timo Savola
2004-05-05 18:28 ` Fabrice Bellard
2004-05-05 18:55 ` Fabrice Bellard
2004-05-07 11:33 ` Chris Emerson [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=20040507113341.GA28776@ixion.tartarus.org \
    --to=qemu@mail.nosreme.org \
    --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).