From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stuff.
Date: Wed, 05 May 2004 20:28:07 +0200 [thread overview]
Message-ID: <40993237.7050300@bellard.org> (raw)
In-Reply-To: <1083706269.26125.1150.camel@imladris.demon.co.uk>
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 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? Especially if we can extend that
> to emulate libX11 too :)
Emulating libc would be _very_ difficult (there are thousands of calls
to convert). There were provisions in em86 to do that, but it was never
really used. Moreover, I think the speed up would be small compared to
the complexity of the task.
> It's cute that I have i386 acroread running in a Mozilla window through
> mozplugger. It'd be cuter if I could get Mozilla plugins running in the
> _same_ process, rather than in a separate process.
>
>
> ----
>
> Also, why do we do what we do in linux-user/path.c? What does it give us
> that couldn't be achieved by stat("$prefix/$filename") in a trivial
> path() function? Other than taking for ever to start up when
> /usr/gnemul/i386-linux is actually an nfs-mounted root file system from
> elsewhere. (When I say forever I mean that literally. We keep following
> symlinks recursively).
The goal was to avoid making too many syscalls.
Fabrice.
next prev parent reply other threads:[~2004-05-05 18:26 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 [this message]
2004-05-05 18:55 ` Fabrice Bellard
2004-05-07 11:33 ` Chris Emerson
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=40993237.7050300@bellard.org \
--to=fabrice@bellard.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).