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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 22 Mar 2010 09:13:02 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Pekka Enberg <penberg@...helsinki.fi>,
	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

On 03/21/2010 11:54 PM, Ingo Molnar wrote:
> * Avi Kivity<avi@...hat.com>  wrote:
>
>    
>> On 03/21/2010 10:55 PM, Ingo Molnar wrote:
>>      
>>> Of course you could say the following:
>>>
>>>    ' Thanks, I'll mark this for v2.6.36 integration. Note that we are not
>>>      able to add this to the v2.6.35 kernel queue anymore as the ongoing
>>>      usability work already takes up all of the project's maintainer and
>>>      testing bandwidth. If you want the feature to be merged sooner than that
>>>      then please help us cut down on the TODO and BUGS list that can be found
>>>      at XYZ. There's quite a few low hanging fruits there. '
>>>        
>> That would be shooting at my own foot as well as the contributor's since I
>> badly want that RCU stuff, and while a GUI would be nice, that itch isn't on
>> my back.
>>      
> I think this sums up the root cause of all the problems i see with KVM pretty
> well.
>    

I think we agree at last.  Neither I nor my employer are interested in 
running qemu as a desktop-on-desktop tool, therefore I don't invest any 
effort in that direction, or require it from volunteers.

If you think a good GUI is so badly needed, either write one yourself, 
or convince someone else to do it.

(btw, why are you interested in desktop-on-desktop?  one use case is 
developers, which don't really need fancy GUIs; a second is people who 
test out distributions, but that doesn't seem to be a huge population; 
and a third is people running Windows for some application that doesn't 
run on Linux - hopefully a small catergory as well.  Seems to be quite a 
small target audience, compared to, say, video editing)

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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