From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <18079.63067.248965.356540@cargo.ozlabs.ibm.com> Date: Fri, 20 Jul 2007 09:40:11 +1000 From: Paul Mackerras To: Segher Boessenkool Subject: Re: [PATCH] Treat ISI faults as read faults on classic 32-bit PowerPC In-Reply-To: References: <11847726193856-git-send-email-segher@kernel.crashing.org> <5d56173bee3f9ea0050aa508e7f27cc932af7229.1184104284.git.segher@kernel.crashing.org> <18078.43412.493174.590540@cargo.ozlabs.ibm.com> Cc: linuxppc-dev@ozlabs.org, Johannes Berg List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Segher Boessenkool writes: > Should you really be testing VM_READ|VM_WRITE, or should it just > be VM_READ? We test VM_READ | VM_WRITE | VM_EXEC in the read case below, and that is because we have no HPTE encoding to say "writable but not readable" or "executable but not readable". Similarly we have no encoding to say "writable but not executable" on classic processors, so if you have just VM_WRITE set, you get a page that is readable, writable and executable. Paul.