From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43543) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgcmR-0001Im-RF for qemu-devel@nongnu.org; Fri, 30 Dec 2011 08:45:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RgcmQ-0006Sn-Vq for qemu-devel@nongnu.org; Fri, 30 Dec 2011 08:45:55 -0500 Received: from mout.web.de ([212.227.15.4]:51856) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgcmQ-0006SH-KW for qemu-devel@nongnu.org; Fri, 30 Dec 2011 08:45:54 -0500 Message-ID: <4EFDC03E.5050507@web.de> Date: Fri, 30 Dec 2011 14:44:30 +0100 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= 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> <4EFCB274.5020102@codemonkey.ws> In-Reply-To: <4EFCB274.5020102@codemonkey.ws> 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: Anthony Liguori Cc: "lmr@redhat.com" , Peter Maydell , Stefan Hajnoczi , cleber@redhat.com, dlaor@redhat.com, qemu-devel , Avi Kivity , Cleber Rosa , Paolo Bonzini , Gerd Hoffmann Am 29.12.2011 19:33, schrieb Anthony Liguori: > I don't think we should focus much on qtest for non-x86 targets. I > mean, if you are interested in it for ARM, fantastic, but I don't think > we would mandate it. I'm actually very interested in having a qtest framework for non-x86 for a) unit testing TCG (execute instruction, check register/memory results) b) unit testing device emulation Your v2 qtest RFC is still missing the libqtest C implementation. We code in C so I'd like to test b) in C, not Python or some random other language that someone happens to like for whatever reason. Andreas