From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 03 Jul 2015 15:45:41 +0100 [thread overview]
Message-ID: <5596A015.1030709@arm.com> (raw)
In-Reply-To: <20150703143703.GB19284@katana>
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
next prev parent reply other threads:[~2015-07-03 14:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 2:40 Possible regression due to "tick: broadcast: Prevent livelock from event handler" Simon Horman
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:32 ` Wolfram Sang
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:45 ` Sudeep Holla [this message]
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 15:09 ` Wolfram Sang
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 16:00 ` Wolfram Sang
2015-07-06 4:42 ` Magnus Damm
2015-07-29 2:23 ` Simon Horman
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-06 4:45 ` Magnus Damm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5596A015.1030709@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).