From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH -v2] Add MCE support to KVM Date: Tue, 21 Apr 2009 15:08:34 -0500 Message-ID: <49EE27C2.3060505@codemonkey.ws> References: <1239953345.6842.3.camel@yhuang-dev.sh.intel.com> <49E9F7BE.4090904@codemonkey.ws> <49EAE334.9020803@redhat.com> <49EDF057.9060501@codemonkey.ws> <49EDF287.9020908@redhat.com> <49EE2497.3060009@codemonkey.ws> <49EE25CB.6070709@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Huang Ying , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Andi Kleen To: Avi Kivity Return-path: Received: from yw-out-2324.google.com ([74.125.46.30]:3180 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752231AbZDUUIi (ORCPT ); Tue, 21 Apr 2009 16:08:38 -0400 In-Reply-To: <49EE25CB.6070709@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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