From: Avi Kivity <avi@redhat.com>
To: Chris Frey <cdfrey@foursquare.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Killing KQEMU
Date: Tue, 02 Jun 2009 09:28:50 +0300 [thread overview]
Message-ID: <4A24C6A2.6070007@redhat.com> (raw)
In-Reply-To: <4A24A806.4060609@redhat.com>
Avi Kivity wrote:
>> I find it hard to believe that these 674 lines of code are too much for
>> the substantial braintrust available on this list.
>>
>
> kqemu is a lot larger than 674 lines; what you're looking at is
> probably the glue module from the pre-GPL days that loads into the
> kernel and links into the real kqemu which was supplied as a binary.
kqemu weighs in at more than 14,000 lines of pretty complicated code.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-06-02 6:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 3:52 [Qemu-devel] Killing KQEMU Chris Frey
2009-06-02 4:18 ` Avi Kivity
2009-06-02 6:28 ` Avi Kivity [this message]
2009-06-02 19:25 ` [Qemu-devel] " Chris Frey
2009-06-02 4:45 ` [Qemu-devel] " Rick Vernam
2009-06-02 12:54 ` Paul Brook
2009-06-02 20:09 ` [Qemu-devel] " Chris Frey
2009-06-02 20:24 ` Avi Kivity
2009-06-03 21:50 ` [Qemu-devel] " Chris Frey
2009-06-04 6:30 ` [Qemu-devel] " Avi Kivity
2009-06-02 20:30 ` Paul Brook
2009-06-03 21:34 ` Chris Frey
2009-06-03 21:46 ` Rick Vernam
2009-06-06 11:01 ` Andreas Färber
2009-06-06 11:27 ` Paul Brook
2009-06-06 13:50 ` Andreas Färber
2009-06-06 15:24 ` Gleb Natapov
2009-06-06 16:03 ` Avi Kivity
2009-06-02 20:35 ` Gerd Hoffmann
2009-06-02 20:47 ` Stuart Brady
2009-06-03 21:21 ` [Qemu-devel] " Chris Frey
2009-06-04 0:22 ` Paul Brook
2009-06-02 6:25 ` [Qemu-devel] " Gleb Natapov
2009-06-02 9:26 ` Anton D Kachalov
2009-06-02 19:47 ` [Qemu-devel] " Chris Frey
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=4A24C6A2.6070007@redhat.com \
--to=avi@redhat.com \
--cc=cdfrey@foursquare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.