Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1380870rwb; Wed, 14 Dec 2022 09:27:52 -0800 (PST) X-Google-Smtp-Source: AA0mqf7nZe0f6VB+MuDlboEqDQFQF6b3O3HQNd4EP3soXv8exba1vlTgpU5h9B3DrZQ4YrzcQpqU X-Received: by 2002:a17:90a:8a8a:b0:219:dc24:7595 with SMTP id x10-20020a17090a8a8a00b00219dc247595mr25471330pjn.19.1671038872572; Wed, 14 Dec 2022 09:27:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671038872; cv=none; d=google.com; s=arc-20160816; b=PW8HAaY0M7fO5rTNhzP7k9oETQaQl/A/Zr2NNRpqBlXNAshkqDpXzMcr7jOwGiU46Y ba+4s18f1YP5uXQhXOgN73GIfR1FWEscL5mZp3ZRSTMiIpXNN2X1lo4eFAQUE5GVkAyb brkfjLIg8xzrUustzHHpLL9YNmTFxhcf3078ONV0XugUFe9Ufit9sJt3EzcyQsYuiNkN KODMJ4bYWnAj3Dky45TcI/92eDDFAB9FsdJC8MiLUZOUgksd+q1X2H8eeexyfusowv9D cC77PyyA0ZO0ykeoulENDMSh9LAWkqFDglffZIERX7hFGW/m1zynQJpTPZLAmL3AsseF vAJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:message-id:mime-version:date :dkim-signature; bh=w7oQvbAJgsoOmtULmkMdeiEDs6Dmo2nAnuZLG7TfGBQ=; b=OHnfAlurOu2qgPWX0IxW1VtVLhRmp9pa8VEGcpsbH4C0GeKjNGisujJ0Od6R+KHkaG gqwnENfCojcgH7scEhb5w7g7jWXl4asAWw+dOP0IoWlnH6t6oOGuR3zmwx9XP95wTI7E YVxPyhNtAU10IBetDvFUzgyWwhv2nJs79SEjyP7LmSF2+paLVdAydhi4SZLgmnzagj7x TCftYWKTia15eV1mFVhZ88ICe/5AevfhAWhclBYr4HLDwggEbxeDD7C7ClosqCwkVCFI oDuaL9ISgcj1kncoMQGK43EBpshlQdPAKPHEkGd+q8KU2p4lCMWuzVRZF3y8wQZ9kDXL oEqA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=QW6ivnix; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g14-20020a65580e000000b00478c967a84esi238765pgr.748.2022.12.14.09.27.43; Wed, 14 Dec 2022 09:27:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=QW6ivnix; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238712AbiLNQJV (ORCPT + 69 others); Wed, 14 Dec 2022 11:09:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238407AbiLNQJT (ORCPT ); Wed, 14 Dec 2022 11:09:19 -0500 Received: from mail-wr1-x449.google.com (mail-wr1-x449.google.com [IPv6:2a00:1450:4864:20::449]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A39D7F57 for ; Wed, 14 Dec 2022 08:09:18 -0800 (PST) Received: by mail-wr1-x449.google.com with SMTP id r17-20020adfb1d1000000b002421ae7fd46so39026wra.10 for ; Wed, 14 Dec 2022 08:09:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:mime-version:date:from:to:cc:subject :date:message-id:reply-to; bh=w7oQvbAJgsoOmtULmkMdeiEDs6Dmo2nAnuZLG7TfGBQ=; b=QW6ivnixs8SD8vSnGu+DMuMjtIS7ZkExXQk539lwR4AMJNJHfYG9V14bXHHRE4BM2x IMFtpP8XdWZw6ORRVL4yOc01HJ9DQiobnNl5roxjCFv2p5K6LB5MB1LTmTpTg+dzUTBV fNSc6beGhwYN9tsX4WUs7Ve+5sNq4BlbH07KAPyl0ImelUqXnF6/FjUs229HMBv7KPs/ IANBlGz1vBDFB83lvgQdAohKVSFH1N3lC/gB8oqf5EcMW2MNe6Lzd6tz5SX76hDOdjHp CA1UihAbnMDBCgSazwFa08vByCZc+JhgEI2XYATBGJTGiNYEZiYq9fhYfH+6Jm/c9nvq O+mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:mime-version:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=w7oQvbAJgsoOmtULmkMdeiEDs6Dmo2nAnuZLG7TfGBQ=; b=Im1PKDgFbgBoSBl4ZOFoRBjF+Xvn5JyqyeBEuLganrGDnvbLjASm9+MX/MbOsr1sng 4orGEuk+nuTLSYvU/DWDFX9ICqCN2jAt5nq5YB49aSdWGQNJFrYStdmeb1etc995lTNr aiYoDrQpgHkJuh+oVoLcA8ijdHDmQIQ7G7vCP9FIj6pWsAXO5rbwxF2Y/72Bjsxf4Dl/ 9BSaMtxLTisNfKwSay8X4P8vRCcE/10Jrga9VPJ3fTkGMdv9CTHuEHy3I+/8Y6Xl6Dpn eSPyp8VqCP2ee/fbsJ4WRVzUDYq0ywUmBUrH6TNpyGjSFTHtRQ/FVKaKovOdEdHH9ZWl zluA== X-Gm-Message-State: ANoB5pnuNEpHx9zMeSwPFSv071l6+R4Q93q0uauE/M26GTs8h3VTtU4p LeG/ph5NaN9mcTugZauyJIUmorjXL9kfxg0fPw== X-Received: from peternewman-vh.c.googlers.com ([fda3:e722:ac3:cc00:28:9cb1:c0a8:30cc]) (user=peternewman job=sendgmr) by 2002:a7b:ce85:0:b0:3d1:f143:c062 with SMTP id q5-20020a7bce85000000b003d1f143c062mr225183wmj.128.1671034157185; Wed, 14 Dec 2022 08:09:17 -0800 (PST) Date: Wed, 14 Dec 2022 17:08:55 +0100 Mime-Version: 1.0 X-Mailer: git-send-email 2.39.0.rc1.256.g54fd8350bd-goog Message-ID: <20221214160856.2164207-1-peternewman@google.com> Subject: [PATCH v2 1/2] x86/resctrl: Fix event counts regression in reused RMIDs From: Peter Newman To: reinette.chatre@intel.com, fenghua.yu@intel.com Cc: Babu.Moger@amd.com, bp@alien8.de, dave.hansen@linux.intel.com, eranian@google.com, hpa@zytor.com, james.morse@arm.com, linux-kernel@vger.kernel.org, mingo@redhat.com, quic_jiles@quicinc.com, tan.shaopeng@fujitsu.com, tglx@linutronix.de, x86@kernel.org, Peter Newman Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=ham 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 When creating a new monitoring group, the RMID allocated for it may have been used by a group which was previously removed. In this case, the hardware counters will have non-zero values which should be deducted from what is reported in the new group's counts. resctrl_arch_reset_rmid() initializes the prev_msr value for counters to 0, causing the initial count to be charged to the new group. Resurrect __rmid_read() and use it to initialize prev_msr correctly. Unlike before, __rmid_read() checks for error bits in the MSR read so that callers don't need to. Fixes: 1d81d15db39c ("x86/resctrl: Move mbm_overflow_count() into resctrl_arch_rmid_read()") Signed-off-by: Peter Newman --- arch/x86/kernel/cpu/resctrl/monitor.c | 49 ++++++++++++++++++--------- 1 file changed, 33 insertions(+), 16 deletions(-) diff --git a/arch/x86/kernel/cpu/resctrl/monitor.c b/arch/x86/kernel/cpu/resctrl/monitor.c index efe0c30d3a12..77538abeb72a 100644 --- a/arch/x86/kernel/cpu/resctrl/monitor.c +++ b/arch/x86/kernel/cpu/resctrl/monitor.c @@ -146,6 +146,30 @@ static inline struct rmid_entry *__rmid_entry(u32 rmid) return entry; } +static int __rmid_read(u32 rmid, enum resctrl_event_id eventid, u64 *val) +{ + u64 msr_val; + + /* + * As per the SDM, when IA32_QM_EVTSEL.EvtID (bits 7:0) is configured + * with a valid event code for supported resource type and the bits + * IA32_QM_EVTSEL.RMID (bits 41:32) are configured with valid RMID, + * IA32_QM_CTR.data (bits 61:0) reports the monitored data. + * IA32_QM_CTR.Error (bit 63) and IA32_QM_CTR.Unavailable (bit 62) + * are error bits. + */ + wrmsr(MSR_IA32_QM_EVTSEL, eventid, rmid); + rdmsrl(MSR_IA32_QM_CTR, msr_val); + + if (msr_val & RMID_VAL_ERROR) + return -EIO; + if (msr_val & RMID_VAL_UNAVAIL) + return -EINVAL; + + *val = msr_val; + return 0; +} + static struct arch_mbm_state *get_arch_mbm_state(struct rdt_hw_domain *hw_dom, u32 rmid, enum resctrl_event_id eventid) @@ -172,8 +196,12 @@ void resctrl_arch_reset_rmid(struct rdt_resource *r, struct rdt_domain *d, struct arch_mbm_state *am; am = get_arch_mbm_state(hw_dom, rmid, eventid); - if (am) + if (am) { memset(am, 0, sizeof(*am)); + + /* Record any initial, non-zero count value. */ + __rmid_read(rmid, eventid, &am->prev_msr); + } } static u64 mbm_overflow_count(u64 prev_msr, u64 cur_msr, unsigned int width) @@ -191,25 +219,14 @@ int resctrl_arch_rmid_read(struct rdt_resource *r, struct rdt_domain *d, struct rdt_hw_domain *hw_dom = resctrl_to_arch_dom(d); struct arch_mbm_state *am; u64 msr_val, chunks; + int ret; if (!cpumask_test_cpu(smp_processor_id(), &d->cpu_mask)) return -EINVAL; - /* - * As per the SDM, when IA32_QM_EVTSEL.EvtID (bits 7:0) is configured - * with a valid event code for supported resource type and the bits - * IA32_QM_EVTSEL.RMID (bits 41:32) are configured with valid RMID, - * IA32_QM_CTR.data (bits 61:0) reports the monitored data. - * IA32_QM_CTR.Error (bit 63) and IA32_QM_CTR.Unavailable (bit 62) - * are error bits. - */ - wrmsr(MSR_IA32_QM_EVTSEL, eventid, rmid); - rdmsrl(MSR_IA32_QM_CTR, msr_val); - - if (msr_val & RMID_VAL_ERROR) - return -EIO; - if (msr_val & RMID_VAL_UNAVAIL) - return -EINVAL; + ret = __rmid_read(rmid, eventid, &msr_val); + if (ret) + return ret; am = get_arch_mbm_state(hw_dom, rmid, eventid); if (am) { base-commit: 830b3c68c1fb1e9176028d02ef86f3cf76aa2476 -- 2.39.0.rc1.256.g54fd8350bd-goog