[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49EE27C2.3060505@codemonkey.ws>
Date: Tue, 21 Apr 2009 15:08:34 -0500
From: Anthony Liguori <anthony@...emonkey.ws>
To: Avi Kivity <avi@...hat.com>
CC: Huang Ying <ying.huang@...el.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH -v2] Add MCE support to KVM
Avi Kivity wrote:
> No argument. But some kernel features will require major rework in
> qemu before we can support them properly. We'll still want to bring
> them to users quickly so users can enjoy them (and we can enjoy users
> testing them). Waiting for a qemu rework may take a while, and we'll
> lose valuable feedback.
Then we're failing. If a particular implementation of a feature is
acceptable for kvm-userspace users, and we don't take it in QEMU without
requiring a huge amount of different work, then it suggests something is
broken about the QEMU process.
> For this kind of work, we can provide kvm-userspace.git as a kind of
> playground where these experiments may be made. kvm-userspace.git
> exists to support kvm.git; while qemu.git has a life of its own and
> more stringent barriers to acceptance.
As long as people are using kvm-userspace.git instead of qemu.git, we're
failing IMHO. If kvm-userspace.git is basically the equivalent of the
x86 git kernel tree, linux-next, or something like that, then that's a
good thing.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists