Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp4134775ybv; Mon, 10 Feb 2020 13:04:54 -0800 (PST) X-Google-Smtp-Source: APXvYqwtxS+T17gXudU/XfZfiEYxQRvpb9iIOWI06EQGl0zVczre6FFKvrthKagab+NRy7O87ERx X-Received: by 2002:a9d:6f0a:: with SMTP id n10mr2695829otq.54.1581368694422; Mon, 10 Feb 2020 13:04:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581368694; cv=none; d=google.com; s=arc-20160816; b=mASUuNC9zyss9AmvgeeHWvji67T94oQei/RJnCrEA/g582bS4IoQ/TrzB8HOutkxyU Lxncl7Na+azjTeR8zSUdf7SRLTJTq/ULZJnMIvVL6K6WosgNFC0DMXVr9nX98MfGk4P9 ogrd4dPws18oF9C6aTgEkDgoB2Kv68mUJzwp6N0IC33wQ8lDphXLqTk86M94p1noWeTx bEBpQu50LJKUd9UJeNg9CtaqpCiuJTO1wOEKtJfE8jJllKdWH5TwHdtS/TkjH0bwyPYU iDB6ECG5pqHDfW4EWBbfe48Dbdvmdg0+BRbgah6VucRGeWyyC4t9bUtbzKBRkA3D1Wns ddCA== 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 :dkim-signature; bh=wQ+2dKU8yIsABCyjypziP41Gbgfmk467AaFM3bLT4b0=; b=Kjm3CAjABwUrqqRkJ2OjlNpKOoIkDW2K9loksIGKqLgoW1HITrF+7rzx4MDDzHU/9S j725j+/VEelPCA93wFcXG68h8z0HTSlL7FLIv2HLUKVvh8Y25ve2MGnY4eQI3EjALNcX 74rGZIn60s+2ct/Hysu1GnB9zb7iwreca48S20XVT3YsHpPM3CicuXmQMzDYqLnD2A4e BHHDtT7MfHJR/ghH30qO4bU8yi1oGVQyiYVKAL+LDwBq/6UlEUl8c7YZea88q17CdP/d bcZEbiuGJjMSBuaovk8xtXz9LavZWPtHP3qIhSC5fNczcGun6HgEWFGK71EdFkFRma5/ oUEg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=H+xr67T0; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 24si640240oip.248.2020.02.10.13.04.41; Mon, 10 Feb 2020 13:04:54 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=H+xr67T0; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727254AbgBJVEa (ORCPT + 99 others); Mon, 10 Feb 2020 16:04:30 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:43158 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726563AbgBJVEa (ORCPT ); Mon, 10 Feb 2020 16:04:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581368668; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wQ+2dKU8yIsABCyjypziP41Gbgfmk467AaFM3bLT4b0=; b=H+xr67T0f5HRzQod68WHV60Q5OMEuEuoXrZkGl16L0RB2q4nKAyY80MZ+D8vawbiuZoIoI wxDIP55Meyx91bskUqCggIUvre8BVRQR5nFTci4rLFnTpBq6TE3Gr/bwT5tlHdecLZMez5 yXd+GRHtF3k0+kkkpwe40GSA+DUMvFA= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-125-1ouHzz-oMR-os2cMib18hA-1; Mon, 10 Feb 2020 16:04:26 -0500 X-MC-Unique: 1ouHzz-oMR-os2cMib18hA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E75368017CC; Mon, 10 Feb 2020 21:04:24 +0000 (UTC) Received: from krava (ovpn-204-37.brq.redhat.com [10.40.204.37]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8FCC219C70; Mon, 10 Feb 2020 21:04:22 +0000 (UTC) Date: Mon, 10 Feb 2020 22:04:19 +0100 From: Jiri Olsa To: Andi Kleen Cc: "Jin, Yao" , acme@kernel.org, jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org, kan.liang@intel.com, yao.jin@intel.com Subject: Re: [PATCH] perf stat: Show percore counts in per CPU output Message-ID: <20200210210419.GD36715@krava> References: <20200206015613.527-1-yao.jin@linux.intel.com> <20200210132804.GA9922@krava> <20200210140120.GD9922@krava> <20200210170159.GV302770@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200210170159.GV302770@tassilo.jf.intel.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 10, 2020 at 09:01:59AM -0800, Andi Kleen wrote: > > > With --percore-show-thread, CPU0 and CPU4 have the same counts (CPU0 and > > > CPU4 are siblings, e.g. 2,453,061 in my example). The value is sum of CPU0 + > > > CPU4. > > > > so it shows percore stats but displays all the cpus? what is this good for? > > This is essentially a replacement for the any bit (which is gone in Icelake). > Per core counts are useful for some formulas, e.g. CoreIPC > > The original percore version was inconvenient to post process. This > variant matches the output of the any bit. I see, please put this to the changelog/doc thanks, jirka