Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp1144685pxv; Fri, 25 Jun 2021 06:26:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwlbAZJruNzd3o3p/PC2lkZT6/4JeOWizy1XFmZZQ9V6LaBbJbyxKe4qOh6zLAhrW3Z21hX X-Received: by 2002:aa7:c70d:: with SMTP id i13mr14643373edq.249.1624627596454; Fri, 25 Jun 2021 06:26:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624627596; cv=none; d=google.com; s=arc-20160816; b=0frzNs1rdlLig9Bvf/YLC4iIqsGE/0lyhjIQ6K0NmcJ+b591BMfG/GlWUKpt+5aSjR 7N388T8PNocGmQv3nV/41nC8Tcqu+6SLclXigFIVDHtZJhWepZg21/IjR6qn2cFE3CCy E/U/okOAVThAwHf8dp/GuppLvKAImJijtYpQTUgMvLuPTB4i+QQEntimeRq1G++OLm5H IPF115TAMIm+DgX2jFPGVWjxax5jiivxSxNU5K8aGwuyjwbV+ifrsC10WqLxt853NTS2 JzL+71tlD2PGe3/l6M5Xhp9ZdTI6q5o/h8LkDr45jua89tQbMZ73LfPYQr7STavNp199 Zd/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :to:subject; bh=LHtczTqWJFNRGH8rHy22kYO9Y/m00u1Qdp8ADlMfkL8=; b=BBIyAOVSNXs92wAY4UJU1mBIId9/ehGbifDVhC4a119TnBlJwRT3KbshsG798jntPr l6CT3qtrDxWlTVjzDC11tZ3adXfQDPJxFeJop8eiBwWjrCPh358t7uGi54WmF5NlM4Xk gkn8aYv4iAZSyKH/E0HBuqI+9IniutRI7xMoTdgqnIAaSCoE53JiUDdu2nwxYKAzmoiQ z8IYcxk+eH/vgHxvxtZmVlfFeGFpjzxH/6pi31yLdYPTZq/QpHo0fa5A1EmgtC86wKs0 HYTDa+J76rtrfd3f4BTnBZwQik0cVuE+vD+tefQYVPUY+3tzRhckIMC+blSyjqpIjJI7 WPjw== 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=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hx21si5665437ejc.112.2021.06.25.06.26.12; Fri, 25 Jun 2021 06:26:36 -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=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231492AbhFYN1k (ORCPT + 99 others); Fri, 25 Jun 2021 09:27:40 -0400 Received: from foss.arm.com ([217.140.110.172]:55846 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229934AbhFYN1k (ORCPT ); Fri, 25 Jun 2021 09:27:40 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5A5B031B; Fri, 25 Jun 2021 06:25:19 -0700 (PDT) Received: from [10.57.8.165] (unknown [10.57.8.165]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 391E73F694; Fri, 25 Jun 2021 06:25:17 -0700 (PDT) Subject: Re: [PATCH v5 5/5] perf arm-spe: Don't wait for PERF_RECORD_EXIT event To: Leo Yan , Arnaldo Carvalho de Melo , John Garry , Will Deacon , Mathieu Poirier , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Dave Martin , Al Grant , linux-arm-kernel@lists.infradead.org, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210519071939.1598923-1-leo.yan@linaro.org> <20210519071939.1598923-6-leo.yan@linaro.org> From: James Clark Message-ID: <369fd454-d94d-daa1-ead4-b42645ec4282@arm.com> Date: Fri, 25 Jun 2021 14:25:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210519071939.1598923-6-leo.yan@linaro.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/05/2021 08:19, Leo Yan wrote: > When decode Arm SPE trace, it waits for PERF_RECORD_EXIT event (the last > perf event) for processing trace data, which is needless and even might > cause logic error, e.g. it might fail to correlate perf events with Arm > SPE events correctly. > > So this patch removes the condition checking for PERF_RECORD_EXIT event. > > Signed-off-by: Leo Yan > --- > tools/perf/util/arm-spe.c | 6 +----- > 1 file changed, 1 insertion(+), 5 deletions(-) > > diff --git a/tools/perf/util/arm-spe.c b/tools/perf/util/arm-spe.c > index 5c5b438584c4..58b7069c5a5f 100644 > --- a/tools/perf/util/arm-spe.c > +++ b/tools/perf/util/arm-spe.c > @@ -717,11 +717,7 @@ static int arm_spe_process_event(struct perf_session *session, > sample->time); > } > } else if (timestamp) { > - if (event->header.type == PERF_RECORD_EXIT) { > - err = arm_spe_process_queues(spe, timestamp); > - if (err) > - return err; > - } > + err = arm_spe_process_queues(spe, timestamp); > } > > return err; > For the whole set: Reviewed-by: James Clark Tested-by: James Clark I see a big improvement in decoding involving multiple processes because the timestamps are now correlated with the comm and mmap events. For example perf-exec samples are visible right before the exec is done, and on an application that forks, samples are visible from all processes. For example: perf record -e arm_spe// -- bash -c "stress -c 1" perf script perf-exec 4502 [003] 259755.050409: 1 l1d-access: ffff80001014b840 sched_clock+0x40 ([kernel.kallsyms]) perf-exec 4502 [003] 259755.050409: 1 tlb-access: ffff80001014b840 sched_clock+0x40 ([kernel.kallsyms]) perf-exec 4502 [003] 259755.050409: 1 memory: ffff80001014b840 sched_clock+0x40 ([kernel.kallsyms]) perf-exec 4502 [003] 259755.050411: 1 tlb-access: ffff800010120fb8 __rcu_read_lock+0x0 ([kernel.kallsyms]) bash 4502 [003] 259755.050411: 1 branch-miss: ffff8000105b2a40 memcpy+0x80 ([kernel.kallsyms]) bash 4502 [003] 259755.050411: 1 tlb-access: 0 [unknown] ([unknown]) ... stress 4502 [003] 259755.051468: 1 l1d-access: ffff800010259a24 __vma_adjust+0x1f4 ([kernel.kallsyms]) stress 4502 [003] 259755.051468: 1 tlb-access: ffff800010259a24 __vma_adjust+0x1f4 ([kernel.kallsyms]) stress 4502 [003] 259755.051468: 1 memory: ffff800010259a24 __vma_adjust+0x1f4 ([kernel.kallsyms]) Previously samples were only attributed to 'stress', which was obviously wrong. James