From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: qemu-kvm.git now live
Date: Thu, 30 Apr 2009 15:43:32 +0000 [thread overview]
Message-ID: <49F9C724.7090501@redhat.com> (raw)
In-Reply-To: <49F08BD0.6000706@redhat.com>
Jan Kiszka wrote:
>>>>>
>>>>>
>>>> Pushing things upstream is quite difficult because of the very different
>>>> infrastructure.
>>>>
>>>>
>>> Isn't the midterm goal to get rid of most of these differences (namely
>>> libkvm)?
>>>
>>>
>> Yes, but not by removing existing functionality.
>>
>
> No one said this.
>
I'm sure no one meant it either, but that is what's happening.
This is the flow:
* qemu.git has very limited kvm support
* more kvm support is added to qemu.git
* because it's a rewrite, not all the knowledge that has gone into
qemu-kvm.git is added
* when I merge qemu.git into qemu-kvm.git, the two implementation
methods clash, and things break
This has happened on most clean rewrites I've seen. The new code is
clean, but the old code works better. It's much better to morph the old
code into shape (though more time consuming and a lot less fun).
>> As is, we're adding something simple, then discovering it's
>> insufficient. We're throwing away information, that's not a good way to
>> make progress.
>>
>
> I doubt this applies here.
>
In fact it's happened. qemu-kvm.git knows that the dirty logging flag
is a shared resource. qemu-kvm.git also handles older kernels (though I
think that was intentional).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-04-30 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 15:40 qemu-kvm.git now live Avi Kivity
2009-04-29 8:49 ` Jan Kiszka
2009-04-29 10:42 ` Avi Kivity
2009-04-29 10:55 ` Jan Kiszka
2009-04-29 11:12 ` Avi Kivity
2009-04-29 11:31 ` Jan Kiszka
2009-04-29 14:40 ` Avi Kivity
2009-04-29 15:42 ` Jan Kiszka
2009-04-30 9:12 ` Avi Kivity
2009-04-30 9:29 ` Jan Kiszka
2009-04-30 10:54 ` Avi Kivity
2009-04-30 15:32 ` Jan Kiszka
2009-04-30 15:43 ` Avi Kivity [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=49F9C724.7090501@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).