qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, agraf@suse.de
Cc: blauwirbel@gmail.com
Subject: Re: [Qemu-devel] [PATCH, RFC] BSD user emulator
Date: Mon, 01 Sep 2008 10:25:15 -0600 (MDT)	[thread overview]
Message-ID: <20080901.102515.-1975969776.imp@bsdimp.com> (raw)
In-Reply-To: <3ACB420B-8C07-4417-80F5-1B74896D1533@suse.de>

In message: <3ACB420B-8C07-4417-80F5-1B74896D1533@suse.de>
            Alexander Graf <agraf@suse.de> writes:
: 
: On Aug 30, 2008, at 10:31 AM, Blue Swirl wrote:
: 
: > Hi,
: >
: > This version can actually execute some programs, for example:
: >
: > ./sparc64-bsd-user/qemu-sparc64 -d in_asm /bin/cat /etc/motd
: > OpenBSD 4.4 (GENERIC) #1715: Mon Aug 11 17:55:10 MDT 2008
: >
: > Welcome to OpenBSD: The proactively secure Unix-like operating system.
: >
: > Please use the sendbug(1) utility to report bugs in the system.
: > Before reporting a bug, please try to reproduce it with the latest
: > version of the code.  With bug reports, please try to ensure that
: > enough information to reproduce the problem is enclosed, and if a
: > known fix for it exists, include that as well.
: >
: > Something is not correct with errno handling, it could also be a bug
: > in CPU emulation:
: > /sparc64-bsd-user/qemu-sparc64 -d in_asm /bin/cat /foobar
: > cat: /foobar: Undefined error: 0
: >
: > Some other programs just fail:
: > ./sparc64-bsd-user/qemu-sparc64 -d in_asm /bin/ls
: > ls: Cannot allocate memory
: > ./sparc64-bsd-user/qemu-sparc64 -d in_asm /bin/ksh
: > ksh in malloc(): error: chunk overflow
: > ./sparc64-bsd-user/qemu-sparc64 -d in_asm /usr/bin/id
: > Segmentation fault
: > ./sparc64-bsd-user/qemu-sparc64 -d in_asm /sbin/ifconfig
: > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 0¸
: > ifconfig: getifgroups: Cannot allocate memory
: >
: > I've cleaned up the patch a bit. Signals, ioctls and structure
: > conversions are still unimplemented and as usual, no docs.
: >
: > I think this is getting ready to be committed pretty soon. Any
: > comments, objections?
: 
: Just off the top of my head: Shouldn't BSD userspace and Darwin  
: userspace emulation be able to share a good bunch of syscalls?
: IIRC the positive Darwin syscalls should be some recent FreeBSD  
: syscalls that should look pretty similar to OpenBSD syscalls. I might  
: be totally wrong here though ;-).

Kinda.

The system calls are mostly similar between the BSDs, but do vary for
syscalls added since 4.4BSD Lite-2.

Warner

  parent reply	other threads:[~2008-09-01 16:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30  8:31 [Qemu-devel] [PATCH, RFC] BSD user emulator 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-08-25 18:45 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

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=20080901.102515.-1975969776.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=agraf@suse.de \
    --cc=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).