From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751381Ab1KFKHq (ORCPT ); Sun, 6 Nov 2011 05:07:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:3581 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750887Ab1KFKHo (ORCPT ); Sun, 6 Nov 2011 05:07:44 -0500 Message-ID: <4EB65C5B.8070709@redhat.com> Date: Sun, 06 Nov 2011 12:07:23 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 MIME-Version: 1.0 To: Pekka Enberg CC: Alexander Graf , Linus Torvalds , Ingo Molnar , "linux-kernel@vger.kernel.org List" , "kvm@vger.kernel.org list" , qemu-devel Developers , =?ISO-8859-1?Q?Am=E9rico_Wang?= , Blue Swirl Subject: Re: [PATCH] KVM: Add wrapper script around QEMU to test kernels References: <1320543320-32728-1-git-send-email-agraf@suse.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/06/2011 12:04 PM, Pekka Enberg wrote: > Hi Alexander, > > On Sun, Nov 6, 2011 at 3:35 AM, Alexander Graf wrote: > > On LinuxCon I had a nice chat with Linus on what he thinks kvm-tool > > would be doing and what he expects from it. Basically he wants a > > small and simple tool he and other developers can run to try out and > > see if the kernel they just built actually works. > > > > Fortunately, QEMU can do that today already! The only piece that was > > missing was the "simple" piece of the equation, so here is a script > > that wraps around QEMU and executes a kernel you just built. > > I'm happy to see some real competition for the KVM tool in usability. ;-) > > That said, while the script looks really useful for developers, > wouldn't it make more sense to put it in QEMU to make sure it's kept > up-to-date and distributions can pick it up too? (And yes, I realize > the irony here.) Why would distributions want it? It's only useful for kernel developers. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: Add wrapper script around QEMU to test kernels Date: Sun, 06 Nov 2011 12:07:23 +0200 Message-ID: <4EB65C5B.8070709@redhat.com> References: <1320543320-32728-1-git-send-email-agraf@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org list" , "linux-kernel@vger.kernel.org List" , qemu-devel Developers , Alexander Graf , Blue Swirl , =?ISO-8859-1?Q?Am=E9rico_Wang?= , Ingo Molnar , Linus Torvalds To: Pekka Enberg Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 11/06/2011 12:04 PM, Pekka Enberg wrote: > Hi Alexander, > > On Sun, Nov 6, 2011 at 3:35 AM, Alexander Graf wrote: > > On LinuxCon I had a nice chat with Linus on what he thinks kvm-tool > > would be doing and what he expects from it. Basically he wants a > > small and simple tool he and other developers can run to try out and > > see if the kernel they just built actually works. > > > > Fortunately, QEMU can do that today already! The only piece that was > > missing was the "simple" piece of the equation, so here is a script > > that wraps around QEMU and executes a kernel you just built. > > I'm happy to see some real competition for the KVM tool in usability. ;-) > > That said, while the script looks really useful for developers, > wouldn't it make more sense to put it in QEMU to make sure it's kept > up-to-date and distributions can pick it up too? (And yes, I realize > the irony here.) Why would distributions want it? It's only useful for kernel developers. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47279) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RMzdf-0002Kn-6z for qemu-devel@nongnu.org; Sun, 06 Nov 2011 05:07:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RMzde-0003JV-4P for qemu-devel@nongnu.org; Sun, 06 Nov 2011 05:07:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37016) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RMzdd-0003JO-Tg for qemu-devel@nongnu.org; Sun, 06 Nov 2011 05:07:42 -0500 Message-ID: <4EB65C5B.8070709@redhat.com> Date: Sun, 06 Nov 2011 12:07:23 +0200 From: Avi Kivity MIME-Version: 1.0 References: <1320543320-32728-1-git-send-email-agraf@suse.de> 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: "kvm@vger.kernel.org list" , "linux-kernel@vger.kernel.org List" , qemu-devel Developers , Alexander Graf , Blue Swirl , =?ISO-8859-1?Q?Am=E9rico_Wang?= , Ingo Molnar , Linus Torvalds On 11/06/2011 12:04 PM, Pekka Enberg wrote: > Hi Alexander, > > On Sun, Nov 6, 2011 at 3:35 AM, Alexander Graf wrote: > > On LinuxCon I had a nice chat with Linus on what he thinks kvm-tool > > would be doing and what he expects from it. Basically he wants a > > small and simple tool he and other developers can run to try out and > > see if the kernel they just built actually works. > > > > Fortunately, QEMU can do that today already! The only piece that was > > missing was the "simple" piece of the equation, so here is a script > > that wraps around QEMU and executes a kernel you just built. > > I'm happy to see some real competition for the KVM tool in usability. ;-) > > That said, while the script looks really useful for developers, > wouldn't it make more sense to put it in QEMU to make sure it's kept > up-to-date and distributions can pick it up too? (And yes, I realize > the irony here.) Why would distributions want it? It's only useful for kernel developers. -- error compiling committee.c: too many arguments to function