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]

Date:	Tue, 23 Mar 2010 18:39:58 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Joerg Roedel <joro@...tes.org>
CC:	Anthony Liguori <anthony@...emonkey.ws>,
	Ingo Molnar <mingo@...e.hu>,
	Pekka Enberg <penberg@...helsinki.fi>,
	"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>,
	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/23/2010 04:06 PM, Joerg Roedel wrote:
> On Mon, Mar 22, 2010 at 05:06:17PM -0500, Anthony Liguori wrote:
>    
>> There always needs to be a system wide entity.  There are two ways to
>> enumerate instances from that system wide entity.  You can centralize
>> the creation of instances and there by maintain an list of current
>> instances.  You can also allow instances to be created in a
>> decentralized manner and provide a standard mechanism for instances to
>> register themselves with the system wide entity.
>>      
> And this system wide entity is the kvm module. It creates instances of
> 'struct kvm' and destroys them. I see no problem if we just attach a
> name to every instance with a good default value like kvm0, kvm1 ... or
> guest0, guest1 ... User-space can override the name if it wants. The kvm
> module takes care about the names being unique.
>    

So, two users can't have a guest named MyGuest each?  What about 
namespace support?  There's a lot of work in virtualizing all kernel 
namespaces, you're adding to that.  What about notifications when guests 
are added or removed?

> This is very much the same as network card numbering is implemented in
> the kernel.
> Forcing perf to talk to qemu or even libvirt produces to much overhead
> imho. Instrumentation only produces useful results with low overhead.
>
>    

It's a setup cost only.

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