summaryrefslogtreecommitdiffstats
path: root/arch/x86/mm
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2009-04-10 08:43:11 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2009-06-21 13:06:05 -0700
commit30c9f3a9fae79517bca595826a19c6855fbb6d32 (patch)
treef7eb9588fe38dc1b045e97409e25c57c516aaf44 /arch/x86/mm
parent232086b19964d0e13359d30d74b11ca31b0751cb (diff)
downloadlinux-30c9f3a9fae79517bca595826a19c6855fbb6d32.tar.gz
linux-30c9f3a9fae79517bca595826a19c6855fbb6d32.tar.bz2
linux-30c9f3a9fae79517bca595826a19c6855fbb6d32.zip
Remove internal use of 'write_access' in mm/memory.c
The fault handling routines really want more fine-grained flags than a single "was it a write fault" boolean - the callers will want to set flags like "you can return a retry error" etc. And that's actually how the VM works internally, but right now the top-level fault handling functions in mm/memory.c all pass just the 'write_access' boolean around. This switches them over to pass around the FAULT_FLAG_xyzzy 'flags' variable instead. The 'write_access' calling convention still exists for the exported 'handle_mm_fault()' function, but that is next. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/x86/mm')
0 files changed, 0 insertions, 0 deletions