From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqLKb-0000rY-K5 for qemu-devel@nongnu.org; Thu, 07 May 2015 08:55:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YqLKX-0005n1-Kr for qemu-devel@nongnu.org; Thu, 07 May 2015 08:55:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50308) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqLKX-0005mp-Fe for qemu-devel@nongnu.org; Thu, 07 May 2015 08:55:09 -0400 Message-ID: <554B60A7.2050904@redhat.com> Date: Thu, 07 May 2015 14:55:03 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1430998302-31502-1-git-send-email-a.spyridakis@virtualopensystems.com> In-Reply-To: <1430998302-31502-1-git-send-email-a.spyridakis@virtualopensystems.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFC 0/2] virt bare-metal payload infrastructure with atomic test case List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Spyridakis , qemu-devel@nongnu.org Cc: mttcg@greensocs.com, jani.kokkonen@huawei.com, tech@virtualopensystems.com, claudio.fontana@huawei.com On 07/05/2015 13:31, Alexander Spyridakis wrote: > This series implements a bare-metal test payload for the ARM and AARCH64 virt > machine models. With the new direction of TCG to finally get multi-threaded > capabilities, simple and easily deployed tests are needed, to reproduce race > conditions and intuitively debug QEMU's TCG internals. > > The goal of the series is to provide an easy way to create SMP guest test cases > with minimal initialization. In its current state the provided features are, > SMP functionality through PSCI calls, a simple spinlock test-case, and > a minimal printf implementation based on the multiboot test. Parts of this > payload have been also tested with normal hosts, as well as KVM guests. > > For the example spinlock test, racing errors could not be reproduced in > the default single-threaded TCG, even with a non-atomic lock. In KVM the > expected behaviour of no errors with regular locks, and some errors with > a non-atomic lock was observed. Next steps are to test multi-threaded TCG > with this kind of payloads, extend the infrastructure to more complex and > sensitive test cases, as well as support different architectures. Can we reuse the kvm-unit-tests infrastructure? As you said, the testcases should run just as well with TCG and KVM. Paolo