From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753768Ab0CROAA (ORCPT ); Thu, 18 Mar 2010 10:00:00 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:37140 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753703Ab0CRN77 (ORCPT ); Thu, 18 Mar 2010 09:59:59 -0400 Date: Thu, 18 Mar 2010 14:59:44 +0100 From: Ingo Molnar To: "Daniel P. Berrange" Cc: Avi Kivity , "Frank Ch. Eigler" , Alexander Graf , Anthony Liguori , "Zhang, Yanmin" , Peter Zijlstra , Sheng Yang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Marcelo Tosatti , oerg Roedel , Jes Sorensen , Gleb Natapov , Zachary Amsden , ziteng.huang@intel.com, Arnaldo Carvalho de Melo , Fr?d?ric Weisbecker Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project Message-ID: <20100318135944.GD25642@elte.hu> References: <20100318085607.GB2157@elte.hu> <20100318101025.GA13073@elte.hu> <4BA1FEB0.7000400@redhat.com> <20100318113527.GA13168@elte.hu> <20100318130226.GB7424@elte.hu> <4BA22663.7070509@redhat.com> <20100318133124.GA25642@elte.hu> <20100318134457.GH22775@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100318134457.GH22775@redhat.com> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Daniel P. Berrange wrote: > On Thu, Mar 18, 2010 at 02:31:24PM +0100, Ingo Molnar wrote: > > > > * Avi Kivity wrote: > > > > > On 03/18/2010 03:02 PM, Ingo Molnar wrote: > > > > > > > >> [...] What users eagerly replace their kernels? > > > > > > > > Those 99% who click on the 'install 193 updates' popup. > > > > > > > > > > Of which 1 is the kernel, and 192 are userspace updates (of which one may be > > > qemu). > > > > I think you didnt understand my (tersely explained) point - which is probably > > my fault. What i said is: > > > > - distros update the kernel first. Often in stable releases as well if > > there's a new kernel released. (They must because it provides new hardware > > enablement and other critical changes they generally cannot skip.) > > > > - Qemu on the other hand is not upgraded with (nearly) that level of urgency. > > Completely new versions will generally have to wait for the next distro > > release. > > This has nothing todo with them being in separate source repos. We could > update QEMU to new major feature releaes with the same frequency in a Fedora > release, but we delibrately choose not to rebase the QEMU userspace because > experiance has shown the downside from new bugs / regressions outweighs the > benefit of any new features. > > The QEMU updates in stable Fedora trees, now just follow the minor bugfix > release stream provided by QEMU & those arrive in Fedora with little > noticable delay. That is exactly what i said: Qemu and most user-space packages are on a 'slower' update track than the kernel: generally updated for minor releases. My further point was that the kernel on the other hand gets updated more frequently and as such, any user-space tool bits hosted in the kernel repo get updated more frequently as well. Thanks, Ingo