From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752829AbbFHQyj (ORCPT ); Mon, 8 Jun 2015 12:54:39 -0400 Received: from smtprelay0086.hostedemail.com ([216.40.44.86]:55501 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751278AbbFHQya (ORCPT ); Mon, 8 Jun 2015 12:54:30 -0400 X-Session-Marker: 726F737465647440676F6F646D69732E6F7267 X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,rostedt@goodmis.org,:::::::::::,RULES_HIT:41:355:379:541:599:800:960:973:988:989:1260:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1534:1538:1568:1593:1594:1711:1714:1730:1747:1777:1792:2393:2553:2559:2562:3138:3139:3140:3141:3142:3622:3865:3866:3867:3868:3871:5007:6120:6261:7875:8660:10004:10400:10848:10967:11026:11232:11658:11914:12517:12519:12740:13069:13148:13230:13311:13357:21080,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 X-HE-Tag: brain12_442e17e439f2b X-Filterd-Recvd-Size: 1595 Date: Mon, 8 Jun 2015 12:54:26 -0400 From: Steven Rostedt To: Peter Zijlstra Cc: Thomas Gleixner , Mathieu Desnoyers , linux-kernel@vger.kernel.org, Ingo Molnar , Francis Giraldeau Subject: Re: [RFC PATCH] sched: Fix sched_wakeup tracepoint Message-ID: <20150608125426.1fb4920f@gandalf.local.home> In-Reply-To: <1433508406.1495.11.camel@twins> References: <1433504509-17013-1-git-send-email-mathieu.desnoyers@efficios.com> <20150605120909.GG19282@twins.programming.kicks-ass.net> <1433508406.1495.11.camel@twins> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 05 Jun 2015 14:46:46 +0200 Peter Zijlstra wrote: > to the time between wakeup and sched switch. > > My point exactly, wake->schedule is what we call the scheduling latency, > not the wake latency, which would be from 'event' to the task being > runnable. Right, which means the tracepoint should be as close to the "wakeup_process()" or whatever calls try_to_wake_up(). Which would be the "sched_waking" part of your proposal. -- Steve