qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Prince Riley" <wmarketing3@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU Roadmap for 2009 -- Status
Date: Mon, 15 Dec 2008 12:18:17 -0600	[thread overview]
Message-ID: <fa04eb750812151018u54c8e8cfyc561b8b813eee76c@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

Greetings <http://bellard.org/qemu/qemu-tech.html#TOC3>I am writing to ask
if anyone can respond to this post with a summary of the current efforts
underway to work on the points mentioned in the lst below for the x86 and
ARM processor platforms.
Is there a development/release roadmap for adding these features ? I am
interested in the work toward adding support for the ARM9 processor.

Thanks

Prince Riley

1.2 x86 emulation <http://bellard.org/qemu/qemu-tech.html#TOC3>

Current QEMU limitations:

   - No SSE/MMX support (yet).
   - No x86-64 support.
   - IPC syscalls are missing.
   - The x86 segment limits and access rights are not tested at every memory
   access (yet). Hopefully, very few OSes seem to rely on that for normal use.
   - On non x86 host CPUs, doubles are used instead of the non standard 10
   byte long doubles of x86 for floating point emulation to get maximum
   performances.

1.3 ARM emulation <http://bellard.org/qemu/qemu-tech.html#TOC4>

   - Full ARM 7 user emulation.
   - NWFPE FPU support included in user Linux emulation.
   - Can run most ARM Linux binaries.

[-- Attachment #2: Type: text/html, Size: 1411 bytes --]

             reply	other threads:[~2008-12-15 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 18:18 Prince Riley [this message]
2008-12-15 18:47 ` [Qemu-devel] QEMU Roadmap for 2009 -- Status Andreas Färber
2008-12-15 19:25 ` Kirill A. Shutemov
2008-12-19 23:44 ` Miklos Vajna
2008-12-20  0:21   ` Martin Mohring

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=fa04eb750812151018u54c8e8cfyc561b8b813eee76c@mail.gmail.com \
    --to=wmarketing3@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).