linux-kernel - Re: [RFC] Unify KVM kernel-space and user-space code into a single project

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: <4BA7B1AE.6050500@redhat.com>
Date:	Mon, 22 Mar 2010 20:06:38 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
CC:	Ingo Molnar <mingo@...e.hu>,
	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>,
	Gregory Haskins <ghaskins@...ell.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
 	project

On 03/22/2010 06:40 PM, Pekka Enberg wrote:
> On Mon, Mar 22, 2010 at 6:16 PM, Avi Kivity<avi@...hat.com>  wrote:
>    
>>> You simply kept ignoring me when I said that if something can be kept out
>>> of the kernel without impacting performance, it should be.  I don't want
>>> emergency patches closing some security hole or oops in a kernel symbol
>>> server.
>>>        
>> Or rather, explained how I am a wicked microkernelist.  The herring were out
>> in force today.
>>      
> Well, if it's not being a "wicked microkernelist" then what is it?
>    

I know I'm bad.

> Performance is hardly the only motivation to put things into the
> kernel. Think kernel mode-setting and devtmpfs (with the ironic twist
> of original devfs being removed from the kernel) here, for example.
>    

Motivations include privileged device access, needing to access physical 
memory, security, and keeping the userspace interface sane.  There are 
others.  I don't think any of them hold here.

-- 
error compiling committee.c: too many arguments to function

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