lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 18 Mar 2010 14:59:44 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Daniel P. Berrange" <berrange@...hat.com>
Cc:	Avi Kivity <avi@...hat.com>, "Frank Ch. Eigler" <fche@...hat.com>,
	Alexander Graf <agraf@...e.de>,
	Anthony Liguori <anthony@...emonkey.ws>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Sheng Yang <sheng@...ux.intel.com>,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	Marcelo Tosatti <mtosatti@...hat.com>,
	oerg Roedel <joro@...tes.org>,
	Jes Sorensen <Jes.Sorensen@...hat.com>,
	Gleb Natapov <gleb@...hat.com>,
	Zachary Amsden <zamsden@...hat.com>, ziteng.huang@...el.com,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Fr?d?ric Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
 project


* Daniel P. Berrange <berrange@...hat.com> wrote:

> On Thu, Mar 18, 2010 at 02:31:24PM +0100, Ingo Molnar wrote:
> > 
> > * Avi Kivity <avi@...hat.com> 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
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ