From: Kevin O'Connor <kevin@koconnor.net>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [ANN] Bochs bios ported to gcc
Date: Sun, 6 Apr 2008 11:03:33 -0400 [thread overview]
Message-ID: <20080406150333.GA19241@ohio.lan> (raw)
In-Reply-To: <47F8BC77.3060106@qumranet.com>
On Sun, Apr 06, 2008 at 03:05:11PM +0300, Avi Kivity wrote:
> Kevin O'Connor wrote:
>> I have been working on a port of bochs bios to gcc.
>
> While moving away from the horror that is bcc is a blessing, the way to
> really benefit from it is to have this code replace the original bochs
> bios. This way updates to the bochs bios are not lost for anyone using the
> new code.
I agree. I've been interacting with the bochs developers since I
started (about a month and half ago).
> Have you proposed replacing the bios to the bochs developers? What was the
> reaction?
The reaction was pretty "quiet". The bochs project is not nearly as
active as kvm, and the bios is just one small part of that project.
Now that the new code can actually launch a wide variety of payloads,
I'm hoping there will be more interest.
BTW, if anyone is interested in testing, please grab the 0.2.1 version
- the v0.2.0 version had a nasty bug on disk writes to large disks
(assuming one uses an OS that writes to disk via the bios).
-Kevin
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-06 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 1:42 [ANN] Bochs bios ported to gcc Kevin O'Connor
2008-04-06 12:05 ` Avi Kivity
2008-04-06 15:03 ` Kevin O'Connor [this message]
2008-04-07 6:42 ` H. Peter Anvin
2008-04-07 13:05 ` Kevin O'Connor
2008-04-07 16:18 ` H. Peter Anvin
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=20080406150333.GA19241@ohio.lan \
--to=kevin@koconnor.net \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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