[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1507031654180.3916@nanos>
Date: Fri, 3 Jul 2015 16:54:49 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Sudeep Holla <sudeep.holla@....com>
cc: Wolfram Sang <wsa@...-dreams.de>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Kevin Hilman <khilman@...nel.org>,
Magnus Damm <magnus.damm@...il.com>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
Tyler Baker <tyler.baker@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Simon Horman <horms@...ge.net.au>,
Borislav Petkov <bp@...en8.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock
from event handler"
On Fri, 3 Jul 2015, Sudeep Holla wrote:
> On 03/07/15 15:37, Wolfram Sang wrote:
> >
> > > So this is a single core machine and uses the em_sti timer w/o the
> > > broadcast nonsense. In Simons case it looks like em_sti is used as
> > > broadcast device.
> >
> > We use the same board. Just my kernel has SMP=n.
> >
>
> If it's UP build, then GENERIC_CLOCKEVENTS_BROADCAST is disabled. You
> may be hitting the issue I reported[1] and is still under discussion.
Nope. The UP version uses a non affected timer.
Thanks,
tglx
--
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