Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp5582411pxb; Wed, 19 Jan 2022 23:41:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJzb7+chV7NsnebrnSZrrUSagXEgR4YXWYJcbNub2EEZLFJ2YdXGE9jHsdaud2VhN2sL7/2i X-Received: by 2002:a05:6a00:1a8f:b0:4bd:118:8071 with SMTP id e15-20020a056a001a8f00b004bd01188071mr23027273pfv.28.1642664491960; Wed, 19 Jan 2022 23:41:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642664491; cv=none; d=google.com; s=arc-20160816; b=bGJ/HoRw/0x1SteghqAjdpJftzuqyvmDRUafcgF5u4prkmsWDrooxjVPhUElcyswJR yN+3+0sw63Se1nBAeT5ZpA+WDBWXnNaC/1oUediMH27D7Mpk/Imf0QdxJOteToxc5KW1 JkxdBgkohtV4GDJeUGq88dhv+1OSfbqq8BtrHE0XyFNIypxmm6Hd0Khmn5dNP4JPV92A WOC/caJP5ZO3qM8gALl+k7TDZdcW60d1BvnUtOd9s+21WA7JVULIBdFQXvEK24oVUvQm eKw0qfikbS+rVD9reJ46Mphfeim1L5wEMdoz97Dr7Bq8Nnue540mIM+SUAhbFoP23wjg mgFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:robot-unsubscribe :robot-id:message-id:mime-version:references:in-reply-to:cc:subject :to:reply-to:sender:from:dkim-signature:dkim-signature:date; bh=PaW7SLV/zkwu/CdKU07m4qvRYvngfu+HL9fRAydCr/0=; b=Dno45myld8FlvBVMAz28iTp5GEjzCero0c5vo5wPOECrNtY8S208X2Bqvi7s/65dPc M8m1uOlSFRfeUHsAfDOCvVBIVvrcX2V4JUKxcCgQHSP748ce9RYbGuYSuuZHaUxsPKyy XOYazfRx8KLvsa91jjz82Y2iipdmZhLvHEXy9tM+TqQd2mL/a7OtVA6MLTDd/BiWrfPY cysT50xEyx49loy/Q3usVjNKc+QRuW+yMAYdxGdM43pz+ZnS6P99FlgBaCh47PaoTAbL qGjC6DztfPnJo396NJoVj4Aj1qkGYQYeRLyzAq8lmoPboYOAsQB4YNuphVoufqQyVL4g 5e2w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b="TFTaPEp/"; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=9ayccppg; 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=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a38si2545534pfx.112.2022.01.19.23.41.19; Wed, 19 Jan 2022 23:41:31 -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=@linutronix.de header.s=2020 header.b="TFTaPEp/"; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=9ayccppg; 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=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239501AbiARLSH (ORCPT + 99 others); Tue, 18 Jan 2022 06:18:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40492 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239344AbiARLR4 (ORCPT ); Tue, 18 Jan 2022 06:17:56 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AAFC1C06173E; Tue, 18 Jan 2022 03:17:55 -0800 (PST) Date: Tue, 18 Jan 2022 11:17:53 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1642504674; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PaW7SLV/zkwu/CdKU07m4qvRYvngfu+HL9fRAydCr/0=; b=TFTaPEp/cRgrAwQr/V13GpwcqaktqGtZJua9FYunFUvsoM5dBhJR6cQJ3utzO67i120P/W StGK1NVRgubrqPgSqJb0aVJZv3YXqslPupdfA0d3O02Z+9g8/EJ6lXNwk9J0jiZTvsDcT/ +DHy7pDJgTg6uRld3FStCdU07ghBTLkng7uvsLFGPbvFnEC9EmXBPVhIwx4H2LrAlKbCDf 714HAXC3w5o2EjU7Ial4wAvEFJ4NvUsFg0KYmqRdGlL/wYmp0IXc9KxHcr+vviMba8PBdk OkmomaST2aB2pHO7Ql8vzhfXh7vZtl7l2ANR0EZKbCdQ6HgASsHEdcsK066xUQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1642504674; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PaW7SLV/zkwu/CdKU07m4qvRYvngfu+HL9fRAydCr/0=; b=9ayccppgZB5QDhM13WPT0bivqpPJe9wUlA2NAD2p9U1yNURzNFIr6VdKn9MLnlBZ4nknfp 6YbkPE5D/9cIiMDw== From: "tip-bot2 for Zhengjun Xing" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: perf/urgent] perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX Cc: Zhengjun Xing , "Peter Zijlstra (Intel)" , Adrian Hunter , Kan Liang , stable@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20211223144826.841267-1-zhengjun.xing@linux.intel.com> References: <20211223144826.841267-1-zhengjun.xing@linux.intel.com> MIME-Version: 1.0 Message-ID: <164250467331.16921.5385792639692425336.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following commit has been merged into the perf/urgent branch of tip: Commit-ID: 96fd2e89fba1aaada6f4b1e5d25a9d9ecbe1943d Gitweb: https://git.kernel.org/tip/96fd2e89fba1aaada6f4b1e5d25a9d9ecbe= 1943d Author: Zhengjun Xing AuthorDate: Thu, 23 Dec 2021 22:48:26 +08:00 Committer: Peter Zijlstra CommitterDate: Tue, 18 Jan 2022 12:09:48 +01:00 perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX The user recently report a perf issue in the ICX platform, when test by perf event =E2=80=9Cuncore_imc_x/cas_count_write=E2=80=9D,the write bandwidth= is always very small (only 0.38MB/s), it is caused by the wrong "umask" for the "cas_count_write" event. When double-checking, find "cas_count_read" also is wrong. The public document for ICX uncore: 3rd Gen Intel=C2=AE Xeon=C2=AE Processor Scalable Family, Codename Ice Lake,U= ncore Performance Monitoring Reference Manual, Revision 1.00, May 2021 On 2.4.7, it defines Unit Masks for CAS_COUNT: RD b00001111 WR b00110000 So corrected both "cas_count_read" and "cas_count_write" for ICX. Old settings: hswep_uncore_imc_events INTEL_UNCORE_EVENT_DESC(cas_count_read, "event=3D0x04,umask=3D0x03") INTEL_UNCORE_EVENT_DESC(cas_count_write, "event=3D0x04,umask=3D0x0c") New settings: snr_uncore_imc_events INTEL_UNCORE_EVENT_DESC(cas_count_read, "event=3D0x04,umask=3D0x0f") INTEL_UNCORE_EVENT_DESC(cas_count_write, "event=3D0x04,umask=3D0x30") Fixes: 2b3b76b5ec67 ("perf/x86/intel/uncore: Add Ice Lake server uncore suppo= rt") Signed-off-by: Zhengjun Xing Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: Adrian Hunter Reviewed-by: Kan Liang Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/20211223144826.841267-1-zhengjun.xing@linux.i= ntel.com --- arch/x86/events/intel/uncore_snbep.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/events/intel/uncore_snbep.c b/arch/x86/events/intel/unc= ore_snbep.c index 3660f69..ed86944 100644 --- a/arch/x86/events/intel/uncore_snbep.c +++ b/arch/x86/events/intel/uncore_snbep.c @@ -5482,7 +5482,7 @@ static struct intel_uncore_type icx_uncore_imc =3D { .fixed_ctr_bits =3D 48, .fixed_ctr =3D SNR_IMC_MMIO_PMON_FIXED_CTR, .fixed_ctl =3D SNR_IMC_MMIO_PMON_FIXED_CTL, - .event_descs =3D hswep_uncore_imc_events, + .event_descs =3D snr_uncore_imc_events, .perf_ctr =3D SNR_IMC_MMIO_PMON_CTR0, .event_ctl =3D SNR_IMC_MMIO_PMON_CTL0, .event_mask =3D SNBEP_PMON_RAW_EVENT_MASK,