From: Ryan Rempel <rgrempel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Accelerator for FreeBSD?
Date: Sun, 20 Mar 2005 19:42:41 -0600 [thread overview]
Message-ID: <fb5ec42305032017423b7e66a2@mail.gmail.com> (raw)
There is a reference here [1] to the possibility of porting the
Accelerator to *BSD by porting a small "C stub".
Is anyone working on this at the moment? If not, would it be possible
to make the "C stub" available so that someone could give it a try?
I'd be interested in taking a crack at it myself, but there may be
others better situated (I've not done FreeBSD kernel development
before, but I have done some Darwin kernel development).
That's assuming that the reference is at all accurate :-)
[1] http://www.dad-answers.com/qemu-forum/viewtopic.php?t=333
next reply other threads:[~2005-03-21 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 1:42 Ryan Rempel [this message]
2005-03-21 4:22 ` [Qemu-devel] Accelerator for FreeBSD? Mikko Työläjärvi
2005-03-21 14:57 ` KQEMU on FreeBSD partially works. (Was: [Qemu-devel] Accelerator for FreeBSD?) Antony T Curtis
2005-03-23 1:27 ` Ryan Rempel
2005-03-23 12:15 ` Antony T Curtis
2005-03-23 13:58 ` Antony T Curtis
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=fb5ec42305032017423b7e66a2@mail.gmail.com \
--to=rgrempel@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).