Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp4497895ybv; Mon, 17 Feb 2020 00:00:04 -0800 (PST) X-Google-Smtp-Source: APXvYqzqOCtJins2WCeFsbf+qnF+bwspPYUS7CyDpBSngaIoZqK/d9cnY9jAX43I64VJjfi5xR97 X-Received: by 2002:a05:6808:b29:: with SMTP id t9mr9174876oij.69.1581926404371; Mon, 17 Feb 2020 00:00:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581926404; cv=none; d=google.com; s=arc-20160816; b=uMe3vU6IPCOOQ6NjkEYSafXG8Nj4CTTQV/evUnB1avDH5c3l9VMdl0YiwYmV0zFy9b 4+Lz8Rwqhi+Xx6Bw9feHgs9Lt96drnFSKmQriOdP5nW1JGI29pZOCWhU4Vt/oXUL+iRp vjzM8E69XZ78ZUCxenuoqF3na9gHvulHh5rZ88hDL7CW1BjSaWkpaIR2vWccUrOOXl+5 /fm/iQAGQiyXg9moeULvAe1/vcEb0B+qqoV5BSqgWnGZFhsqhyGsv/H3VMZRNFd6eQhQ EjoqTJTzIUMDAufCiEK+C2bzXdr0GrfsRGMBirImDFOjYhMWAKWqmUv6dsm6UUk3DGKr NGlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=ukhRmLO0uDUj0sjVxTaRuEjBf4HSABfB5fyYym9+cHE=; b=GniLQJDqWl2YRzHwEpvXbhIe6kSfBetN2QFSV2iQw+n319zOdLH8muMH3yxJ172kdb gedUVd9c4vpFAhLR3SuU6hh/75GqZ1TxDbbmypkDemrGIp/uipsnri+ZKF5fnFgZqtcv L6ZgWttdWosx/jibq5+A9CB7Z4Cjos9uq/OsP8LAuqUpioW5ioDxSaYXMRk4iKQLRMnM KzH7SvBhfD8EkZmRCpZqhUpsd06zRJVdSj2WNCUDYzVSGy1mOLHjWP0ZYjP8ColQMsho zX0ho0Xi65GTHjNqK0GZMB9zv2Klazo5Dd8IkVwYtfi3XWr1WxCttrSoTbJoQGQO4E3o LMeQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j2si6969528otk.164.2020.02.16.23.59.52; Mon, 17 Feb 2020 00:00:04 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726977AbgBQH7j (ORCPT + 99 others); Mon, 17 Feb 2020 02:59:39 -0500 Received: from mga11.intel.com ([192.55.52.93]:16751 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726267AbgBQH7i (ORCPT ); Mon, 17 Feb 2020 02:59:38 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Feb 2020 23:59:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,451,1574150400"; d="scan'208";a="229120141" Received: from zhouy1-mobl1.ccr.corp.intel.com ([10.249.169.88]) by fmsmga008.fm.intel.com with ESMTP; 16 Feb 2020 23:59:35 -0800 Message-ID: <19d5aad060442ca4917046286b82e723199d4088.camel@intel.com> Subject: Re: [PATCH] thermal/intel_powerclamp: Don't report an error for AMD CPUs From: Zhang Rui To: Alexander Koskovich , arjan@linux.intel.com, jacob.jun.pan@linux.intel.com Cc: Alexander Koskovich , Daniel Lezcano , Amit Kucheria , Greg Kroah-Hartman , Luc Van Oostenryck , Petr Mladek , Thomas Gleixner , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Date: Mon, 17 Feb 2020 15:59:34 +0800 In-Reply-To: <20200215160938.1025-1-zvnexus@outlook.com> References: <20200215160938.1025-1-zvnexus@outlook.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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;