From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=37084 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PkKQC-0002or-2A for qemu-devel@nongnu.org; Tue, 01 Feb 2011 12:53:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PkKQA-0006qI-Gr for qemu-devel@nongnu.org; Tue, 01 Feb 2011 12:53:43 -0500 Received: from bombadil.infradead.org ([18.85.46.34]:48008) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PkKQA-0006pe-FI for qemu-devel@nongnu.org; Tue, 01 Feb 2011 12:53:42 -0500 Date: Tue, 1 Feb 2011 12:53:36 -0500 From: Christoph Hellwig Message-ID: <20110201175336.GA22653@infradead.org> References: <20110201155414.GF28968@x200.localdomain> <4D48367D.2060802@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D48367D.2060802@siemens.com> Subject: [Qemu-devel] Re: KVM call minutes for Feb 1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Chris Wright , qemu-devel@nongnu.org, kvm@vger.kernel.org On Tue, Feb 01, 2011 at 05:36:13PM +0100, Jan Kiszka wrote: > kvm_cpu_exec/kvm_run, and start wondering "What needs to be done to > upstream so that qemu-kvm could use that implementation?". If they > differ, the reasons need to be understood and patched away, either by > fixing/enhancing upstream or simplifying qemu-kvm. Once the upstream > changes are merged back, a qemu-kvm patch is posted to switch to that > version. while I'm not an expert in that area I really like you're approach. I'd really prefer to let you finish up all the major work that way before starting massive revamping like the glib main loop. Resolving the qemu/qemu-kvm schisma surely is more important for the overall project than rewriting existing functionality to look a little nicer.