From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MASum-0003NF-HV for qemu-devel@nongnu.org; Sat, 30 May 2009 14:04:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MASug-0003Ht-Vv for qemu-devel@nongnu.org; Sat, 30 May 2009 14:04:16 -0400 Received: from [199.232.76.173] (port=60344 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MASug-0003Hb-Se for qemu-devel@nongnu.org; Sat, 30 May 2009 14:04:10 -0400 Received: from smtp3-g21.free.fr ([212.27.42.3]:34068) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MASuf-0001Ys-R5 for qemu-devel@nongnu.org; Sat, 30 May 2009 14:04:10 -0400 In-Reply-To: <4A1FA616.7040402@siemens.com> Subject: Re: [Qemu-devel] Re: [PATCH] remove pieces of source code From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Sat, 30 May 2009 20:04:02 +0200 CEST Message-Id: <6013601887-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: glommer@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org > > That said, here are the arguments for keeping kqemu > > > > o Even though it's unmaintained, it seems to work for people > > At some point, I bet, at least the Linux bindings will break, and no > one > will be interested or able to fix that anymore. Same may happen to > other > platforms (doesn't Windows 7 come with a new driver model=3F). Yes and MS even made supplications to hw vendors to write drivers for it, as they got slapped by their own monopoly practices :D Instead they should just ask them to release specs so everyone can write drivers for their own OS and restore fair competition... > > o There is no alternative for non-Linux users and folks with non- > > VT/SVM > > hardware > > The non-HVM argument will become widely irrelevant (for desktops) > very Hmm not everyone has the money to renew their hw every year or so. I still have an AthlonXP and a PentiumM based laptop here, which do work fine. > soon. The non-Linux issue will likely persist - unless someone feels > so > much pain to write some KVM for those platforms. But as long as there > is Well, some FOSS devs have a tendancy those years to act like proprietary devs, disregarding other OSes as "non existant, not relevant" and so "not worth caring", which is both quite irritating and wrong, since many of those actually account for the technodiversity necessary to keep "innovation" going. I still remember all the buzz I read about Linux getting "tickless", wow, I mean like, BeOS had it 10 years ago (and Irix probably also but it wasn't really desktop oriented). Just like ALSA, which is written by Linux, for Linux, without everyone else in mind, discrediting OSS API, which actually is defacto std on UNIX, and making it unportable to anything else. Maybe those things like KVM could be written in a portable way... OSSv4 proves kernel code can be written in a portable way, despite them having to maintain a huge ugly kludge to account for the total lack of a stable DDM API in Linux... and again the total disregard from Linux devs dismissing the problem as "you aren't in the kernel tree, you don't exist". Of course they wouldn't include OSSv4 in the tree since it's meant to be portable anyway. Still, Haiku proves one can go forward yet have a stable driver API. the OSSv4 BeOS port runs fine in Haiku : http://revolf.free.fr/Alchimie-7/Alchimie7=5FOSS=5FHaiku.en.pdf yet we have a new DDM, bluetooth support, ... Couldn't they just write their KVM code cleanly =3F Fran=C3=A7ois.