From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM call agenda for Jan 26 Date: Tue, 26 Jan 2010 15:24:50 +0200 Message-ID: <4B5EED22.4080009@redhat.com> References: <20100126064902.GD25779@x200.localdomain> <03EA8701-C607-4B87-A6C6-1DCD3E5DCAAC@suse.de> <4B5EE9EF.6030904@codemonkey.ws> <197BDDDF-D808-4157-8270-42B72B99BE0D@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Alexander Graf Return-path: Received: from mx1.redhat.com ([209.132.183.28]:41805 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554Ab0AZNY5 (ORCPT ); Tue, 26 Jan 2010 08:24:57 -0500 In-Reply-To: <197BDDDF-D808-4157-8270-42B72B99BE0D@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 01/26/2010 03:18 PM, Alexander Graf wrote: > > The main question is where does it belong? > > a) built into qemu > b) built as separate tool, but shipped with qemu > c) completely separate > > I'm personally leaning towards a. That way we can reuse the detection code and give help when an option is used that doesn't work. > > Me too, especially as the whole stack is involved, and qemu is the topmost part from our perspective (no doubt libvirt will want to integrate that functionality as well). -- error compiling committee.c: too many arguments to function