From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] BSD user emulator
Date: Thu, 28 Aug 2008 18:49:28 +0300 [thread overview]
Message-ID: <f43fc5580808280849p43a64d62nda4e0e586a389a28@mail.gmail.com> (raw)
In-Reply-To: <72152057-E96E-4331-8483-062D241ED8DD@web.de>
On 8/27/08, Andreas Färber <andreas.faerber@web.de> wrote:
> Hi,
>
> Am 25.08.2008 um 20:45 schrieb Blue Swirl:
>
>
> > This is a preliminary implementation of BSD user emulator. Some files
> > inside bsd-user contain a lot of unwanted cruft copied from linux-user
> > and ldscript is not used. But it can already run a handcrafted Sparc64
> > helloworld file (on OpenBSD/Sparc64 host)
> >
> [...]
>
> > I think in BSD (at least OpenBSD), system call numbers, system call
> > parameters, ioctls, and signal numbers are shared across
> > architectures, maybe even between *BSDs. If it's true, it should make
> > the emulator much simpler than Linux one.
> >
>
> Recently I had investigated the idea of a Haiku user emulator. Looking at
> your patch, I see a lot of similarities with what I saw in the linux-user
> dir, but your patch is not an svn diff and marks all files as fully new
> against /dev/null, so it's hard to spot the actual differences to
> linux-user...
>
> In light of getting more userland emulations, do you see possibilities to
> move shared stuff to a new "user" dir rather than copying them to each
> *-user dir? The ELF loading for instance?
I don't think so, Fabrice was strongly against such merges:
http://article.gmane.org/gmane.comp.emulators.qemu/20864
next prev parent reply other threads:[~2008-08-28 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 18:45 [Qemu-devel] [PATCH, RFC] BSD user emulator Blue Swirl
2008-08-25 19:03 ` M. Warner Losh
2008-08-27 19:38 ` Andreas Färber
2008-08-28 15:49 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-30 8:31 Blue Swirl
2008-09-01 8:58 ` Alexander Graf
2008-09-01 9:19 ` Andreas Färber
2008-09-01 16:25 ` M. Warner Losh
2008-09-01 16:44 ` Alexander Graf
2008-09-01 17:55 ` M. Warner Losh
2008-09-01 18:21 ` Blue Swirl
2008-09-01 19:13 ` M. Warner Losh
2008-09-02 17:13 ` Blue Swirl
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=f43fc5580808280849p43a64d62nda4e0e586a389a28@mail.gmail.com \
--to=blauwirbel@gmail.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).