Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp907490ybg; Wed, 29 Jul 2020 00:22:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzKW7EvY+WydF2ukeAWovufsai/JcVRkgtL34Pb26JLWpc7ZDrGjXpuVoJqZYAdXVMoM/DX X-Received: by 2002:aa7:d043:: with SMTP id n3mr30557347edo.102.1596007342706; Wed, 29 Jul 2020 00:22:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596007342; cv=none; d=google.com; s=arc-20160816; b=WqiInQzf4wW4Zzfk919G717GKhZM6HbM2LwcanKiyWn2M7idFXnpL0pjsNfGAsqYtz qlACTuMCdUX2g6Jxbje02SJ/Q/L+SBAvx+dZJslqCgMGdopPYLIF4o069O/qANwPKJrs re0jA6ZyU/d7QMiwLidFaSUrmw6Y5fhE86nktQq/5vUqj9fonVEI21mEW56Hy4aMYJr2 XhVHW21Bxi//sWAA2+wlXrKvcoWzwJqB/yq0a3XFZz608CTm0Ag3pgX9C38HOUjuo/bh hlIJUVqPLUWUXl9MxP7AW9ORyVcSCad/jaOBLI47yYkny8URmwEdwvArEsUrPbmzs0pY VPSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=p+RSxKhPUkQ8gglds584uqsqfDpdbN720Nfj9Uq2em0=; b=aqGnnxsY67V0zMBkQ5GTxFhAKsk5NC1pcHgkVjQaZU+v9mmYEeKHpnaFjTe8pGaYpY tu4v9u7/QiYNGCdkvcxdXUqIAkZbM0LIQ16P4Zo6grYJEMYcyaJMLhSIRB/53o66PIjS 6tIyjEA8im/hostMr+f0hKMrQPgAosSs/Ok6fqkbVcDtHM2CYl7nphOLcJns1563E3Gc WX5xRsDRj5avFeeO5wp1Aam2KY3dok3NWffEfKl6iFQA5v7Xbbf+7oI0b76K52gEig4S SLxdSq3BFtc598NYIDPgYI++w39xFHTnHfQAj7lNLCNoN9gNImeBRfnR4R7SuTdx3fTL FFLQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k18si758817edj.429.2020.07.29.00.21.59; Wed, 29 Jul 2020 00:22:22 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727008AbgG2HVj (ORCPT + 99 others); Wed, 29 Jul 2020 03:21:39 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:8848 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726299AbgG2HVi (ORCPT ); Wed, 29 Jul 2020 03:21:38 -0400 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 86C591C6D554C687250A; Wed, 29 Jul 2020 15:21:32 +0800 (CST) Received: from [10.174.178.63] (10.174.178.63) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.487.0; Wed, 29 Jul 2020 15:21:22 +0800 Subject: Re: [PATCH 2/4] perf: arm-spe: Add support for ARMv8.3-SPE To: Leo Yan CC: Adrian Hunter , Alexander Shishkin , Arnaldo Carvalho de Melo , Catalin Marinas , James Clark , Jiri Olsa , Mark Rutland , Namhyung Kim , Suzuki K Poulose , Will Deacon , , , , Ingo Molnar , "Peter Zijlstra" , References: <20200724091607.41903-1-liwei391@huawei.com> <20200724091607.41903-3-liwei391@huawei.com> <20200729062951.GE4343@leoy-ThinkPad-X240s> From: "liwei (GF)" Message-ID: Date: Wed, 29 Jul 2020 15:21:20 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.0 MIME-Version: 1.0 In-Reply-To: <20200729062951.GE4343@leoy-ThinkPad-X240s> Content-Type: text/plain; charset="gbk" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.178.63] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Leo, On 2020/7/29 14:29, Leo Yan wrote: > On Fri, Jul 24, 2020 at 05:16:05PM +0800, Wei Li wrote: >> Armv8.3 extends the SPE by adding: >> - Alignment field in the Events packet, and filtering on this event >> using PMSEVFR_EL1. >> - Support for the Scalable Vector Extension (SVE). >> >> The main additions for SVE are: >> - Recording the vector length for SVE operations in the Operation Type >> packet. It is not possible to filter on vector length. >> - Incomplete predicate and empty predicate fields in the Events packet, >> and filtering on these events using PMSEVFR_EL1. > > This comment description is not relevant with the changes in this > patch, so could remove them. > >> Add the corresponding decode process of Events packet and Operation Type >> packet in perf tool. > > This patch is to add the raw dumping for Events packet and Operation Type > packet. > >> Signed-off-by: Wei Li >> --- >> .../arm-spe-decoder/arm-spe-pkt-decoder.c | 69 ++++++++++++++++++- >> 1 file changed, 67 insertions(+), 2 deletions(-) >> >> diff --git a/tools/perf/util/arm-spe-decoder/arm-spe-pkt-decoder.c b/tools/perf/util/arm-spe-decoder/arm-spe-pkt-decoder.c >> index b94001b756c7..10a3692839de 100644 >> --- a/tools/perf/util/arm-spe-decoder/arm-spe-pkt-decoder.c >> +++ b/tools/perf/util/arm-spe-decoder/arm-spe-pkt-decoder.c >> @@ -347,6 +347,24 @@ int arm_spe_pkt_desc(const struct arm_spe_pkt *packet, char *buf, >> blen -= ret; >> } >> } >> + if (idx > 2) { >> + if (payload & 0x800) { >> + ret = snprintf(buf, buf_len, " ALIGNMENT"); >> + buf += ret; >> + blen -= ret; >> + } >> + if (payload & 0x20000) { >> + ret = snprintf(buf, buf_len, " SVE-PRED-PARTIAL"); >> + buf += ret; >> + blen -= ret; >> + } >> + if (payload & 0x40000) { >> + ret = snprintf(buf, buf_len, " SVE-PRED-EMPTY"); >> + buf += ret; >> + blen -= ret; >> + } >> + } >> + > > Correct. > >> if (ret < 0) >> return ret; >> blen -= ret; >> @@ -354,8 +372,38 @@ int arm_spe_pkt_desc(const struct arm_spe_pkt *packet, char *buf, >> } >> case ARM_SPE_OP_TYPE: >> switch (idx) { >> - case 0: return snprintf(buf, buf_len, "%s", payload & 0x1 ? >> - "COND-SELECT" : "INSN-OTHER"); >> + case 0: { >> + if (payload & 0x8) { > > Some nitpicks for packet format checking ... > > For SVE operation, the payload partten is: 0b0xxx1xx0. > > So it's good to check the partten like: > > /* SVE operation subclass is: 0b0xxx1xx0 */ > if ((payload & 0x8081) == 0x80) { > .... > } > > If later the packet format is extended, this will not introduce any > confliction. Get it, but i think what you are really meaning is: if ((payload & 0x89) == 0x80) { ... } > >> + size_t blen = buf_len; >> + >> + ret = snprintf(buf, buf_len, "SVE-OTHER"); >> + buf += ret; >> + blen -= ret; >> + if (payload & 0x2) { > > Here should express as binary results: " FP" or " INT". I think this is a style choice, i add these just like the current code where processing "AT", "EXCL", "AR", "COND" and so on. So should we modify all the corresponding code together? > >> + ret = snprintf(buf, buf_len, " FP"); >> + buf += ret; >> + blen -= ret; >> + } >> + if (payload & 0x4) { >> + ret = snprintf(buf, buf_len, " PRED"); > > Here should express as binary results: " PRED" or " NOT-PRED". Ditto. > >> + buf += ret; >> + blen -= ret; >> + } >> + if (payload & 0x70) { > > This is incorrect. If bits[6:4] is zero, it presents vector length is 32 bits. > I am a little confused here. Refer to the ARM DDI 0487F.b (ID040120), page D10-2830, if bits[6:4] is zero, it presents vector length is 32 bits indeed. >> + ret = snprintf(buf, buf_len, " EVL %d", >> + 32 << ((payload & 0x70) >> 4)); >> + buf += ret; >> + blen -= ret; >> + } >> + if (ret < 0) >> + return ret; >> + blen -= ret; >> + return buf_len - blen; >> + } else { > > Here we can check with more accurate format as defined in ARMv8 ARM: > > /* Other operation subclass is: 0b0000000x */ > if ((payload & 0xfe) == 0x0) { > .... > } > >> + return snprintf(buf, buf_len, "%s", payload & 0x1 ? >> + "COND-SELECT" : "INSN-OTHER"); >> + } >> + } >> case 1: { >> size_t blen = buf_len; >> >> @@ -385,6 +433,23 @@ int arm_spe_pkt_desc(const struct arm_spe_pkt *packet, char *buf, >> ret = snprintf(buf, buf_len, " SIMD-FP"); >> buf += ret; >> blen -= ret; >> + } else if (payload & 0x8) { >> + if (payload & 0x4) { >> + ret = snprintf(buf, buf_len, " PRED"); > > Here should express as binary results: " PRED" or " NOT-PRED". Ditto. >> + buf += ret; >> + blen -= ret; >> + } >> + if (payload & 0x70) { > > This is incorrect. If bits[6:4] is zero, it presents vector length is 32 bits. Refer to the ARM DDI 0487F.b (ID040120), page D10-2832, if bits[6:4] is zero, it presents vector length is 32 bits indeed. >> + ret = snprintf(buf, buf_len, " EVL %d", >> + 32 << ((payload & 0x70) >> 4)); >> + buf += ret; >> + blen -= ret; >> + } >> + if (payload & 0x80) { >> + ret = snprintf(buf, buf_len, " SG"); > > Here should express as binary results: " SG" or " NOT-SG". Thanks, Wei