From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51552) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avRMA-0001Nh-Fz for qemu-devel@nongnu.org; Wed, 27 Apr 2016 11:26:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1avRM6-0005so-Fi for qemu-devel@nongnu.org; Wed, 27 Apr 2016 11:26:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39775) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avRM6-0005sj-8N for qemu-devel@nongnu.org; Wed, 27 Apr 2016 11:26:22 -0400 Date: Wed, 27 Apr 2016 17:26:16 +0200 From: Andrew Jones Message-ID: <20160427152616.4bpqvmeleebtwlfi@hawk.localdomain> References: <1456492533-17171-1-git-send-email-alex.bennee@linaro.org> <20160226141256.7rcdm3apxsnglh2p@hawk.localdomain> <87potbdr77.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <87potbdr77.fsf@linaro.org> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC 00/11] Current MTTCG kvm-unit-test patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex =?iso-8859-1?Q?Benn=E9e?= Cc: mttcg@greensocs.com, peter.maydell@linaro.org, claudio.fontana@huawei.com, a.spyridakis@virtualopensystems.com, mark.burton@greensocs.com, qemu-devel@nongnu.org, will.deacon@arm.com, a.rigo@virtualopensystems.com, crosthwaitepeter@gmail.com, pbonzini@redhat.com, rth@twiddle.net, aurelien@aurel32.net, fred.konrad@greensocs.com On Wed, Apr 27, 2016 at 04:09:00PM +0100, Alex Benn=E9e wrote: >=20 > Andrew Jones writes: >=20 > > On Fri, Feb 26, 2016 at 01:15:22PM +0000, Alex Benn=E9e wrote: > >> Hi, > >> > >> Some of these patches have been posted before and previous patches > >> have already been accepted upstream so I'm tagging this as a new RFC > >> series. > >> > >> This is a series of tests built around kvm-unit-tests but built with > >> the express purpose of stressing the TCG, in particular MTTCG builds= . > >> > >> Changes from previous appearances: > >> > >> * Separated locking and barrier tests > >> * Included Drew's IPI patches (used in tcg-test) > >> * New TCG chaining test > >> > >> The new barrier tests really only fails when running on MTTCG builds= on > >> a weak backend. Many thanks to Will Deacon for helping me get a > >> working test case at the last Connect. > >> > >> I'm mainly posting these for reference for others testing MTTCG as > >> I've still got to check I've addressed any outstanding review > >> comments. However there has been enough code churn some of the > >> comments may no longer be relevant. > >> > >> The TCG tests are also useful as benchmarks for comparing the cost o= f > >> having chained basic blocks versus exiting the loop every time. The > >> pathological case is the computed jumps test as all the addresses ar= e > >> within a PAGE_SIZE boundary the tb_jump_cache has no effect meaning = a > >> full look up each time. > >> > >> Alex Benn=E9e (8): > >> config/config-arm-common: build-up tests-common target > >> lib: add isaac prng library from CCAN > >> arm/run: set indentation defaults for emacs > >> arm/run: allow aarch64 to start arm binaries > >> arm/tlbflush-test: Add TLB torture test > >> arm/locking-tests: add comprehensive locking test > >> arm/barrier-litmus-tests: add some litmus tests > >> arm/tcg-test: some basic TCG exercising tests > >> > >> Andrew Jones (3): > >> arm/arm64: irq enable/disable > >> arm/arm64: Add initial gic support > >> arm/arm64: Add IPI test > > > > I've actually updated these patches a bit, and started extending the > > series to also work with a v3 gic. I'll pick that back up and get it > > posted for you (hopefully next week). Or I'll at least update my > > arm/ipi-test branch with the changes I've made for gicv2... >=20 > I'm getting ready to post the current iteration and I realised I hadn't > seen your updates. Have they gone public anywhere? Sorry. I didn't finish polishing the gicv3 stuff so didn't end up sending anything. I'll send something tomorrow (same story as last time, if not gicv3 stuff, at least updated gicv2 :-) Thanks, drew