[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5596A015.1030709@arm.com>
Date: Fri, 03 Jul 2015 15:45:41 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Wolfram Sang <wsa@...-dreams.de>,
Thomas Gleixner <tglx@...utronix.de>
CC: Sudeep Holla <sudeep.holla@....com>,
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 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.
Regards,
Sudeep
[1] https://lkml.org/lkml/2015/6/25/271
--
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