From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "J. Mayer" <l_indien@magic.fr>, thayne@c2.net
Subject: Re: [Qemu-devel] [RFC] linux-user (mostly syscall.c)
Date: Sun, 4 Nov 2007 01:51:08 +0000 [thread overview]
Message-ID: <200711040151.09983.paul@codesourcery.com> (raw)
In-Reply-To: <1194140125.16781.580.camel@rapid>
> If you take a close look, you'll find more variations between Linux ABIs
> for different CPUs than between all BSD implementations: common syscalls
> of all BSD flavors do the same thing (and have the same ABI whatever the
> CPU...). You'll also find very few variations between the syscalls
> common to BSD & Linux because most of those directly map POSIX defined
> functions.
> Then, following the given argument, we never should try to share any
> code between linux-user for different targets, as the Linux ABI and
> behavior is different for different CPUs...
I'd guess that the ones that are all the same are the ones that don't take any
real effort to implement in the first place.
If you can combine the implementations I'd also expect to be able to do cross
emulation. e.g. run *BSD applications on a Linux host. This definitely works
for simple cases, even in the extreme case of a windows host - as you say
many syscalls map directly onto POSIX functions so there is only ever one
implementation. Whether it works well enough for real applications or whole
distributions of software I'm not so sure. If you can't do cross emulation
I'm sceptical about how much they can be combined.
Paul
next prev parent reply other threads:[~2007-11-04 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 0:05 [Qemu-devel] [RFC] linux-user (mostly syscall.c) Thayne Harbaugh
2007-11-03 1:21 ` Thiemo Seufer
2007-11-03 12:52 ` J. Mayer
2007-11-03 14:15 ` Thayne Harbaugh
2007-11-03 19:13 ` Fabrice Bellard
2007-11-04 1:16 ` Thayne Harbaugh
2007-11-04 1:35 ` J. Mayer
2007-11-04 1:51 ` Paul Brook [this message]
2007-11-04 7:49 ` J. Mayer
2007-11-03 17:24 ` TJ
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=200711040151.09983.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=l_indien@magic.fr \
--cc=qemu-devel@nongnu.org \
--cc=thayne@c2.net \
/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).