summaryrefslogtreecommitdiffstats
path: root/arch/s390/kernel/Makefile
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2011-08-24 15:32:31 +0200
committerMichal Simek <monstr@monstr.eu>2011-10-14 12:28:42 +0200
commit84ac218f0257a0cfd7689d9a44f53118dbf307b3 (patch)
tree015d3fc9489fbb00da12dbf4eee72752f3307b9e /arch/s390/kernel/Makefile
parentcb5edfe3e553d930f9a13cb75cfe395ee38cde23 (diff)
downloadblackbird-op-linux-84ac218f0257a0cfd7689d9a44f53118dbf307b3.tar.gz
blackbird-op-linux-84ac218f0257a0cfd7689d9a44f53118dbf307b3.zip
microblaze: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW usage
As far as I can tell the only reason microblaze has __ARCH_WANT_INTERRUPTS_ON_CTXSW is because it initializes new task state with interrupts enabled so that on switch_to() interrupts get enabled. So change copy_thread() to clear MSR_IE instead of set it, this will ensure switch_to() will always keep IRQs disabled. The scheduler will disable IRQs when taking rq->lock in schedule() and enable IRQs in finish_lock_switch() after its done its magic. This leaves ARM the only __ARCH_WANT_INTERRUPTS_ON_CTXSW user. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Michal Simek <monstr@monstr.eu>
Diffstat (limited to 'arch/s390/kernel/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud