Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp5347065img; Wed, 27 Mar 2019 06:56:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqyviPYgzwT/VyAC2MbON5KIdw4DwvI5e86JFg/5QLJ3dbPE8OjZKz0IEUQ09evA2/Rv9uT4 X-Received: by 2002:a62:12d0:: with SMTP id 77mr35671066pfs.15.1553695014951; Wed, 27 Mar 2019 06:56:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553695014; cv=none; d=google.com; s=arc-20160816; b=sFXIQ8xhmXsoCO4uh4wXILXDygd0KgP/we6ej/y/jnd/Dcs9PYofF2U+MlaHhBYxI1 rNJb4J+vTHvjofpz9HR/Gk53pgGLiJnbWopKHtUbUhf5S36bW/0wxr5ZRNdt++35WbuK r5QntuOh6NPgVU/XmrIQvbbhradER9luAHzNjyc8m5J/9CAK3I5Wyv/XCFXudYItb9UG N5lWQ337McWWPvjep5+QFKrwXqpbWkF2Di63T92Cc92Hg/fyExERbu3SPSOX/RN/dFuV rxtPGNGJLOI638uiKm7U/k2mBP3wpqKWQmUVVRnO0z1WtDrG/jCRP3SCGv+7tmJ9ZJy3 Wi9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=MxAp0ixoWdMFyaxnp72hlriLSBfNiJMWR8SCcq0gHTE=; b=eJ8zEZIlfsEOsJPaDmW4lHNZ/iFNcPg26FyZd3PN9O8b6tVla/KVXKDhbtOAQWHz90 ruRoQlF1+L86VCc+PaoVVPyTkOivEnYejWgFRRoGjPKq6FUN6FKgSX/W0goBFRW3IQF3 1g/lq+LN2XU2cOmyaCx+9ZcbM8o5BbZP2E15ZpXmZC39WyHVtbRv0TM0/VpVVLSsd1YG jwZSdYpBUUG46Xo9baI+QRBWQ/fm78SfwqfjL1m8RMT23qxeFbQjVC/fghUkNvhl5nr1 +jlKz7wmX7r6MfB0kwkuEJuvwoOzSDpJjYOAquDUh9SDrYGZvblcqayC8/ihbjqBCoG3 4JOQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id g64si18738353pfd.234.2019.03.27.06.56.39; Wed, 27 Mar 2019 06:56:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1728357AbfC0Nyk (ORCPT + 99 others); Wed, 27 Mar 2019 09:54:40 -0400 Received: from mga18.intel.com ([134.134.136.126]:27040 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726248AbfC0Nyk (ORCPT ); Wed, 27 Mar 2019 09:54:40 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Mar 2019 06:54:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,277,1549958400"; d="scan'208";a="145679114" Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.137]) by orsmga002.jf.intel.com with ESMTP; 27 Mar 2019 06:54:39 -0700 Received: by tassilo.localdomain (Postfix, from userid 1000) id 5C93E301327; Wed, 27 Mar 2019 06:54:39 -0700 (PDT) Date: Wed, 27 Mar 2019 06:54:39 -0700 From: Andi Kleen To: Jiri Olsa Cc: Andi Kleen , acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org Subject: Re: [PATCH 2/4] perf, tools: Implement duration_time as a proper event Message-ID: <20190327135439.GS18020@tassilo.jf.intel.com> References: <20190326221823.11518-1-andi@firstfloor.org> <20190326221823.11518-3-andi@firstfloor.org> <20190327085813.GB24156@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190327085813.GB24156@krava> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > so now that we have time in a separate event, we could > get rid of the isolated update_stats(&walltime_nsecs_stats) calls > and move them to perf_stat__update_shadow_stats? In theory yes, but it would require perf stat always setting up the duration_time event implicitely and then special handling. For stat it would need to be hidden to keep the same output. It's probably simpler to keep the old way for that. -Andi