Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3186062ybz; Sun, 19 Apr 2020 20:09:15 -0700 (PDT) X-Google-Smtp-Source: APiQypJWIraLC1PGkSaF1KtdN9khH/MYj/XohbiT1FGCXpgeelJmd4hU4fwHZBp7YFB8yoeYbED7 X-Received: by 2002:a50:c25a:: with SMTP id t26mr12230887edf.20.1587352154847; Sun, 19 Apr 2020 20:09:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587352154; cv=none; d=google.com; s=arc-20160816; b=GhzjE09Juh9oqKLad+IFtSjW7iNxJStF3weojeo7BqoolBitTeGdPpBOQW4ILtxfIz GeX6UA2KnLmNGUH3shDGjqduIg9oVqDR0Jle5wrWAEbb7fBqYvTg1/MGBUFPdzfgkHES D1r4xJzYW050VaeWwHTHMyHCXdNMK6WIuVWT6yY3nGCV0G3zK9bbSi7JgpcH6QOikCMi x2wiDv1rqfyYywyB7FnN7k/bZI5jJ+f9MCGIKUtR0Esgqod5b3A2X6QVon48Orqk5CxI vhwbTbGEmGKxBu3ChoR8BCMCB10IdmbBR4hJyQSjgQryyTBH2jSNDLKz2VnAuJRS1TeD 2dhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :ironport-sdr:ironport-sdr; bh=Y0PHoUs4Hj1MLBR4NtLIK0KRgO3wfctJ5ih4fY1HoxY=; b=OkOk0d331XtZzR1USKU3OV0cfkU52UwlltIQOcJztjXiZtNk6AHPUf9WRDx0cCsIVR VvfL3mZBLMQU13SR4xjzWt8Z+NuC4DYPH6+23bRL67DEC8LojkLbKq+AycmoR0PqOucS iRkxMxgeqWVpvCj7owmq0jTVuKmYAzkYjr4U5tyJej51it8mga/tFHjhnxoojZ5PDjGa p+AQ9cmqB1Y9RZQoChl3ef7TJ3stwe2XSVh7u56j+ZeGeTadNIWxQWbwoEw/46pZugwn DjvX5j2CSFEIK4a6XsXESuomR0uqy9AkVH0ctJXHOkC2janwsDxp4gXNGYtt5vpkGXaU JlIg== 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 r21si12883442eju.300.2020.04.19.20.08.47; Sun, 19 Apr 2020 20:09:14 -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 S1726141AbgDTDE6 (ORCPT + 99 others); Sun, 19 Apr 2020 23:04:58 -0400 Received: from mga09.intel.com ([134.134.136.24]:37199 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725896AbgDTDE6 (ORCPT ); Sun, 19 Apr 2020 23:04:58 -0400 IronPort-SDR: cKOUMm93oephk6d/KizPVf8oz3V3p3NatxHjUjTIGJqkNK5DhyJbl+DA51B8Itek0Tw5OaMqrX wZG5wbAJ45CA== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Apr 2020 20:04:57 -0700 IronPort-SDR: 0aKYO64MEi9ETNwxvLiKShf2uVoHsv6E1K5LcORKxl04J2uhq5k9dxV7H9TweCAp+1CCK8OVXd y7oCQREJNISg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.72,405,1580803200"; d="scan'208";a="258201028" Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.21]) by orsmga006.jf.intel.com with ESMTP; 19 Apr 2020 20:04:57 -0700 Received: by tassilo.localdomain (Postfix, from userid 1000) id 452223019B6; Sun, 19 Apr 2020 20:04:57 -0700 (PDT) Date: Sun, 19 Apr 2020 20:04:57 -0700 From: Andi Kleen To: Arnaldo Carvalho de Melo Cc: Adrian Hunter , Jiri Olsa , linux-kernel@vger.kernel.org, Namhyung Kim , linux-perf-users@vger.kernel.org Subject: Re: [PATCH 11/16] perf intel-pt: Add support for synthesizing callchains for regular events Message-ID: <20200420030457.GA608746@tassilo.jf.intel.com> References: <20200401101613.6201-1-adrian.hunter@intel.com> <20200401101613.6201-12-adrian.hunter@intel.com> <20200416151443.GA2650@kernel.org> <5b8f28f5-968f-bfff-68af-ed0350a90765@intel.com> <20200417213704.GB21512@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200417213704.GB21512@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Andi? My concern is that if this is the optimal solution for a good > subset of the machines out there, then we need to make it easy to use, > even transparent, if possible and safe to take that path. I'm not sure it's that great in the general case. A PT call graph would need a full PT recording from start to end. The problem with full PT recording is that it doesn't really work for a lot of workloads, because for anything doing enough computation the CPU just generates too much data and you end up with a lot of gaps in the trace when the perf record flushing cannot keep up. Also even if it worked you might end up with far too much data that will take a long time to process. So I suspect it wouldn't work often enough to be generally useful. For the leader sample case we just want to use some non PT method to get the call graph. -Andi