linux-kernel - Re: [ANNOUNCE] Native Linux KVM tool

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]

Message-ID: <20110406101405.GA65838@dspnet.fr>
Date:	Wed, 6 Apr 2011 12:14:05 +0200
From:	Olivier Galibert <galibert@...ox.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Avi Kivity <avi@...hat.com>,
	Anthony Liguori <anthony@...emonkey.ws>,
	Pekka Enberg <penberg@...nel.org>,
	linux-kernel@...r.kernel.org, aarcange@...hat.com,
	mtosatti@...hat.com, kvm@...r.kernel.org, joro@...tes.org,
	penberg@...helsinki.fi, asias.hejun@...il.com, gorcunov@...il.com
Subject: Re: [ANNOUNCE] Native Linux KVM tool

On Wed, Apr 06, 2011 at 11:33:33AM +0200, Ingo Molnar wrote:
> Examples: X11 and GCC - both were struggling for years to break through magic 
> invisible barriers of growth and IMHO a lot of it had to do with the lack of 
> code (and development model) cleanliness.

A large part of what's killing X11 and qemu is the decomposition in
multiple trees and the requirement that every version must work with
every other version.

For X11 you have:
- the server
- the protocol headers
- the individual 2D drivers
- libdrm
- the kernel
- mesa
- the video decoding driver/libs

For qemu you have:
- qemu
- qemu-kvm
- the kernel
- libvirt
- seabios

Any reaching change ends up hitting most of the trees, with all to
coordination that means.  And in any case you're supposed to handle
any version of the other components.

Virtualbox works in part because they provide everything, from the
dhcp server to the kernel modules.  The NVidia closed-source drivers
works in part because they provide everything, from the glx interface
to the kernel modules.  And both of them refuse to start if everything
is not in lockstep.  Meanwhile the open source idealists are a way
smaller number and expect to support every combination of everything
with everything as long as it appeared one day in a release, no matter
how buggy or badly designed it was.

So less people, additional hurdles that experience has shown not to be
a necessity (people cope with lockstep updates, vbox and nvidia prove
it), and one wonders why the "open" solutions end up way inferior?

  OG.

--
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/