From: Johan Rydberg <jrydberg@night.trouble.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] simulated memory instead of host memory
Date: Mon, 9 Jun 2003 20:31:26 +0200 [thread overview]
Message-ID: <20030609203126.7fc1bb17.jrydberg@night.trouble.net> (raw)
First question of the day;
First of all I would like to say that I really like the concept of QEMU.
Let GCC do most of the work and just glue it all together. Brilliant.
One downside of it though is all the tampering with flags to GCC.
To the question. How hard would it be to make QEMU a full-system
simulator? Or, more concrete: How hard would it be to instead of using
the host memory for the simulated app, use simulated memory (on per-page
basis)?
--
Johan Rydberg, Free Software Developer, Sweden
http://rtmk.sf.net | http://www.nongnu.org/guss/
Listning to Tricky - Where I'm from
next reply other threads:[~2003-06-09 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 18:31 Johan Rydberg [this message]
2003-06-09 19:09 ` [Qemu-devel] simulated memory instead of host memory Fabrice Bellard
2003-06-09 19:37 ` Johan Rydberg
2003-06-09 20:18 ` Fabrice Bellard
2003-06-09 20:43 ` Johan Rydberg
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=20030609203126.7fc1bb17.jrydberg@night.trouble.net \
--to=jrydberg@night.trouble.net \
--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).