From: Peter Zijlstra <peterz@infradead.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 2/6] mm: stack based kmap_atomic
Date: Tue, 24 Aug 2010 10:04:23 +0200 [thread overview]
Message-ID: <1282637063.2605.2333.camel@laptop> (raw)
In-Reply-To: <20100824163545.052e44fd.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 2010-08-24 at 16:35 +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 24 Aug 2010 16:24:27 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> > And Is it documented that kmap_atomic shouln't be used under NMI or something
> > special interrupts ?
> >
> Sorry, I missed something..Maybe not trouble.
In particular, we actually do use kmap_atomic from NMI context ;-)
It only relies on preempt_disable(), which for now is implied by
pagefault_disable(), if at some point those get split kmap_atomic will
need to do both (currently only PREEMPT_RT splits it, but then that has
a totally different kmap implementation too).
--
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 prev parent reply other threads:[~2010-08-24 8:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:13 [RFC][PATCH 0/6] mm, highmem: kmap_atomic rework Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-19 20:13 ` [RFC][PATCH 1/6] mm: strictly nested kmap_atomic Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-20 20:50 ` Rik van Riel
2010-08-20 20:50 ` Rik van Riel
2010-08-24 7:09 ` KAMEZAWA Hiroyuki
2010-08-24 7:09 ` KAMEZAWA Hiroyuki
2010-08-19 20:13 ` [RFC][PATCH 2/6] mm: stack based kmap_atomic Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-20 21:34 ` Rik van Riel
2010-08-20 21:34 ` Rik van Riel
2010-08-24 7:24 ` KAMEZAWA Hiroyuki
2010-08-24 7:24 ` KAMEZAWA Hiroyuki
2010-08-24 7:35 ` KAMEZAWA Hiroyuki
2010-08-24 8:04 ` Peter Zijlstra [this message]
2010-08-19 20:13 ` [RFC][PATCH 3/6] mm, frv: Out-of-line kmap-atomic Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-20 21:48 ` Rik van Riel
2010-08-20 21:48 ` Rik van Riel
2010-08-19 20:13 ` [RFC][PATCH 4/6] mm: Remove all KM_type arguments Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-20 21:44 ` Rik van Riel
2010-08-20 21:44 ` Rik van Riel
2010-08-19 20:13 ` [RFC][PATCH 5/6] mm: Fix up KM_type argument removal fallout Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-20 21:45 ` Rik van Riel
2010-08-20 21:45 ` Rik van Riel
2010-08-19 20:13 ` [RFC][PATCH 6/6] mm: Remove pte_*map_nested() Peter Zijlstra
2010-08-19 20:13 ` Peter Zijlstra
2010-08-20 21:47 ` Rik van Riel
2010-08-20 21:47 ` Rik van Riel
2010-08-19 21:31 ` [RFC][PATCH 0/6] mm, highmem: kmap_atomic rework Andrew Morton
2010-08-19 21:31 ` Andrew Morton
2010-08-20 14:38 ` Peter Zijlstra
2010-08-20 14:38 ` 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=1282637063.2605.2333.camel@laptop \
--to=peterz@infradead.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.