qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "syeng" <syeng@yango.us>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Perhaps a Virtual CPU for host?
Date: Sat, 17 Jul 2004 20:42:13 -0500	[thread overview]
Message-ID: <001001c46c68$81f01510$2e389c3f@computername> (raw)

I'm a lurker in this list and I'm not a developer, so please excuse me if
this isn't a good idea.

I've been wondering... Since Qemu is a binary translator, would it be
reasonable to have Qemu generate code for a virtual cpu instead of a real
cpu?

Then the program would run the virtual cpu emulator, which runs the code
generated by qemu.

In other words... No more back-ends for PPC, x86, Sparc, etc. etc.  Porting
to a new system would be easier, too.

Now, I know it sounds pretty bad.

BUT, I was thinking that if you chose the right virtual cpu architecture,
you might actually be able to get pretty decent performance out it.  I've
heard of cases where virtual cpu's ran benchmarks pretty well because each
instruction was easily decoded and each instruction did a lot of 'work'
(CISC vs. RISC.  For a virtual cpu, CISC style cpu's are better, I guess.)

I don't know how efficient the code is that Qemu generates, but it certainly
wouldn't be extremely efficient.  Perhaps a carefully chosen virtual cpu
architecture might make up for some of that, and perhaps run as fast as half
the speed of a native Qemu port?

If nothing else, it might provide a generic base for currently unsupported
host systems.

Any comments?

             reply	other threads:[~2004-07-18  1:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18  1:42 syeng [this message]
2004-07-18  1:56 ` [Qemu-devel] Perhaps a Virtual CPU for host? Jim C. Brown

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='001001c46c68$81f01510$2e389c3f@computername' \
    --to=syeng@yango.us \
    --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).