From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> To: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>, Russell King <rmk@arm.linux.org.uk>, David Howells <dhowells@redhat.com>, Ralf Baechle <ralf@linux-mips.org>, David Miller <davem@davemloft.net>, Paul Mackerras <paulus@samba.org>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Hugh Dickins <hughd@google.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org Subject: Re: [RFC][PATCH 2/6] mm: stack based kmap_atomic Date: Tue, 24 Aug 2010 16:24:27 +0900 [thread overview] Message-ID: <20100824162427.58e2eb88.kamezawa.hiroyu@jp.fujitsu.com> (raw) In-Reply-To: <20100819202753.656285068@chello.nl> On Thu, 19 Aug 2010 22:13:19 +0200 Peter Zijlstra <a.p.zijlstra@chello.nl> wrote: > Keep the current interface but ignore the KM_type and use a stack > based approach. > > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> > --- > +DECLARE_PER_CPU(int, __kmap_atomic_idx); > + > +static inline int kmap_atomic_idx_push(void) > +{ > + int idx = __get_cpu_var(__kmap_atomic_idx)++; > +#ifdef CONFIG_DEBUG_HIGHMEM > + BUG_ON(idx > KM_TYPE_NR); > +#endif > + return idx; > +} > + > +static inline int kmap_atomic_idx_pop(void) > +{ > + int idx = --__get_cpu_var(__kmap_atomic_idx); > +#ifdef CONFIG_DEBUG_HIGHMEM > + BUG_ON(idx < 0); > +#endif > + return idx; > +} > + > #else /* CONFIG_HIGHMEM */ > I may don't understand anything... Is irq already disabled ? And Is it documented that kmap_atomic shouln't be used under NMI or something special interrupts ? Thanks, -Kame
WARNING: multiple messages have this Message-ID (diff)
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> To: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>, Russell King <rmk@arm.linux.org.uk>, David Howells <dhowells@redhat.com>, Ralf Baechle <ralf@linux-mips.org>, David Miller <davem@davemloft.net>, Paul Mackerras <paulus@samba.org>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Hugh Dickins <hughd@google.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org Subject: Re: [RFC][PATCH 2/6] mm: stack based kmap_atomic Date: Tue, 24 Aug 2010 16:24:27 +0900 [thread overview] Message-ID: <20100824162427.58e2eb88.kamezawa.hiroyu@jp.fujitsu.com> (raw) In-Reply-To: <20100819202753.656285068@chello.nl> On Thu, 19 Aug 2010 22:13:19 +0200 Peter Zijlstra <a.p.zijlstra@chello.nl> wrote: > Keep the current interface but ignore the KM_type and use a stack > based approach. > > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> > --- > +DECLARE_PER_CPU(int, __kmap_atomic_idx); > + > +static inline int kmap_atomic_idx_push(void) > +{ > + int idx = __get_cpu_var(__kmap_atomic_idx)++; > +#ifdef CONFIG_DEBUG_HIGHMEM > + BUG_ON(idx > KM_TYPE_NR); > +#endif > + return idx; > +} > + > +static inline int kmap_atomic_idx_pop(void) > +{ > + int idx = --__get_cpu_var(__kmap_atomic_idx); > +#ifdef CONFIG_DEBUG_HIGHMEM > + BUG_ON(idx < 0); > +#endif > + return idx; > +} > + > #else /* CONFIG_HIGHMEM */ > I may don't understand anything... Is irq already disabled ? And Is it documented that kmap_atomic shouln't be used under NMI or something special interrupts ? Thanks, -Kame -- 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 7:29 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 [this message] 2010-08-24 7:24 ` KAMEZAWA Hiroyuki 2010-08-24 7:35 ` KAMEZAWA Hiroyuki 2010-08-24 8:04 ` Peter Zijlstra 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=20100824162427.58e2eb88.kamezawa.hiroyu@jp.fujitsu.com \ --to=kamezawa.hiroyu@jp.fujitsu.com \ --cc=a.p.zijlstra@chello.nl \ --cc=akpm@linux-foundation.org \ --cc=benh@kernel.crashing.org \ --cc=davem@davemloft.net \ --cc=dhowells@redhat.com \ --cc=hpa@zytor.com \ --cc=hughd@google.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mingo@elte.hu \ --cc=paulus@samba.org \ --cc=ralf@linux-mips.org \ --cc=rmk@arm.linux.org.uk \ --cc=tglx@linutronix.de \ --cc=torvalds@linux-foundation.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: linkBe 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.