qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Developing new user-level target?
Date: Sat, 10 Jul 2004 17:57:00 +0200	[thread overview]
Message-ID: <40F011CC.6080909@bellard.org> (raw)
In-Reply-To: <BAY8-F114YEcSvtxgBc0000e0d6@hotmail.com>

Hi,

User level emulation in QEMU only supports Linux as host _and_ guest. 
Supporting a different Unix would be very difficult except for simple 
console programs.

If the hardware is simple enough, it would be better to go for full 
system emulation right from the beginning.

Fabrice.

Patrick Mackinlay wrote:
> In searching across the net, I've managed to stumble across QEMU, which 
> may be the best starting point for a project I have in mind. I'd like 
> some feedback on the difficulty of doing what I propose, or if there are 
> any more appropriate systems that people are aware of that may better 
> satisfy my requirements.
> 
> Essentially, I have an interest in some older (mid to late 80's) UNIX 
> computer systems. The one I'm particularly interested in used the 
> CLIPPER processor (one of the first fully commercialised RISC CPUs) and 
> a version of SVR3 named CLIX.
> 
> I'm interested in adding support for this system to QEMU. In the first 
> instance, I'd like to get a user-level target working. Without having 
> looked at any of the source yet, can someone comment on the difficulty 
> of adding support for a new CPU? Following that, my next biggest concern 
> is supporting not only the COFF executable format (does QEMU support 
> only ELF at the moment?), but the translation from the native to Linux 
> system calls.
> 
> As a final complexity, I'd like to (eventually) host all this on Windows 
> - either natively under Win32, or more probably under the Interix 
> subsystem included in Microsoft's Services For Unix (SFU). Again, the 
> question arises regarding the system call translation component - how 
> much work is involved in adapting this to suit a different (although 
> still UNIX) target and a non-Linux host?
> 
> BTW, before anyone asks, I'm specifically interested in the user-level 
> target right now. Producing a full system level emulation is 
> interesting, but I have almost no documentation of the other system 
> hardware and I think it's going to be quite an exercise in 
> reverse-engineering to figure out enough to write emulation code.
> 
> Regards,
> Pat Mackinlay.
> 
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

  reply	other threads:[~2004-07-10 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-10 15:44 [Qemu-devel] Developing new user-level target? Patrick Mackinlay
2004-07-10 15:57 ` Fabrice Bellard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-11  4:55 Patrick Mackinlay

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=40F011CC.6080909@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).