[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150507111231.GF23123@twins.programming.kicks-ass.net>
Date: Thu, 7 May 2015 13:12:31 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: David Hildenbrand <dahi@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...hat.com,
yang.shi@...driver.com, bigeasy@...utronix.de,
benh@...nel.crashing.org, paulus@...ba.org,
akpm@...ux-foundation.org, heiko.carstens@...ibm.com,
schwidefsky@...ibm.com, borntraeger@...ibm.com, mst@...hat.com,
tglx@...utronix.de, David.Laight@...LAB.COM, hughd@...gle.com,
hocko@...e.cz, ralf@...ux-mips.org, herbert@...dor.apana.org.au,
linux@....linux.org.uk, airlied@...ux.ie, daniel.vetter@...el.com,
linux-mm@...ck.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH RFC 01/15] uaccess: count pagefault_disable() levels in
pagefault_disabled
On Thu, May 07, 2015 at 12:50:53PM +0200, David Hildenbrand wrote:
> Just to make sure we have a common understanding (as written in my cover
> letter):
>
> Your suggestion won't work with !CONFIG_PREEMPT (!CONFIG_PREEMPT_COUNT). If
> there is no preempt counter, in_atomic() won't work.
But there is, we _always_ have a preempt_count, and irq_enter() et al.
_always_ increment the relevant bits.
The thread_info::preempt_count field it never under PREEMPT_COUNT
include/asm-generic/preempt.h provides stuff regardless of
PREEMPT_COUNT.
See how __irq_enter() -> preempt_count_add(HARDIRQ_OFFSET) ->
__preempt_count_add() _always_ just works.
Its only things like preempt_disable() / preempt_enable() that get
munged depending on PREEMPT_COUNT/PREEMPT.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists