Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CA798C6FD1C for ; Fri, 24 Mar 2023 07:22:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230501AbjCXHWi (ORCPT ); Fri, 24 Mar 2023 03:22:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230003AbjCXHWh (ORCPT ); Fri, 24 Mar 2023 03:22:37 -0400 Received: from mail-yw1-x114a.google.com (mail-yw1-x114a.google.com [IPv6:2607:f8b0:4864:20::114a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 22A0346B9 for ; Fri, 24 Mar 2023 00:22:36 -0700 (PDT) Received: by mail-yw1-x114a.google.com with SMTP id 00721157ae682-54463468d06so10580777b3.7 for ; Fri, 24 Mar 2023 00:22:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; t=1679642555; h=cc:to:from:subject:mime-version:message-id:date:from:to:cc:subject :date:message-id:reply-to; bh=gEYIS2l83zsy/niTXf00xhSaE+cVwhcmbbmGjuA/bhk=; b=aXOAVRjHCsIJ292QycPWRl/rqRaYRbmPwekvoYNr09K++UOvxifs1jiEFYz8H1i8pu 1YyUqFMppMKiYSVFf8TxJqPhuXVbMd/pUSCTrYCc/k1QnQzKZs3rX96G0ZP1JBh3Tblc q/e1NuNc4X+dXb7skN5MDcfJUEaKO/335pw77NAsH2bsqbAP4+401zKRm7rc3LIYtnv/ L/ahnf1MnwwYI4QiHvvviW8Uy6IoXRgCbuZepVwa8gquU/Fhr/SHINFAHmXAXX6DSi7q 7h407Oxk+J0E6WIYMwqndXYp+Hj760F5KoKGBqoOrdqh2yQ8XAbE0Xzon/YFxLYJYOQG GRNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679642555; h=cc:to:from:subject:mime-version:message-id:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=gEYIS2l83zsy/niTXf00xhSaE+cVwhcmbbmGjuA/bhk=; b=PcokW192s4iLFh8RwvKDRhd6+3Qm0yUZXUA/PPx7cUV1UNUKmjzC+tAwFHyHfknVZk oInYJoZRz7JFhZ6wHcPdL9FWAFjKOQmpiwtsndu1qLtfK9oEt4pFiSbTxaLXOPZYI5sy qg91sXuxxEK6MRkK49Dmm6SA74ZS7OMKSyzENiVsYDw8mEj086wXiddyNVRh3H/JWk9E D1jZ01iIiFjjy3NCR+kz+0Z5HB6N3vOq5QJg5Jk6/jpTFj5sPhyRQMIXyjRpsPw/CTc0 nho+C6067ddkyBSunKzu2Ko12EWyU+sw30U5VjLHZmQGf6mUxrAe/KSW/XcWVI6NeFX/ xTBg== X-Gm-Message-State: AAQBX9et1jNmti4pFPMoiV1gUXrLiprgXe4Mgal72wmtL2ENxXTQx64H 8q21fHbb0HE9QsiUSS+icmk5OwlRynp9 X-Google-Smtp-Source: AKy350beRdjWw+bm0JzNfNprJ4XxnE62v3xB7iKZgl5Q1sWju2Wtrp9OcNaYzVWSZbREJgwUOf2oPRL+CtBZ X-Received: from irogers.svl.corp.google.com ([2620:15c:2d4:203:e705:3a3d:46e5:fb50]) (user=irogers job=sendgmr) by 2002:a81:4049:0:b0:541:6aa7:f889 with SMTP id m9-20020a814049000000b005416aa7f889mr563321ywn.5.1679642554895; Fri, 24 Mar 2023 00:22:34 -0700 (PDT) Date: Fri, 24 Mar 2023 00:22:09 -0700 Message-Id: <20230324072218.181880-1-irogers@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.40.0.348.gf938b09366-goog Subject: [PATCH v3 0/9] Update Intel events and make nvdimm events dynamic From: Ian Rogers To: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Zhengjun Xing , Kan Liang , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, Edward Baker , Dan Williams , perry.taylor@intel.com, caleb.biggers@intel.com, samantha.alt@intel.com, weilin.wang@intel.com Cc: Ian Rogers Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-perf-users@vger.kernel.org Update events from: https://github.com/intel/perfmon/pull/62 Add new #has_pmem literal to allow memory metrics to be dynamic in how nvdimm events are enabled. Update CLX, ICX and SPR for this using this PR: https://github.com/intel/perfmon/pull/63 v3. Change has_optane to has_pmem as suggested by Kan Liang and Dan Williams. Ian Rogers (9): perf vendor events: Broadwell v27 events perf vendor events: Broadwellde v9 events perf vendor events: Broadwellx v20 events perf vendor events: Haswell v33 events perf vendor events: Haswellx v27 events perf vendor events: Jaketown v23 events perf vendor events: Sandybridge v19 events perf metrics: Add has_pmem literal perf vendor events: Update metrics to detect pmem at runtime .../pmu-events/arch/x86/broadwell/cache.json | 296 +++++----- .../arch/x86/broadwell/floating-point.json | 7 + .../arch/x86/broadwell/frontend.json | 18 +- .../pmu-events/arch/x86/broadwell/memory.json | 248 ++++----- .../arch/x86/broadwell/pipeline.json | 22 +- .../arch/x86/broadwell/uncore-other.json | 2 +- .../arch/x86/broadwellde/cache.json | 105 ++-- .../arch/x86/broadwellde/floating-point.json | 45 +- .../arch/x86/broadwellde/frontend.json | 18 +- .../arch/x86/broadwellde/memory.json | 64 ++- .../arch/x86/broadwellde/pipeline.json | 79 +-- .../arch/x86/broadwellde/uncore-cache.json | 72 +-- .../arch/x86/broadwellde/uncore-memory.json | 256 ++++++++- .../arch/x86/broadwellde/uncore-other.json | 27 +- .../arch/x86/broadwellde/uncore-power.json | 10 +- .../pmu-events/arch/x86/broadwellx/cache.json | 16 +- .../arch/x86/broadwellx/frontend.json | 18 +- .../arch/x86/broadwellx/pipeline.json | 20 +- .../arch/x86/broadwellx/uncore-cache.json | 156 ++---- .../x86/broadwellx/uncore-interconnect.json | 84 +-- .../arch/x86/broadwellx/uncore-memory.json | 522 +++++++++--------- .../arch/x86/broadwellx/uncore-other.json | 44 +- .../arch/x86/broadwellx/uncore-power.json | 10 +- .../arch/x86/cascadelakex/clx-metrics.json | 10 +- .../pmu-events/arch/x86/haswell/cache.json | 38 +- .../pmu-events/arch/x86/haswell/memory.json | 38 +- .../pmu-events/arch/x86/haswell/pipeline.json | 8 + .../pmu-events/arch/x86/haswellx/cache.json | 2 +- .../arch/x86/haswellx/pipeline.json | 8 + .../arch/x86/haswellx/uncore-cache.json | 16 +- .../arch/x86/haswellx/uncore-other.json | 6 +- .../arch/x86/icelakex/icx-metrics.json | 10 +- .../arch/x86/jaketown/pipeline.json | 8 + tools/perf/pmu-events/arch/x86/mapfile.csv | 14 +- .../arch/x86/sandybridge/pipeline.json | 8 + .../arch/x86/sapphirerapids/spr-metrics.json | 10 +- tools/perf/util/expr.c | 19 + 37 files changed, 1323 insertions(+), 1011 deletions(-) -- 2.40.0.348.gf938b09366-goog