From: Zhang Rui <rui.zhang@intel.com>
To: Alexander Koskovich <zvnexus@gmail.com>,
arjan@linux.intel.com, jacob.jun.pan@linux.intel.com
Cc: Alexander Koskovich <zvnexus@outlook.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal/intel_powerclamp: Don't report an error for AMD CPUs
Date: Mon, 17 Feb 2020 15:59:34 +0800 [thread overview]
Message-ID: <19d5aad060442ca4917046286b82e723199d4088.camel@intel.com> (raw)
In-Reply-To: <20200215160938.1025-1-zvnexus@outlook.com>
On Sat, 2020-02-15 at 11:09 -0500, Alexander Koskovich wrote:
> Resolves dmesg error "intel_powerclamp: CPU does not support MWAIT".
>
> The error that is outputted in dmesg prior to this patch
> is innacurate, AMD Ryzen CPUs do support MWAIT. We could
> also add the AMD vendor to the MWAIT check, but even though
> AMD CPUs do support MWAIT, they fail the C-state package
> check so it's better just to bail out in the beginning.
>
> Signed-off-by: Alexander Koskovich <zvnexus@outlook.com>
I think you're resending the same patch.
As intel_powerclamp_ids already checks for Intel CPUs, so we don't need
the check for AMD CPU, but instead, just remove the following line
"pr_err("CPU does not support MWAIT\n");"
when intel_powerclamp driver fails to probe.
thanks,
rui
> ---
> drivers/thermal/intel/intel_powerclamp.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/thermal/intel/intel_powerclamp.c
> b/drivers/thermal/intel/intel_powerclamp.c
> index 53216dcbe173..3c5b25bfa596 100644
> --- a/drivers/thermal/intel/intel_powerclamp.c
> +++ b/drivers/thermal/intel/intel_powerclamp.c
> @@ -650,6 +650,11 @@ static struct thermal_cooling_device_ops
> powerclamp_cooling_ops = {
> .set_cur_state = powerclamp_set_cur_state,
> };
>
> +static const struct x86_cpu_id amd_cpu[] = {
> + { X86_VENDOR_AMD },
> + {},
> +};
> +
> static const struct x86_cpu_id __initconst intel_powerclamp_ids[] =
> {
> { X86_VENDOR_INTEL, X86_FAMILY_ANY, X86_MODEL_ANY,
> X86_FEATURE_MWAIT },
> {}
> @@ -659,6 +664,11 @@ MODULE_DEVICE_TABLE(x86cpu,
> intel_powerclamp_ids);
> static int __init powerclamp_probe(void)
> {
>
> + if (x86_match_cpu(amd_cpu)) {
> + pr_info("Intel PowerClamp does not support AMD
> CPUs\n");
> + return -ENODEV;
> + }
> +
> if (!x86_match_cpu(intel_powerclamp_ids)) {
> pr_err("CPU does not support MWAIT\n");
> return -ENODEV;
prev parent reply other threads:[~2020-02-17 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 16:09 Alexander Koskovich
2020-02-15 11:58 ` Thomas Gleixner
2020-02-17 7:59 ` Zhang Rui [this message]
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=19d5aad060442ca4917046286b82e723199d4088.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=amit.kucheria@verdurent.com \
--cc=arjan@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=zvnexus@gmail.com \
--cc=zvnexus@outlook.com \
/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®