Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754482AbZAZTLZ (ORCPT ); Mon, 26 Jan 2009 14:11:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754063AbZAZTLH (ORCPT ); Mon, 26 Jan 2009 14:11:07 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:35832 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753998AbZAZTLF (ORCPT ); Mon, 26 Jan 2009 14:11:05 -0500 Date: Mon, 26 Jan 2009 11:09:59 -0800 (PST) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Andrew Morton cc: Nick Piggin , mingo@elte.hu, linux-arch@vger.kernel.org, rusty@rustcorp.com.au, travis@sgi.com, linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com, suresh.b.siddha@intel.com, arjan@infradead.org, hpa@zytor.com, tglx@linutronix.de Subject: Re: [git pull] cpus4096 tree, part 3 In-Reply-To: <20090126110054.bdddbf38.akpm@linux-foundation.org> Message-ID: References: <20090102203839.GA26850@elte.hu> <20090103193859.GB9805@elte.hu> <20090103203621.GA2491@elte.hu> <20090103213856.GA24138@elte.hu> <20090103223723.GA17047@elte.hu> <20090105011416.GG32239@wotan.suse.de> <20090105011630.GI32239@wotan.suse.de> <20090126110054.bdddbf38.akpm@linux-foundation.org> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1067 Lines: 32 On Mon, 26 Jan 2009, Andrew Morton wrote: > > + write = error_code & PF_WRITE; > > What's going on here? We set `error_code' to PF_WRITE, which is some > x86-specific thing. No. We set "write" to non-zero if it was a write fault. > > fault = handle_mm_fault(mm, vma, address, write); > > and then pass it into handle_mm_fault(), which is expecting a bunch of > flags in the FAULT_FLAG_foo domain. No. "handle_mm_fault()" takes an integer that is non-zero if it's a write, zero if it's a read. That's how it has _always_ worked. I don't see where you find that FAULT_FLAG_foo thing. That's much deeper down, when people do things like unsigned int flags = FAULT_FLAG_NONLINEAR | (write_access ? FAULT_FLAG_WRITE : 0); based on that whole "write_access" flag. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/