From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752671AbcHUDp7 (ORCPT ); Sat, 20 Aug 2016 23:45:59 -0400 Received: from smtprelay0249.hostedemail.com ([216.40.44.249]:34891 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751936AbcHUDp6 (ORCPT ); Sat, 20 Aug 2016 23:45:58 -0400 X-Session-Marker: 726F737465647440676F6F646D69732E6F7267 X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,rostedt@goodmis.org,:::::::::::::::::::::::::,RULES_HIT:41:152:355:379:421:599:800:960:973:988:989:1260:1261:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1777:1792:2393:2553:2559:2562:3138:3139:3140:3141:3142:3167:3353:3865:3866:3867:3868:3871:3872:3873:3874:5007:6742:7514:7652:7875:7903:8957:10004:10400:10848:11232:11473:11658:11914:12517:12519:12740:13069:13311:13357:13894:14096:14097:14181:14659:14721:14777:21080:30026:30054:30090:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: crook44_169ebc4ae462d X-Filterd-Recvd-Size: 2611 User-Agent: K-9 Mail for Android In-Reply-To: References: <94710CE6-857F-424A-9D50-8569D6282367@gmail.com> <072e2e64-2e9f-eb2b-eca2-00d8aa62974a@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: runaway latency detection From: Steven Rostedt Date: Sat, 20 Aug 2016 23:45:53 -0400 To: Tracy Smith , Nikolay Borisov CC: Sebastian Andrzej Siewior , Clark Williams , Thomas Gleixner , Carsten Emde , Daniel Bristot de Oliveira , linux-kernel@vger.kernel.org, Andrew Morton , Jon Masters , Daniel Wagner , Ingo Molnar , Peter Zijlstra Message-ID: <38EC0AD0-E266-41CD-B10D-34629918803E@goodmis.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On August 20, 2016 3:04:43 PM EDT, Tracy Smith >Using ftace it is difficult to catch the latency since it can occur at >any >point during the cyclictest. It is an uncomfortable level of >indeterminism >without knowing the cause. > >Is there a way to trace random latency jumps on a single core using >trace, >or any other suggestion to isolate it? I know the functions and tasks >running on the core using ftrace, but can't catch the random latency >jumps. Have you tried using the -b option of cyclictest? It stops the tracing when it detects a latency. It shows what happened up to that point. I can discuss more about what to do later but I'll be traveling to LinuxCon tomorrow. -- Steve > >Thx, Tracy >On Aug 20, 2016 12:54 PM, "Nikolay Borisov" >wrote: > >> >> >> On 20.08.2016 20:03, T. Smith wrote: >> > The goal is to isolate causes of indeterminism when using the >PREEMPT_RT >> kernel configuration with full preemption and to characterize latency >and >> jitter using ftrace, any recommendations? >> >> What hardware is it ? If it's x86 it's entirely possible you are >seeing >> SMI. Perhaps you should look into disabling those if you are on x86? >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.