From: Borislav Petkov <bp@suse.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
kitsunyan <kitsunyan@airmail.cc>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/msr: do not warn on writes to OC_MAILBOX
Date: Mon, 7 Sep 2020 12:06:47 +0200 [thread overview]
Message-ID: <20200907100647.GB10657@zn.tnic> (raw)
In-Reply-To: <20200907094843.1949-1-Jason@zx2c4.com>
+ Srinivas.
+ kitsunyan.
On Mon, Sep 07, 2020 at 11:48:43AM +0200, Jason A. Donenfeld wrote:
> Popular tools, like intel-undervolt, use MSR 0x150 to control the CPU
> voltage offset. In fact, evidently the intel_turbo_max_3 driver in-tree
> also uses this MSR. So, teach the kernel's MSR list about this, so that
> intel-undervolt and other such tools don't spew warnings to dmesg, while
> unifying the constant used throughout the kernel.
>
> Fixes: a7e1f67ed29f ("x86/msr: Filter MSR writes")
> Cc: Borislav Petkov <bp@suse.de>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> arch/x86/include/asm/msr-index.h | 2 ++
> arch/x86/kernel/msr.c | 5 ++++-
> drivers/platform/x86/intel_turbo_max_3.c | 6 +++---
> 3 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/include/asm/msr-index.h b/arch/x86/include/asm/msr-index.h
> index 2859ee4f39a8..0bcb3604d0e2 100644
> --- a/arch/x86/include/asm/msr-index.h
> +++ b/arch/x86/include/asm/msr-index.h
> @@ -132,6 +132,8 @@
> #define MSR_IA32_MCU_OPT_CTRL 0x00000123
> #define RNGDS_MITG_DIS BIT(0)
>
> +#define MSR_IA32_OC_MAILBOX 0x00000150
> +
> #define MSR_IA32_SYSENTER_CS 0x00000174
> #define MSR_IA32_SYSENTER_ESP 0x00000175
> #define MSR_IA32_SYSENTER_EIP 0x00000176
> diff --git a/arch/x86/kernel/msr.c b/arch/x86/kernel/msr.c
> index 49dcfb85e773..64f6200681e3 100644
> --- a/arch/x86/kernel/msr.c
> +++ b/arch/x86/kernel/msr.c
> @@ -86,8 +86,11 @@ static int filter_write(u32 reg)
> default: break;
> }
>
> - if (reg == MSR_IA32_ENERGY_PERF_BIAS)
> + switch (reg) {
> + case MSR_IA32_ENERGY_PERF_BIAS:
> + case MSR_IA32_OC_MAILBOX:
> return 0;
> + }
>
> pr_err_ratelimited("Write to unrecognized MSR 0x%x by %s\n"
> "Please report to x86@kernel.org\n",
> diff --git a/drivers/platform/x86/intel_turbo_max_3.c b/drivers/platform/x86/intel_turbo_max_3.c
> index 892140b62898..991cdbc3295b 100644
> --- a/drivers/platform/x86/intel_turbo_max_3.c
> +++ b/drivers/platform/x86/intel_turbo_max_3.c
> @@ -17,8 +17,8 @@
>
> #include <asm/cpu_device_id.h>
> #include <asm/intel-family.h>
> +#include <asm/msr.h>
>
> -#define MSR_OC_MAILBOX 0x150
> #define MSR_OC_MAILBOX_CMD_OFFSET 32
> #define MSR_OC_MAILBOX_RSP_OFFSET 32
> #define MSR_OC_MAILBOX_BUSY_BIT 63
> @@ -41,14 +41,14 @@ static int get_oc_core_priority(unsigned int cpu)
> value = cmd << MSR_OC_MAILBOX_CMD_OFFSET;
> /* Set the busy bit to indicate OS is trying to issue command */
> value |= BIT_ULL(MSR_OC_MAILBOX_BUSY_BIT);
> - ret = wrmsrl_safe(MSR_OC_MAILBOX, value);
> + ret = wrmsrl_safe(MSR_IA32_OC_MAILBOX, value);
> if (ret) {
> pr_debug("cpu %d OC mailbox write failed\n", cpu);
> return ret;
> }
>
> for (i = 0; i < OC_MAILBOX_RETRY_COUNT; ++i) {
> - ret = rdmsrl_safe(MSR_OC_MAILBOX, &value);
> + ret = rdmsrl_safe(MSR_IA32_OC_MAILBOX, &value);
> if (ret) {
> pr_debug("cpu %d OC mailbox read failed\n", cpu);
> break;
> --
Actually, we added the filtering to catch exactly such misuses and,
lemme check what is the proper word now... /me checks, aha, adding new
MSRs to the "passlist" is the wrong thing to do.
Srinivas, can you pls convert this in-tree driver to use a proper sysfs
interface for that mailbox MSR and also work with the intel-undervolt
author - I hope I have the right person CCed from the git repo on github
- to come up with a proper interface so that we can drop this MSR use
too.
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2020-09-07 10:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 9:48 Jason A. Donenfeld
2020-09-07 10:06 ` Borislav Petkov [this message]
2020-09-07 10:46 ` Jason A. Donenfeld
2020-09-07 11:11 ` Borislav Petkov
2020-09-07 11:15 ` Jason A. Donenfeld
2020-09-07 11:23 ` Borislav Petkov
2020-09-08 17:10 ` Srinivas Pandruvada
2020-09-08 17:12 ` Jason A. Donenfeld
2020-09-08 17:25 ` Borislav Petkov
2020-09-08 17:29 ` Jason A. Donenfeld
2020-09-08 17:36 ` Borislav Petkov
2020-09-08 17:42 ` Jason A. Donenfeld
2020-09-08 18:01 ` Borislav Petkov
2020-09-08 19:07 ` Jason A. Donenfeld
2020-09-08 19:18 ` Sultan Alsawaf
2020-09-08 19:30 ` Borislav Petkov
2020-09-08 20:35 ` Andy Lutomirski
2020-09-08 22:32 ` Matthew Garrett
2020-09-09 23:56 ` Andy Lutomirski
2020-09-09 1:02 ` Srinivas Pandruvada
2020-09-10 0:08 ` Andy Lutomirski
2020-10-19 17:15 ` Borislav Petkov
2020-10-20 17:21 ` Srinivas Pandruvada
2020-10-20 17:47 ` Borislav Petkov
2020-10-20 18:40 ` Srinivas Pandruvada
2020-10-20 19:40 ` Dave Hansen
2020-10-21 13:11 ` Srinivas Pandruvada
2020-10-22 19:28 ` Borislav Petkov
2020-10-21 13:24 ` Peter Zijlstra
2020-09-08 17:31 ` Borislav Petkov
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=20200907100647.GB10657@zn.tnic \
--to=bp@suse.de \
--cc=Jason@zx2c4.com \
--cc=kitsunyan@airmail.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--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
all inboxes | Powered by JetHome®