From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34736) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgJxv-00070l-Qz for qemu-devel@nongnu.org; Thu, 29 Dec 2011 12:40:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RgJxu-00057o-1b for qemu-devel@nongnu.org; Thu, 29 Dec 2011 12:40:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:32628) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgJxt-00057i-RF for qemu-devel@nongnu.org; Thu, 29 Dec 2011 12:40:30 -0500 Message-ID: <4EFCA605.8020104@redhat.com> Date: Thu, 29 Dec 2011 19:40:21 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4EEF70B4.3070109@us.ibm.com> <4EF73EF5.8050606@redhat.com> <4EF88EC0.8020301@codemonkey.ws> <4EF8FC88.70809@redhat.com> <4EFA4829.4000207@redhat.com> <4EFA80EA.3050405@codemonkey.ws> <4EFAA2A2.4000107@redhat.com> <4EFB2764.7040006@codemonkey.ws> <4EFB2F36.2090408@redhat.com> <4EFB35AB.6040003@redhat.com> <4EFB4757.4020504@codemonkey.ws> <4EFB5138.5020502@redhat.com> <4EFC916E.4070902@codemonkey.ws> <4EFC9706.4090500@redhat.com> <4EFCA2AF.5000806@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [ANNOUNCE] qemu-test: a set of tests scripts for QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "lmr@redhat.com" , Stefan Hajnoczi , cleber@redhat.com, dlaor@redhat.com, qemu-devel , Gerd Hoffmann , Cleber Rosa On 12/29/2011 07:36 PM, Peter Maydell wrote: > On 29 December 2011 17:26, Avi Kivity wrote: > > On 12/29/2011 07:22 PM, Peter Maydell wrote: > >> I think for devices what would be particularly useful would be > >> if you can write a (simple) test for something at the register > >> level, which generates an image which you can run on the real > >> hardware as well as on QEMU. Then you can confirm that your test > >> case is correct. Otherwise the tests are just going to bake in the > >> same assumptions/misconceptions about what the hardware does as > >> the QEMU model. > > > > That is exactly qtest. > > Am I missing something? I looked at the qtest patches and they seem > to work by just prodding the device through qemu function calls, > not by running a guest CPU binary that prods the device. Sorry, I misread your post. I guess we can point a qtest test at real hardware too, if something like vfio is available to provide access to registers and to hook interrupts. -- error compiling committee.c: too many arguments to function