Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp4291611rdb; Mon, 11 Dec 2023 15:02:13 -0800 (PST) X-Google-Smtp-Source: AGHT+IE6yn7LJzS8Xc49F28AGJqwI16Z+rgCB+3maHQT4oR6Sdw3/XRepima2qtbIUK/HXF3UhHk X-Received: by 2002:a05:6a00:8c8:b0:6d0:9bcc:facd with SMTP id s8-20020a056a0008c800b006d09bccfacdmr1300744pfu.40.1702335733231; Mon, 11 Dec 2023 15:02:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702335733; cv=none; d=google.com; s=arc-20160816; b=nUKcPmQlztOPCkziDvFW3cVZ2pSXRSjX0hJ5tRIdul50EoFW5R4SMKTJuxIknL1Hi0 Klh3FSQWXFlKL7N9d/llKNE+Jun+DTBnS0yS14K8hMoUIDAYuJs2M/YV70UsJOaS5H5Y DTjWm0zp7LYnmxJa8U3b3j2rG2iUuxTGWVdtKdiShVbO0YA6DR6Xa7kUeMfvcgJZMx0Q DzLWFUTI3HZmcIcd3fFFmjCFllB8znUS4m0wqkydKWntdSUX5XfNPpGxZuBID8zSbnqP K684YZNv8GMa9VYUME3bZSAKsWI2hLDXLo6jxcZTxxVLb4TrCyXl86zkPP84kCgELWCT K3rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version; bh=jtwaTMyljIMzZXcJkd20fAmJDWxPPDI7YfTvKBwVRYk=; fh=LS3Waojm+odtyAmTz7hf1JGpgblc4o4LTFxz4R4sPUc=; b=1EOMLeVLmEJcsHwpSUR/hECzvjyinuJf/PvFio1Rm1FSa9adog2RRYSuESP8ADOw58 zRl3Zd+f2X+bBzRMnq+PoNxTQQ91KyYY2vJw0yvLVbu+Z1muPWItXtqw3Th+NMLnBoUw Pt33CWKnHREJsjmP1by3H4Eg8VLh1SRie4a5sCLA8SA2N71QMyTLoBJlhf/lNLWlpR4E GcZbx8rpwleDhInuq3LqZHfQaD9PloJzsbb/StwC357lM5iq15cAsZo3DENuMV+QSZFm l8lPSHb9u25BU2jtEEyyUWYnC+q9SVhtJcd20b5nDCHHowqcl/s3DdU4v+zXEYaMrEsi Q1ig== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from snail.vger.email (snail.vger.email. [23.128.96.37]) by mx.google.com with ESMTPS id o2-20020a634e42000000b005c662c8da7fsi6744603pgl.730.2023.12.11.15.02.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Dec 2023 15:02:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by snail.vger.email (Postfix) with ESMTP id 76074804E884; Mon, 11 Dec 2023 15:02:11 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at snail.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345231AbjLKXCC convert rfc822-to-8bit (ORCPT + 99 others); Mon, 11 Dec 2023 18:02:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49942 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345166AbjLKXCB (ORCPT ); Mon, 11 Dec 2023 18:02:01 -0500 Received: from mail-oo1-f50.google.com (mail-oo1-f50.google.com [209.85.161.50]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C96619A; Mon, 11 Dec 2023 15:02:07 -0800 (PST) Received: by mail-oo1-f50.google.com with SMTP id 006d021491bc7-58d18c224c7so2644818eaf.2; Mon, 11 Dec 2023 15:02:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702335727; x=1702940527; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZzAtMvelZEhbKh45bRc76zp7HAJfBcphLeBiuFGz8KE=; b=kdnwIZMoLWSUtx9MK2XxYNTE/kpzkUED8UPdL5KVAguznnYThi/PAuDhwBTpAiw8RC ZH11+sqrL4Q0vtYnIWHu7GF+lLy8Q0wZDShHITYt6ejOdsyl8SjEx2LYgAr0ULwOZIj6 hpblz31PvCONHGShDAYz2UNH1UBwdy8Y7hnrBX8/rz0QlQnwT/Mgn9miej43MBOwGyZR 8/kUaNfK6f2cSOwsejqCsWRxHl11pOkL6LXt/cuo+kRKf2+m4OEgEzJJ/K633pH8Pa0G prISvDM4DK5RrtZVZOp99cr77XodNYDh2687n9lbRsgQ60RWvmOmtSVNa7pjhiC6MlsN ar8w== X-Gm-Message-State: AOJu0YwedWa+g3sF9JyhJqUY4E1tR+WXHGsZGMNFDb82W/2FNyETBpiB M6vnCczKhvvsSRITdq0gNuoQpFUitAvtd82Ar0c= X-Received: by 2002:a05:6358:248b:b0:170:6ed7:3148 with SMTP id m11-20020a056358248b00b001706ed73148mr2916226rwc.22.1702335726809; Mon, 11 Dec 2023 15:02:06 -0800 (PST) MIME-Version: 1.0 References: <20231107083331.901-1-ravi.bangoria@amd.com> <53374e41-d1e0-aa8f-d001-5e89783b962c@amd.com> In-Reply-To: <53374e41-d1e0-aa8f-d001-5e89783b962c@amd.com> From: Namhyung Kim Date: Mon, 11 Dec 2023 15:01:55 -0800 Message-ID: Subject: Re: [PATCH 1/2] perf tool AMD: Use non-precise cycles as default event on certain Zen2 processors To: Ravi Bangoria Cc: acme@kernel.org, kim.phillips@amd.com, peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com, alexander.shishkin@linux.intel.com, jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com, kan.liang@linux.intel.com, changbin.du@huawei.com, yangjihong1@huawei.com, zwisler@chromium.org, wangming01@loongson.cn, chenhuacai@kernel.org, kprateek.nayak@amd.com, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, sandipan.das@amd.com, ananth.narayan@amd.com, santosh.shukla@amd.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (snail.vger.email [0.0.0.0]); Mon, 11 Dec 2023 15:02:11 -0800 (PST) On Mon, Dec 11, 2023 at 5:54 AM Ravi Bangoria wrote: > > Hi Namhyung, > > >>>> By default, Perf uses precise cycles event when no explicit event is > >>>> specified by user. Precise cycles event is forwarded to ibs_op// pmu > >>>> on AMD. However, IBS has hw issue on certain Zen2 processors where > >>>> it might raise NMI without sample_valid bit set, which causes Unknown > >>>> NMI warnings. (Erratum #1215: IBS (Instruction Based Sampling) Counter > >>>> Valid Value May be Incorrect After Exit From Core C6 (CC6) State.) So, > >>>> use non-precise cycles as default event on affected processors. > >>> > >>> It seems like a kernel issue, do we have a kernel patch not to forward > >>> precise cycles or instructions events to IBS on the affected CPUs? > >> > >> I'm not sure how it's a kernel issue. User can use ibs_op// pmu directly > >> and might hit the hw bug. > > > > Sorry for the late reply. I know it's the user's fault when using ibs_op// > > directly but I think the kernel should not forward cycles:pp to IBS. > > For all AMD zen uarchs, cycles:p is same as ibs_op// (man perf-list has > more detail). It's confusing if ibs_op// works but cycles:p fails on the > same machine. Make sense. Probably perf tools can provide a more detailed message about the situation. > > No strong opinion though. I can prepare a kernel patch, if you want. I have a report that these unknown NMI messages caused some performance issues. So maybe we need to be safe by not using IBS automatically. I've also posted a patch to rate-limit the message itself. Thanks, Namhyung