From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38626) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNOZX-00013N-Fo for qemu-devel@nongnu.org; Mon, 07 Nov 2011 07:45:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RNOZR-0004ov-1I for qemu-devel@nongnu.org; Mon, 07 Nov 2011 07:45:07 -0500 Received: from mx1.redhat.com ([209.132.183.28]:32436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNOZQ-0004on-Oa for qemu-devel@nongnu.org; Mon, 07 Nov 2011 07:45:01 -0500 Message-ID: <4EB7D2C0.80201@redhat.com> Date: Mon, 07 Nov 2011 14:44:48 +0200 From: Avi Kivity MIME-Version: 1.0 References: <1320543320-32728-1-git-send-email-agraf@suse.de> <4EB65C5B.8070709@redhat.com> <4EB66036.4080102@redhat.com> <1320577728.1428.73.camel@jaguar> <4EB67486.1070105@redhat.com> <4EB67D17.7000701@redhat.com> <4EB680D9.2070706@redhat.com> <877C82F4-F07C-44AA-8722-3AF57CFC4597@suse.de> <4EB7B1A9.9000409@redhat.com> <4EB7CE71.50401@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] KVM: Add wrapper script around QEMU to test kernels List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pekka Enberg Cc: Alexander Graf , "kvm@vger.kernel.org list" , qemu-devel Developers , "linux-kernel@vger.kernel.org List" , Blue Swirl , Sasha Levin , =?ISO-8859-1?Q?Am=E9rico_Wang?= , Ingo Molnar , Linus Torvalds , Gerd Hoffmann On 11/07/2011 02:29 PM, Pekka Enberg wrote: > Hi Avi, > > On Mon, Nov 7, 2011 at 2:26 PM, Avi Kivity wrote: > >> tools/power was merged in just 2 versions ago, do you think that > >> merging that was a mistake? > > > > Things like tools/power may make sense, most of the code is tied to the > > kernel interfaces. tools/kvm is 20k lines and is likely to be 40k+ > > lines or more before it is generally usable. The proportion of the code > > that talks to the kernel is quite small. > > So what do you think about perf then? The amount of code that talks to > the kernel is much smaller than that of the KVM tool. Maybe it's outgrown the kernel repo too. Certainly something that has perl and python integration, a TUI, and one day hopefully a GUI, doesn't really need the kernel sources. -- error compiling committee.c: too many arguments to function