qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: thayne@c2.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] linux-user (mostly syscall.c)
Date: Sat, 03 Nov 2007 20:13:54 +0100	[thread overview]
Message-ID: <472CC872.2090405@bellard.org> (raw)
In-Reply-To: <1194099328.2168.61.camel@phantasm.home.enterpriseandprosperity.com>

Thayne Harbaugh wrote:
> On Sat, 2007-11-03 at 13:52 +0100, J. Mayer wrote:
>> On Sat, 2007-11-03 at 01:21 +0000, Thiemo Seufer wrote:
>> [...]
>>  But it could be great to group the syscalls by
>> categories, or so. For example, putting all POSIX compliant syscalls in
>> a single file and using a syscall table could make quite easy to develop
>> a BSD-user target (I did this in the past, not in Qemu though...). POSIX
>> compliant interfaces can mostly be shared with Linux ones and a lot of
>> other syscalls are common to the 3 BSD flavors (Net, Open and Free..).
>> Being able to add a BSD target sharing the same code would be a proof
>> the code is flexible and well organized; I guess large parts of the
>> Darwin user target could also be merged with a FreeBSD user target...
> 
> That's a reasonable strategy as well.  I've looked through some of the
> darwin code and have considered how common code could be merged.

I am strongly against such merges.

Different OS emulation must be handled in different directories (and
maybe even in different projects) as they are likely to have subtle
differences which makes impossible to test a modification made for one
OS without testing all the other OSes.

Regards,

Fabrice.

  reply	other threads:[~2007-11-03 19:14 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 [this message]
2007-11-04  1:16         ` Thayne Harbaugh
2007-11-04  1:35           ` J. Mayer
2007-11-04  1:51             ` Paul Brook
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=472CC872.2090405@bellard.org \
    --to=fabrice@bellard.org \
    --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).