From: Derek Fawcus <dfawcus@cisco.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] virtualization
Date: Sat, 26 Mar 2005 22:26:24 +0000 [thread overview]
Message-ID: <20050326222624.S21020@mrwint.cisco.com> (raw)
In-Reply-To: <ee9e417a0503260954513208ee@mail.gmail.com>; from russcox@gmail.com on Sat, Mar 26, 2005 at 12:54:22PM -0500
On Sat, Mar 26, 2005 at 12:54:22PM -0500, Russ Cox wrote:
> qemu now accepts kernel help in executing its vm.
> http://fabrice.bellard.free.fr/qemu/qemu-accel.html
>
> the interesting parts of the kernel module itself are
> closed, but the interface that qemu uses is open.
> if anyone out there feels like x86 hacking, it would
> be cool to have a plan 9 version of the module so
> that qemu could be used as a vmware-substitute
> that ran on top of plan 9.
Hmm. qemu depends upon some 'interesting' code generation
using the output of GCC. So it _really_ needs gcc
as the compiler - generating ELF.
(There are some other flavours of output, but I'm not sure
if they're easier than ELF - have a read of dyngen.c)
DF
prev parent reply other threads:[~2005-03-26 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 17:54 Russ Cox
2005-03-26 22:26 ` Derek Fawcus [this message]
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=20050326222624.S21020@mrwint.cisco.com \
--to=dfawcus@cisco.com \
--cc=9fans@cse.psu.edu \
/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).