Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1464156pxb; Sat, 29 Jan 2022 06:50:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJzy7YYx8G8lu1Cy13Ksd/oHCQKf4HUbtXYQZCRJfUHIbgres8kF3BThKorNznBfhrVTh4WW X-Received: by 2002:a63:5242:: with SMTP id s2mr10241520pgl.435.1643467852536; Sat, 29 Jan 2022 06:50:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643467852; cv=none; d=google.com; s=arc-20160816; b=nw4H+d2vZZjxaz41yLlAmyZ3WfxsrGir9nEO/Dqs2mOFgjVFhDt4fi5713Gt1jZGSv U80mNpoFBv4ptt5W8KI8i7SzQ/JbRxkGngyxVBmBSeyd362Ng7sC5KI9Csbmo2eyphGg xICWQzMpmFwoxURHdhdiLY8NypYhXgpGPlqn4Ana7iZzb4qEJy63n1GJxA9DTE2bYr+3 CzqRGUW05Pf4R3Vf2iOYraFZt3mp8x8KV7bxf478A2XsFcj+W9+kyL+X6z6nrybk6CDm DBNfqxK5EhxvGUNHN+13nwfkzgmbnRpM2I6WsUu3Cb+4vYO2jd3emnaN1hcCEoNNSbCF ++FQ== 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 :cc:to:subject; bh=lsTAln8mbkpN5rMMuTcNMI54vhJBlew3TRdD8r+g6y4=; b=vRGy79SkzRdZGsquPVjYf/VZO/FNj8YGCVUpJYRDtmelW/l35cO4qZQWlCPw26lMiN j/osjbYwGkBUs052A1fnGo40Aup7AyBmwrystzX2FOaZXXAC3dGYX9GzrRvuzbMoMq6R 6GPcxjaIAWhS5ODL9UBU2W0rwm8R2l5SMU+CKghkeFWn8fzEKpVNpj19vXFoPcxvh/wr n5viry2JQys3v653xSNQmgMnMjI1xkyXYa8yuk/Nzge2RVo1Y8xjH3SqhvW4g+10yiMr pwB/3iocE9LrX0LgW0EJCYnGS2HFs5a6ZzmUpi5KuDIUDSaGjfwRQeh5IMai3LexrXfk XfIg== 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 b4si8373919pgt.307.2022.01.29.06.50.22; Sat, 29 Jan 2022 06:50:52 -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; 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 S1345932AbiA1EOW (ORCPT + 99 others); Thu, 27 Jan 2022 23:14:22 -0500 Received: from foss.arm.com ([217.140.110.172]:45856 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236875AbiA1EOV (ORCPT ); Thu, 27 Jan 2022 23:14:21 -0500 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 D4214113E; Thu, 27 Jan 2022 20:14:20 -0800 (PST) Received: from [10.163.44.75] (unknown [10.163.44.75]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 331C03F7D7; Thu, 27 Jan 2022 20:14:15 -0800 (PST) Subject: Re: [RFC V1 10/11] perf: Expand perf_branch_entry.type To: James Clark , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Catalin Marinas , Will Deacon , Mark Rutland , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , linux-perf-users@vger.kernel.org, Alexander Shishkin , Jiri Olsa , Namhyung Kim References: <1642998653-21377-1-git-send-email-anshuman.khandual@arm.com> <1642998653-21377-11-git-send-email-anshuman.khandual@arm.com> <2d7297b3-9a22-626b-9840-a4eaab4b94e8@arm.com> From: Anshuman Khandual Message-ID: <17dc4a62-14d6-c0f2-b428-c1525411b1e0@arm.com> Date: Fri, 28 Jan 2022 09:44:22 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <2d7297b3-9a22-626b-9840-a4eaab4b94e8@arm.com> 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 1/25/22 10:28 PM, James Clark wrote: > > On 24/01/2022 04:30, Anshuman Khandual wrote: >> Current perf_branch_entry.type is a 4 bits field just enough to accommodate >> 16 generic branch types. This is insufficient to accommodate platforms like >> arm64 which has much more branch types. Lets just expands this field into a >> 6 bits one, which can now hold 64 generic branch types. This also adds more >> generic branch types and updates the BRBE driver as required. >> >> Cc: Peter Zijlstra >> Cc: Ingo Molnar >> Cc: Arnaldo Carvalho de Melo >> Cc: Mark Rutland >> Cc: Alexander Shishkin >> Cc: Jiri Olsa >> Cc: Namhyung Kim >> Cc: Will Deacon >> Cc: linux-arm-kernel@lists.infradead.org >> Cc: linux-perf-users@vger.kernel.org >> Cc: linux-kernel@vger.kernel.org >> Signed-off-by: Anshuman Khandual >> --- >> drivers/perf/arm_pmu_brbe.c | 7 ++++++- >> include/uapi/linux/perf_event.h | 10 ++++++++-- >> tools/include/uapi/linux/perf_event.h | 10 ++++++++-- >> tools/perf/util/branch.c | 8 +++++++- >> 4 files changed, 29 insertions(+), 6 deletions(-) >> >> diff --git a/drivers/perf/arm_pmu_brbe.c b/drivers/perf/arm_pmu_brbe.c >> index 8d27ad868359..7cd1208c6c58 100644 >> --- a/drivers/perf/arm_pmu_brbe.c >> +++ b/drivers/perf/arm_pmu_brbe.c >> @@ -253,12 +253,17 @@ static int brbe_fetch_perf_type(u64 brbinf) >> case BRBINF_TYPE_DEBUG_EXIT: >> return PERF_BR_DEBUG_EXIT; >> case BRBINF_TYPE_SERROR: >> + return PERF_BR_SERROR; >> case BRBINF_TYPE_INST_DEBUG: >> + return PERF_BR_DEBUG_INST; >> case BRBINF_TYPE_DATA_DEBUG: >> + return PERF_BR_DEBUG_DATA; >> case BRBINF_TYPE_ALGN_FAULT: >> + return PERF_BR_FAULT_ALGN; >> case BRBINF_TYPE_INST_FAULT: >> + return PERF_BR_FAULT_INST; >> case BRBINF_TYPE_DATA_FAULT: >> - return PERF_BR_UNKNOWN; >> + return PERF_BR_FAULT_DATA; >> default: >> pr_warn("unknown branch type captured\n"); >> return PERF_BR_UNKNOWN; >> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h >> index b91d0f575d0c..361fdc6b87a0 100644 >> --- a/include/uapi/linux/perf_event.h >> +++ b/include/uapi/linux/perf_event.h >> @@ -256,6 +256,12 @@ enum { >> PERF_BR_FIQ = 13, /* fiq */ >> PERF_BR_DEBUG_HALT = 14, /* debug halt */ >> PERF_BR_DEBUG_EXIT = 15, /* debug exit */ >> + PERF_BR_DEBUG_INST = 16, /* instruciton debug */ >> + PERF_BR_DEBUG_DATA = 17, /* data debug */ >> + PERF_BR_FAULT_ALGN = 18, /* alignment fault */ >> + PERF_BR_FAULT_DATA = 19, /* data fault */ >> + PERF_BR_FAULT_INST = 20, /* instruction fault */ >> + PERF_BR_SERROR = 21, /* system error */ >> PERF_BR_MAX, >> }; >> >> @@ -1370,8 +1376,8 @@ struct perf_branch_entry { >> in_tx:1, /* in transaction */ >> abort:1, /* transaction abort */ >> cycles:16, /* cycle count to last branch */ >> - type:4, /* branch type */ >> - reserved:40; >> + type:6, /* branch type */ >> + reserved:38; >> }; >> >> union perf_sample_weight { >> diff --git a/tools/include/uapi/linux/perf_event.h b/tools/include/uapi/linux/perf_event.h >> index 1882054e8684..9a82b8aaed93 100644 >> --- a/tools/include/uapi/linux/perf_event.h >> +++ b/tools/include/uapi/linux/perf_event.h >> @@ -256,6 +256,12 @@ enum { >> PERF_BR_FIQ = 13, /* fiq */ >> PERF_BR_DEBUG_HALT = 14, /* debug halt */ >> PERF_BR_DEBUG_EXIT = 15, /* debug exit */ >> + PERF_BR_DEBUG_INST = 16, /* instruciton debug */ >> + PERF_BR_DEBUG_DATA = 17, /* data debug */ >> + PERF_BR_FAULT_ALGN = 18, /* alignment fault */ >> + PERF_BR_FAULT_DATA = 19, /* data fault */ >> + PERF_BR_FAULT_INST = 20, /* instruction fault */ >> + PERF_BR_SERROR = 21, /* system error */ >> PERF_BR_MAX, >> }; >> >> @@ -1370,8 +1376,8 @@ struct perf_branch_entry { >> in_tx:1, /* in transaction */ >> abort:1, /* transaction abort */ >> cycles:16, /* cycle count to last branch */ >> - type:4, /* branch type */ >> - reserved:40; >> + type:6, /* branch type */ >> + reserved:38; >> }; > There's another copy of this struct in branch.h that is used to access the same data in > perf which also needs updating: > > struct branch_flags { > union { > u64 value; > struct { > u64 mispred:1; > u64 predicted:1; > u64 in_tx:1; > u64 abort:1; > u64 cycles:16; > u64 type:4; > u64 reserved:40; > }; > }; > }; Sure, thanks for the catch. Will fix it. > > It's never assigned directly but there is some casting stuff going on in > evsel__parse_sample() and it eventually ends up being used to access branch > records. Same applies to the privilege data change. > Okay, will do the necessary changes in the privilege data patch.