[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1306413454.1200.92.camel@twins>
Date: Thu, 26 May 2011 14:37:34 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Ingo Molnar <mingo@...e.hu>, Marc Zyngier <Marc.Zyngier@....com>,
Frank Rowand <frank.rowand@...sony.com>,
Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org,
Yong Zhang <yong.zhang0@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [BUG] "sched: Remove rq->lock from the first half of ttwu()"
locks up on ARM
On Thu, 2011-05-26 at 13:31 +0100, Russell King - ARM Linux wrote:
> On Thu, May 26, 2011 at 02:26:23PM +0200, Ingo Molnar wrote:
> >
> > * Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > > Sort this by reverting to the old behaviour for this situation and
> > > perform a full remote wake-up.
> >
> > Btw., ARM should consider switching most of its subarchitectures to
> > !__ARCH_WANT_INTERRUPTS_ON_CTXSW - enabling irqs during context
> > switches is silly and now expensive as well.
>
> Not going to happen. The reason we do it is because most of the CPUs
> have to (slowly) flush their caches during switch_mm(), and to have
> IRQs off over the cache flush means that we lose IRQs.
>
> So it's not silly at all, bit a technical requirement imposed by the
> cache architecture.
>
> If it's become expensive through development, it suggests that the
> development did not take account of the issues we have on ARM.
Its not more expensive than it was before this patch series, and the
case in question is relatively rare (guesstimate, lacking measurements)
so ARM should benefit from most of the optimization provided.
--
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