From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vineet.Gupta1@synopsys.com (Vineet Gupta) Date: Tue, 17 Nov 2015 18:07:08 +0530 Subject: [PATCH v2 18/19] ARC: [plat-eznps] replace sync with proper cpu barrier In-Reply-To: <20151117122208.GX3816@twins.programming.kicks-ass.net> References: <1446297327-16298-1-git-send-email-noamc@ezchip.com> <1446893557-29748-19-git-send-email-noamc@ezchip.com> <564B0BB1.8080709@synopsys.com> <20151117112343.GW3816@twins.programming.kicks-ass.net> <564B1182.7050107@synopsys.com> <20151117122208.GX3816@twins.programming.kicks-ass.net> List-ID: Message-ID: <564B1F74.6090709@synopsys.com> To: linux-snps-arc@lists.infradead.org On Tuesday 17 November 2015 05:52 PM, Peter Zijlstra wrote: >> > BTW since we are on the topic we have this loop in stack unwinder which can >> > potentially cause RCU stalls, actual lockups etc. I was planning to add the >> > following - does that seem fine to you. > Worries me more than anything. How could you get stuck in there? No we not getting stuck in there - but this has potential to - if say unwind info were corrupt (not seen that ever though). The old code won't even respond to say a Ctrl+C if it were stuck ! Plus the reschedule there will keeps sched happy when say unraveling deep stack frames with perf ?