Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423338AbcKALuL (ORCPT ); Tue, 1 Nov 2016 07:50:11 -0400 Received: from mailapp01.imgtec.com ([195.59.15.196]:47577 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1168995AbcKALuJ (ORCPT ); Tue, 1 Nov 2016 07:50:09 -0400 Date: Tue, 1 Nov 2016 11:49:56 +0000 From: "Maciej W. Rozycki" To: Paul Burton CC: Ralf Baechle , , Subject: Re: [PATCH 3/4] MIPS: Fix ISA I/II FP signal context offsets In-Reply-To: <1814661.4I5xJD6gaP@np-p-burton> Message-ID: References: <1814661.4I5xJD6gaP@np-p-burton> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [10.20.78.238] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1400 Lines: 30 On Tue, 1 Nov 2016, Paul Burton wrote: > BTW, do you have a feel for whether there's a good r2k/r3k platform (ideal > would be some software emulator if any are good enough) that we could hook up > to our continuous integration system? That would help us to catch any > regressions like this in future before they hit mainline. I know about no such platform I'm afraid. QEMU does not have the R2k/R3k exception/MMU/cache model and implementing that would be a considerable effort I see no volunteers for. I haven't heard of any other simulator which might be closer to implementing that model. As to using real hardware -- I might be the closest myself to be capable of doing some automated testing as I have an R3k machine in my home lab wired for remote control. It could track Ralf's `mips-for-linux-next' branch and watch out for regressions, by trying to build and boot kernels automatically on a regular basis; maybe doing some further validation even, such as running GCC or glibc regression testing. But while the target is ready I'm still missing the host-side setup, which I haven't completed. I don't think there's any other hardware readily available which could be hooked somewhere. So for the time being I think we need to continue relying on people spotting issues by hand. I think we've been doing pretty good overall. Thanks for your review. Maciej