From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 18 Apr 2011 20:52:34 +0200 (CEST) Received: from mail3.caviumnetworks.com ([12.108.191.235]:4506 "EHLO mail3.caviumnetworks.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S1493124Ab1DRSw1 (ORCPT ); Mon, 18 Apr 2011 20:52:27 +0200 Received: from caexch01.caveonetworks.com (Not Verified[192.168.16.9]) by mail3.caviumnetworks.com with MailMarshal (v6,7,2,8378) id ; Mon, 18 Apr 2011 11:53:24 -0700 Received: from caexch01.caveonetworks.com ([192.168.16.9]) by caexch01.caveonetworks.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Apr 2011 11:52:24 -0700 Received: from dd1.caveonetworks.com ([12.108.191.236]) by caexch01.caveonetworks.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Apr 2011 11:52:24 -0700 Message-ID: <4DAC8868.4090003@caviumnetworks.com> Date: Mon, 18 Apr 2011 11:52:24 -0700 From: David Daney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10 MIME-Version: 1.0 To: Kevin Cernekee CC: Ralf Baechle , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] MIPS: Replace _PAGE_READ with _PAGE_NO_READ References: <7aa38c32b7748a95e814e5bb0583f967@localhost> <4DAC75C6.2060504@caviumnetworks.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Apr 2011 18:52:24.0662 (UTC) FILETIME=[C194A760:01CBFDF9] Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 29783 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ddaney@caviumnetworks.com Precedence: bulk X-list: linux-mips On 04/18/2011 11:24 AM, Kevin Cernekee wrote: > On Mon, Apr 18, 2011 at 10:32 AM, David Daney wrote: >> How much testing have you done on non-RI/XI CPUs? > > On a non-RIXI CPU I was able to boot the system, run a basic GUI > application, create R/W shared mappings to /dev/mem, insert/remove > kernel modules, run a broken program that dumps core, etc. > > I guess it would be a good idea to make sure swap still works. Didn't > try that yet. > > Can you think of anything else that might exercise the bits that were > touched by the patch? Were there any tests you ran during the > development of RIXI support which uncovered subtle issues? > We run the LTP, I think it tests these things. We also have a small test case that tests for both the no-read and no-execute parts, but that would be expected to fail on platforms that don't have RI/XI bits. David Daney