From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project Date: Sun, 21 Mar 2010 18:43:15 -0500 Message-ID: <4BA6AF13.2030602@codemonkey.ws> References: <20100318170223.GB9756@elte.hu> <4BA25E66.2050800@redhat.com> <20100318172805.GB26067@elte.hu> <4BA32E1A.2060703@redhat.com> <20100319085346.GG12576@elte.hu> <4BA3747F.60401@codemonkey.ws> <20100321191742.GD25922@elte.hu> <4BA674F1.6070603@nagafix.co.uk> <20100321195903.GA29490@elte.hu> <4BA67D0B.9030705@redhat.com> <20100321210011.GD30194@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Antoine Martin , Pekka Enberg , "Zhang, Yanmin" , Peter Zijlstra , Sheng Yang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Marcelo Tosatti , oerg Roedel , Jes Sorensen , Gleb Natapov , Zachary Amsden , ziteng.huang@intel.com, Arnaldo Carvalho de Melo , Fr?d?ric Weisbecker To: Ingo Molnar Return-path: Received: from mail-vw0-f46.google.com ([209.85.212.46]:63439 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752476Ab0CUXnU (ORCPT ); Sun, 21 Mar 2010 19:43:20 -0400 In-Reply-To: <20100321210011.GD30194@elte.hu> Sender: kvm-owner@vger.kernel.org List-ID: On 03/21/2010 04:00 PM, Ingo Molnar wrote: > * Avi Kivity wrote: > > >> On 03/21/2010 09:59 PM, Ingo Molnar wrote: >> >>> Frankly, i was surprised (and taken slightly off base) by both Avi and Anthony >>> suggesting such a clearly inferior "add a demon to the guest space" solution. >>> It's a usability and deployment non-starter. >>> >> It's only clearly inferior if you ignore every consideration against it. >> It's definitely not a deployment non-starter, see the tons of daemons that >> come with any Linux system. [...] >> > Avi, please dont put arguments into my mouth that i never made. > > My (clearly expressed) argument was that: > > _a new guest-side demon is a transparent instrumentation non-starter_ > FWIW, there's no reason you couldn't consume a vmchannel port from within the kernel. I don't think the code needs to be in the kernel and from a security PoV, that suggests that it should be in userspace IMHO. But if you want to make a kernel thread, knock yourself out. I have no objection to that from a qemu perspective. I can't see why Avi would mind either. I think it's papering around another problem (the kernel should control initrds IMHO) but that's a different topic. Regards, Anthony Liguori