From: "tip-bot2 for Maxim Levitsky" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Maxim Levitsky <mlevitsk@redhat.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Kan Liang <kan.liang@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/urgent] perf/x86/intel/lbr: Use setup_clear_cpu_cap() instead of clear_cpu_cap()
Date: Thu, 20 Oct 2022 15:17:56 -0000 [thread overview]
Message-ID: <166627907623.401.782680400478591314.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220718141123.136106-2-mlevitsk@redhat.com>
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: b329f5ddc9ce4b622d9c7aaf5c6df4de52caf91a
Gitweb: https://git.kernel.org/tip/b329f5ddc9ce4b622d9c7aaf5c6df4de52caf91a
Author: Maxim Levitsky <mlevitsk@redhat.com>
AuthorDate: Mon, 18 Jul 2022 17:11:19 +03:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Thu, 20 Oct 2022 17:10:28 +02:00
perf/x86/intel/lbr: Use setup_clear_cpu_cap() instead of clear_cpu_cap()
clear_cpu_cap(&boot_cpu_data) is very similar to setup_clear_cpu_cap()
except that the latter also sets a bit in 'cpu_caps_cleared' which
later clears the same cap in secondary cpus, which is likely what is
meant here.
Fixes: 47125db27e47 ("perf/x86/intel/lbr: Support Architectural LBR")
Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Link: https://lkml.kernel.org/r/20220718141123.136106-2-mlevitsk@redhat.com
---
arch/x86/events/intel/lbr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/events/intel/lbr.c b/arch/x86/events/intel/lbr.c
index 4fce1a4..8259d72 100644
--- a/arch/x86/events/intel/lbr.c
+++ b/arch/x86/events/intel/lbr.c
@@ -1596,7 +1596,7 @@ void __init intel_pmu_arch_lbr_init(void)
return;
clear_arch_lbr:
- clear_cpu_cap(&boot_cpu_data, X86_FEATURE_ARCH_LBR);
+ setup_clear_cpu_cap(X86_FEATURE_ARCH_LBR);
}
/**
next prev parent reply other threads:[~2022-10-20 15:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 14:11 [PATCH v2 0/5] x86: cpuid: improve support for broken CPUID configurations Maxim Levitsky
2022-07-18 14:11 ` [PATCH v2 1/5] perf/x86/intel/lbr: use setup_clear_cpu_cap instead of clear_cpu_cap Maxim Levitsky
2022-09-19 14:31 ` Borislav Petkov
2022-09-20 8:20 ` Maxim Levitsky
2022-09-26 13:12 ` Borislav Petkov
2022-09-28 10:49 ` Maxim Levitsky
2022-10-20 8:59 ` Borislav Petkov
2022-10-20 9:05 ` Herbert Xu
2022-10-20 10:21 ` Maxim Levitsky
2022-10-20 11:13 ` Borislav Petkov
2022-10-22 21:08 ` H. Peter Anvin
2022-11-02 13:40 ` Paolo Bonzini
2022-11-02 14:27 ` Elliott, Robert (Servers)
2022-11-02 16:23 ` H. Peter Anvin
2022-11-02 18:19 ` H. Peter Anvin
2022-11-02 19:14 ` Elliott, Robert (Servers)
2022-11-03 13:26 ` Paolo Bonzini
2022-11-03 13:30 ` Paolo Bonzini
2022-10-20 15:17 ` tip-bot2 for Maxim Levitsky [this message]
2022-07-18 14:11 ` [PATCH v2 2/5] x86/cpuid: refactor setup_clear_cpu_cap()/clear_cpu_cap() Maxim Levitsky
2022-10-21 16:19 ` Borislav Petkov
2022-11-07 19:10 ` Borislav Petkov
2022-11-07 21:57 ` Borislav Petkov
2022-07-18 14:11 ` [PATCH v2 3/5] x86/cpuid: move filter_cpuid_features to cpuid-deps.c Maxim Levitsky
2022-07-18 14:11 ` [PATCH v2 4/5] x86/cpuid: remove 'warn' parameter from filter_cpuid_features Maxim Levitsky
2022-07-18 14:11 ` [PATCH v2 5/5] x86/cpuid: check for dependencies violations in CPUID and attempt to fix them Maxim Levitsky
2022-07-28 7:30 ` [PATCH v2 0/5] x86: cpuid: improve support for broken CPUID configurations Maxim Levitsky
2022-08-01 16:05 ` Maxim Levitsky
2022-08-01 16:31 ` Dave Hansen
2022-08-01 16:41 ` Maxim Levitsky
2022-09-19 13:43 ` Maxim Levitsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166627907623.401.782680400478591314.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).