From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <npiggin@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-arch@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/3] on do_page_fault() and *copy*_inatomic
Date: Wed, 01 Nov 2006 12:44:35 +0100 [thread overview]
Message-ID: <20061101114435.234474405@chello.nl> (raw)
In light of the recent work on fault handlers and generic_file_buffered_write()
I've gone over some of the arch specific stuff that supports this work.
The following three patches are ready for inclusion IMHO, please apply.
The first patch fixes up some arch fault handlers to respect the
'take no locks in atomic context' rule; this also fixes CONFIG_PREEMPT bugs
on those platforms.
The second patch introduces pagefault_{disable,enable}() - an abtraction that
replaces the now open coded {inc,dec}_preempt_count() calls when we mean to
create atomic pagefault scope. The added barrier() calls in the new
primitives might fix some CONFIG_PREEMPT bugs.
The third patch make k{,un}map_atomic denote an atomic pagefault scope. All
non-trivial implementation already do this, and this allows us to rely on that
in generic. This might also fix some bugs where people already assumed this.
Peter
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2006-11-01 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 11:44 Peter Zijlstra [this message]
2006-11-01 11:44 ` [PATCH 1/3] mm: arch do_page_fault() vs in_atomic() Peter Zijlstra
2006-11-01 11:44 ` [PATCH 2/3] mm: pagefault_{disable,enable}() Peter Zijlstra
2006-11-01 11:44 ` [PATCH 3/3] mm: k{,um}map_atomic() vs in_atomic() Peter Zijlstra
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=20061101114435.234474405@chello.nl \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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