From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Mac OS X and QEMU "roadmap"
Date: Tue, 07 Oct 2003 00:27:01 +0200 [thread overview]
Message-ID: <3F81EC35.8040808@free.fr> (raw)
In-Reply-To: <62042.67.168.46.137.1065438296.squirrel@mail.apvio.net>
qemu@raylucke.com wrote:
> I have been lurking around this mailing list (via the online web view) and
> decided to post here. I have decided to attempt to try to make Qemu at
> least compile on the Darwin kernel.
>
> So far I have a few files successfully compiling, but I am still a LONG
> way from being there. Of course, the dyngen app is intended to read ELF
> binaries, and I have almost no understanding of Mach-O binaries at all.
>
> People can check the status of this little (potentially futile) project,
> as well as download a tarball of what I have so far at:
> http://www.raylucke.com/20010926/software/qemu/
OK. I will try to look at that after the next release. On my TODO list I
have 3 (or 4) items left:
- Finish full soft MMU mode (almost there, it allows to launch unpatched
guest OSes and it eases QEMU portability on non Linux host OSes).
- (maybe, because it is more complicated) add a physical TB cache, so
that QEMU does not flush translated code when the guest OS switches tasks.
- add builtin user mode tests for ARM and SPARC targets (I need to
compile tests/linuxtest.c for those archs).
- add test "reference" images for Linux, NetBSD and FreeDOS (if someone
wants to help on that topic...).
Fabrice.
next prev parent reply other threads:[~2003-10-06 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 11:04 [Qemu-devel] I am attempting to port Qemu to Mac OS X qemu
2003-10-06 22:27 ` Fabrice Bellard [this message]
2003-10-07 7:22 ` [Qemu-devel] Mac OS X and QEMU "roadmap" Benjamin Herrenschmidt
2003-10-07 10:16 ` Rusty Russell
2003-10-14 21:24 ` Fabrice Bellard
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=3F81EC35.8040808@free.fr \
--to=fabrice.bellard@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.