From: David Daney <ddaney@caviumnetworks.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] MIPS: Replace _PAGE_READ with _PAGE_NO_READ
Date: Mon, 18 Apr 2011 11:52:24 -0700 [thread overview]
Message-ID: <4DAC8868.4090003@caviumnetworks.com> (raw)
In-Reply-To: <BANLkTinbFNvez+G4LpmF7uwwJrH_J1NK8w@mail.gmail.com>
On 04/18/2011 11:24 AM, Kevin Cernekee wrote:
> On Mon, Apr 18, 2011 at 10:32 AM, David Daney<ddaney@caviumnetworks.com> 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
next prev parent reply other threads:[~2011-04-18 18:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 16:44 [PATCH 1/4] MIPS: Replace _PAGE_READ with _PAGE_NO_READ Kevin Cernekee
2011-04-16 16:44 ` [PATCH 2/4] MIPS: Add dummy _PAGE_NO_EXEC field for R3000 and 64BIT_PHYS_ADDR cases Kevin Cernekee
2011-05-12 14:12 ` Ralf Baechle
2011-04-16 16:44 ` [PATCH 3/4] MIPS: Clean up protection_map[] initialization Kevin Cernekee
2011-05-12 14:12 ` Ralf Baechle
2011-04-16 16:44 ` [PATCH 4/4] MIPS: Remove unused PAGE_* definitions Kevin Cernekee
2011-05-12 14:12 ` Ralf Baechle
2011-04-18 17:32 ` [PATCH 1/4] MIPS: Replace _PAGE_READ with _PAGE_NO_READ David Daney
2011-04-18 18:24 ` Kevin Cernekee
2011-04-18 18:52 ` David Daney [this message]
2011-05-12 14:12 ` Ralf Baechle
2011-05-13 15:07 ` Ralf Baechle
2011-05-13 15:46 ` Kevin Cernekee
2011-05-13 15:56 ` Ralf Baechle
2011-05-13 16:55 ` Kevin Cernekee
2011-05-13 17:36 ` Jayachandran C.
2011-05-13 17:51 ` Kevin Cernekee
2011-05-13 18:45 ` Jayachandran C.
2011-05-13 18:57 ` David Daney
2011-05-13 22:00 ` Arnaud Patard
2011-05-13 22:06 ` Kevin Cernekee
2011-05-14 5:13 ` Jayachandran C.
2011-05-14 6:02 ` Kevin Cernekee
2011-05-16 12:57 ` Jayachandran C.
2011-05-13 17:17 ` David Daney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DAC8868.4090003@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=cernekee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox