Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp221079ybt; Mon, 6 Jul 2020 07:49:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwio1Fz1tRW9r+i46eECIhyCjea2YEA50ZH8kiQrIRZxtQizjrZzkLj8/pJPTWkQP5yTjK8 X-Received: by 2002:a17:906:31c8:: with SMTP id f8mr31882059ejf.269.1594046949808; Mon, 06 Jul 2020 07:49:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594046949; cv=none; d=google.com; s=arc-20160816; b=f4seaq9XkMLiwzt+by3qnLRmc9lfTutl3ziUZ7vMPJ4kVhY/ijk85qPTVWvOp/lfom vO5fAit1ULljBKmjRJpUr66wt5OIOtTwey+xGTpgSKaiQh5qVFW4Yi/0Zj6L6h7hTJRF OqEjbvVKvY20j/nTZZA5xf8bO08UnRGaNxHncYbcA9zsuVWxHbPThX1AU+OTZ5aMOEon T7Fxz2gsLI9EcbvNKA9jeV7S0nn+jIy+5cqWIwkpwNe/HvN/sjEZ7Zzf8I1C6Y8MYeTR q8MNL/xupIsIDyADBjgPKfZPx5XlenrjtarYFUMC5RB6/0wtqHrtG2xXy0FbBN75pfTg vDbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject:ironport-sdr :ironport-sdr; bh=IDALBQ/Hc2XepozrDB56scJJXivCtSt/R2iQgGZ9svw=; b=eb6Nx8MldYzuNxA4NUnXD9Wd6JLEZGCRlyF4o/3M352nvAiOZ7FAXDRdC/iXBA0T+K y+GaVPoflNcr3s5+O8+F0PfWOaBGw8VJBu3zATdnrWhCmwb+C8Hu6gJhVPITBbUojRd7 nWss2T9cIXR4AG+aqVJS7P1Otm6/IRyt1EAbpbPn84j3KRBGIx6ixcGu6Aka1udqQrzW 63MRGLHyeScWbz8ZdJjA/b7ZgjKm8G1/1uJBjoiUU+TaE6swVtbiCHwUdRNkGeH8nSOI GO5loIwZgn032CgJowqNXrLzP/g7cJNN5MYeYC1QdI/S9u4kV+a1kED0sEYQoOjVnYdQ ty8A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bi11si14611655edb.544.2020.07.06.07.48.46; Mon, 06 Jul 2020 07:49:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729321AbgGFOsA (ORCPT + 99 others); Mon, 6 Jul 2020 10:48:00 -0400 Received: from mga09.intel.com ([134.134.136.24]:4606 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729250AbgGFOr7 (ORCPT ); Mon, 6 Jul 2020 10:47:59 -0400 IronPort-SDR: LMOL+JlZqj77Lo4xMAQXzRb3P9kI0kv45o612uskvu/xI31adPSSGAVlwkLIw/5LlXF5ZH8GTB zlgxkzNqqBOg== X-IronPort-AV: E=McAfee;i="6000,8403,9673"; a="148921754" X-IronPort-AV: E=Sophos;i="5.75,320,1589266800"; d="scan'208";a="148921754" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jul 2020 07:47:58 -0700 IronPort-SDR: D2/jICv74KPRVjee/UF8HIK3f8Qrtv2itFmRCdKw+8eqdtAp51ByYkWVIY9jma+GVbo2PCtba/ 7zBmbWZvjnCg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,320,1589266800"; d="scan'208";a="322396539" Received: from linux.intel.com ([10.54.29.200]) by FMSMGA003.fm.intel.com with ESMTP; 06 Jul 2020 07:47:57 -0700 Received: from [10.249.225.12] (abudanko-mobl.ccr.corp.intel.com [10.249.225.12]) by linux.intel.com (Postfix) with ESMTP id 80D45580378; Mon, 6 Jul 2020 07:47:55 -0700 (PDT) Subject: Re: [PATCH v9 11/15] perf stat: implement control commands handling To: Jiri Olsa Cc: Arnaldo Carvalho de Melo , Namhyung Kim , Alexander Shishkin , Peter Zijlstra , Ingo Molnar , Andi Kleen , linux-kernel References: <21669f5a-6220-df0a-09f1-b73b32487f23@linux.intel.com> <20200706123436.GD3401866@krava> From: Alexey Budankov Organization: Intel Corp. Message-ID: <6cf91811-ea6a-3c7c-8bbf-7f96bfa1fc82@linux.intel.com> Date: Mon, 6 Jul 2020 17:47:54 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200706123436.GD3401866@krava> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06.07.2020 15:34, Jiri Olsa wrote: > On Fri, Jul 03, 2020 at 10:47:22AM +0300, Alexey Budankov wrote: >> >> Implement handling of 'enable' and 'disable' control commands >> coming from control file descriptor. process_evlist() function >> checks for events on control fds and makes required operations. >> If poll event splits initiated timeout interval then the reminder >> is calculated and still waited in the following poll() syscall. >> >> Signed-off-by: Alexey Budankov >> --- >> tools/perf/builtin-stat.c | 75 ++++++++++++++++++++++++++++----------- >> 1 file changed, 55 insertions(+), 20 deletions(-) >> >> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c >> index 9e4288ecf2b8..5021f7286422 100644 >> --- a/tools/perf/builtin-stat.c >> +++ b/tools/perf/builtin-stat.c >> @@ -485,6 +485,31 @@ static bool handle_interval(unsigned int interval, int *times) >> return false; >> } >> >> +static bool process_evlist(struct evlist *evlist, unsigned int interval, int *times) >> +{ >> + bool stop = false; >> + enum evlist_ctl_cmd cmd = EVLIST_CTL_CMD_UNSUPPORTED; >> + >> + if (evlist__ctlfd_process(evlist, &cmd) > 0) { >> + switch (cmd) { >> + case EVLIST_CTL_CMD_ENABLE: >> + pr_info(EVLIST_ENABLED_MSG); >> + stop = handle_interval(interval, times); >> + break; >> + case EVLIST_CTL_CMD_DISABLE: >> + stop = handle_interval(interval, times); > > I still don't understand why you call handle_interval in here > > I don't see it being necessary.. you enable events and handle_interval, > wil be called in the next iteration of dispatch_events, why complicate > this function with that? Printing event counts at the moment of command processing lets scripts built on top of stat output to provide more plain and accurate metrics. Otherwise it may get spikes in the beginning of the next time interval because not all counts lay inside [Events enabled, Events disable] If -I interval is large tail event count can be also large. Compare the output below with the output in the cover letter. Either way is possible but the latter one likely complicates the scripts I mentioned above. perf=tools/perf/perf ${perf} stat -D -1 -e cpu-cycles -a -I 1000 \ --control fd:${ctl_fd},${ctl_fd_ack} \ -- sleep 40 & Events disabled # time counts unit events 1.001100723 cpu-cycles 2.003146566 cpu-cycles 3.005073317 cpu-cycles 4.006337062 cpu-cycles Events enabled enable acked(ack) 5.011182000 54,128,692 cpu-cycles <=== 6.012300167 3,648,804,827 cpu-cycles 7.013631689 590,438,536 cpu-cycles 8.015558583 406,935,663 cpu-cycles 9.017455505 407,806,862 cpu-cycles 10.019300780 399,351,824 cpu-cycles 11.021180025 404,584,417 cpu-cycles 12.023033661 537,787,981 cpu-cycles 13.024422354 699,395,364 cpu-cycles 14.026325749 397,871,324 cpu-cycles disable acked() Events disabled 15.027857981 396,956,159 cpu-cycles <=== 16.029279264 cpu-cycles 17.031131311 cpu-cycles 18.033010580 cpu-cycles 19.034918883 cpu-cycles enable acked(ack) Events enabled 20.036758793 183,544,975 cpu-cycles <=== 21.038163289 419,054,544 cpu-cycles 22.040108245 413,993,309 cpu-cycles 23.042042365 403,584,493 cpu-cycles 24.043985381 416,512,094 cpu-cycles 25.045925682 401,513,429 cpu-cycles # time counts unit events 26.047822238 461,205,096 cpu-cycles 27.049784263 414,319,162 cpu-cycles 28.051745360 403,706,915 cpu-cycles 29.053674600 416,502,883 cpu-cycles disable acked() Events disabled 30.054750685 414,184,409 cpu-cycles <=== Alexey > > thanks, > jirka >