Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp13695189pxu; Mon, 4 Jan 2021 01:40:33 -0800 (PST) X-Google-Smtp-Source: ABdhPJzw65GGT7rVmXROvDstFP3xgio3+YX4QTYPWMuoC0kPSMNWb3C+TKOqSh5ainSumiRuBRcE X-Received: by 2002:a17:906:90d6:: with SMTP id v22mr65945895ejw.88.1609753233108; Mon, 04 Jan 2021 01:40:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609753233; cv=none; d=google.com; s=arc-20160816; b=sYaKSZ9u9zHg9Nrl0LHxDqd80xKvHcLni86dU44lRnAe3jvbsV1QEhtte6eOy2Wy+4 CWVjbHZ5lq+gxyoHFA6PNHfZPuet0Nrfc/OphFOjyelQjZKqf2Mroi43S2zoTOmnYZ2J fj5UReC4HV8WHIdYaSEZGNnWxd+KMt2prUcV1uCFVf/ZzgFvw+ysz5eEiiZ2Ajrubg4L ecw5gL2ZTWvJnbXdonvmnI17Qq/ZHGIPXfnNExkOHonSqM5PPELsr0/9YduSBSZoS/Mi 5bG+qccWCt+85uw2CADK6wBfzG/KchckDbf2Hkbvlh5s1gcP+j6S68aA1xfx3AEnQAYo BvjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=EXtyco+eWjU47nR0Op2rkNaXPKFVZZ+Ls3Jqh0AGFz4=; b=rLL7R0fejN98MwbQZUrfj8zRLHn6umUA9VNnW7OfvCujOIsUCG1CtLVjEx6RBHvM4x B/iV2FGKHXZMGguzg+mFBe02AzSQI/Pp9bDNSZmi+CKC3zoDxoRoe1FjP9UEk4kzEdSA mRM2NCTNY3i+wVwGx5i6xunwJlYVGVRHb2XQrVxf4RtYugCBKgyXfCTH8Xk2RBi/1i/l 0WNTTf9dlzyAm8KfE+P73q5HEULlBK1QhlK1fKOZDM2trgt8G7TMmD6lZIqlbZoKvnMI ymRdV9B26YRi6bWgwtaJjm67OvBeHuyrP0pvKRIguA+KQtac9Vq+o0mBvu7c75iX1AiA T8ZQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=WoYtXkTm; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ba7si31314036edb.70.2021.01.04.01.40.10; Mon, 04 Jan 2021 01:40:33 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=WoYtXkTm; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726502AbhADJhR (ORCPT + 99 others); Mon, 4 Jan 2021 04:37:17 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:41989 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726196AbhADJhR (ORCPT ); Mon, 4 Jan 2021 04:37:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1609752950; 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=EXtyco+eWjU47nR0Op2rkNaXPKFVZZ+Ls3Jqh0AGFz4=; b=WoYtXkTmX6ody1MEqidM7UL7hPp3+uCDYRw+kOiOkPUraG9HGsrJRsnrPtD+el5ufUsg99 v98zBUdBSACJCA+No0xmvLXTJ2pT1o2tGk5JjjSD5w8Uhjf2nzMdpAIap+EZ4aWHLiHn9+ G6G7J5MEutzCpLrOCSy2lAyg6fZRdC8= 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-395-2XAFPNLaOiiR6NeE-c08Uw-1; Mon, 04 Jan 2021 04:35:47 -0500 X-MC-Unique: 2XAFPNLaOiiR6NeE-c08Uw-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 1E47B804006; Mon, 4 Jan 2021 09:35:45 +0000 (UTC) Received: from krava (unknown [10.40.192.45]) by smtp.corp.redhat.com (Postfix) with SMTP id 91D53E145; Mon, 4 Jan 2021 09:35:41 +0000 (UTC) Date: Mon, 4 Jan 2021 10:35:40 +0100 From: Jiri Olsa To: Leo Yan Cc: Arnaldo Carvalho de Melo , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , Namhyung Kim , Andi Kleen , Ian Rogers , Kan Liang , Joe Mario , David Ahern , Don Zickus , Al Grant , James Clark , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 00/11] perf c2c: Sort cacheline with all loads Message-ID: <20210104093540.GA872376@krava> References: <20201213133850.10070-1-leo.yan@linaro.org> <20210103225219.GA850408@krava> <20210104020930.GA4897@leoy-ThinkPad-X240s> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210104020930.GA4897@leoy-ThinkPad-X240s> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 04, 2021 at 10:09:38AM +0800, Leo Yan wrote: SNIP > > > Leo Yan (11): > > > perf c2c: Add dimensions for total load hit > > > perf c2c: Add dimensions for load hit > > > perf c2c: Add dimensions for load miss > > > perf c2c: Rename for shared cache line stats > > > perf c2c: Refactor hist entry validation > > > perf c2c: Refactor display filter macro > > > perf c2c: Refactor node display macro > > > perf c2c: Refactor node header > > > perf c2c: Add local variables for output metrics > > > perf c2c: Sort on all cache hit for load operations > > > perf c2c: Update documentation for display option 'all' > > > > > > tools/perf/Documentation/perf-c2c.txt | 21 +- > > > tools/perf/builtin-c2c.c | 548 ++++++++++++++++++++++---- > > > 2 files changed, 487 insertions(+), 82 deletions(-) > > > > Joe might want to test it first, but it looks all good to me: > > > > Acked-by: Jiri Olsa > > Thanks for the review, Jiri. > > Note, after testing with Arm SPE, we found the store operations don't > contain the information for L1 cache hit or miss, this leads to there > have no statistics for "st_l1hit" and "st_l1miss"; finally the single > cache line view only can show the load samples and fails to show store > opreations due to the empty statistics for "st_l1hit" and "st_l1miss". > > This is related the hardware issue, after some discussion internally, > so far cannot find a easy way to set memory flag for L1 cache hit or > miss for store operations (more specific, set flags PERF_MEM_LVL_HIT or > PERF_MEM_LVL_MISS for store's L1 cache accessing). > > Given it is uncertain for this issue, please hold on for this patch > series and I will resend if have any conclusion. > > And really sorry I notify this too late. no problem, I think we can take some of the refactoring patches anyway thanks, jirka