mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>, H Peter Anvin <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Len Brown <len.brown@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] x86/mcheck/therm_throt.c: Don't log power limit and package level thermal throttle event in mce log
Date: Mon, 5 Dec 2011 14:18:25 +0100	[thread overview]
Message-ID: <20111205131825.GA31275@gere.osrc.amd.com> (raw)
In-Reply-To: <1321305082-31310-1-git-send-email-fenghua.yu@intel.com>

This looks like a sane improvement, Tony I'm assuming you're handling this?

On Mon, Nov 14, 2011 at 01:11:22PM -0800, Fenghua Yu wrote:
> From: Fenghua Yu <fenghua.yu@intel.com>
> 
> Because of BIOS issues, some platforms report mce errors after power limit and
> thermal throttle events. Customers are concerned about the mce errors. Although
> BIOS need to fix the issues eventually, the events should not be viewed as mce
> errors in the first place.
> 
> This patch doesn't log power limit and package level thermal throttle events
> in mce log. When the events happen, only count them in respective counters in
> sysfs.
> 
> For legacy reason, core level thermal throttle is still logged in mce log and
> counted in counter in sysfs.
> 
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> ---
>  arch/x86/kernel/cpu/mcheck/therm_throt.c |   29 +++++++----------------------
>  1 files changed, 7 insertions(+), 22 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/mcheck/therm_throt.c b/arch/x86/kernel/cpu/mcheck/therm_throt.c
> index 787e06c..ce04b58 100644
> --- a/arch/x86/kernel/cpu/mcheck/therm_throt.c
> +++ b/arch/x86/kernel/cpu/mcheck/therm_throt.c
> @@ -323,17 +323,6 @@ device_initcall(thermal_throttle_init_device);
>  
>  #endif /* CONFIG_SYSFS */
>  
> -/*
> - * Set up the most two significant bit to notify mce log that this thermal
> - * event type.
> - * This is a temp solution. May be changed in the future with mce log
> - * infrasture.
> - */
> -#define CORE_THROTTLED		(0)
> -#define CORE_POWER_LIMIT	((__u64)1 << 62)
> -#define PACKAGE_THROTTLED	((__u64)2 << 62)
> -#define PACKAGE_POWER_LIMIT	((__u64)3 << 62)
> -
>  static void notify_thresholds(__u64 msr_val)
>  {
>  	/* check whether the interrupt handler is defined;
> @@ -363,27 +352,23 @@ static void intel_thermal_interrupt(void)
>  	if (therm_throt_process(msr_val & THERM_STATUS_PROCHOT,
>  				THERMAL_THROTTLING_EVENT,
>  				CORE_LEVEL) != 0)
> -		mce_log_therm_throt_event(CORE_THROTTLED | msr_val);
> +		mce_log_therm_throt_event(msr_val);
>  
>  	if (this_cpu_has(X86_FEATURE_PLN))
> -		if (therm_throt_process(msr_val & THERM_STATUS_POWER_LIMIT,
> +		therm_throt_process(msr_val & THERM_STATUS_POWER_LIMIT,
>  					POWER_LIMIT_EVENT,
> -					CORE_LEVEL) != 0)
> -			mce_log_therm_throt_event(CORE_POWER_LIMIT | msr_val);
> +					CORE_LEVEL);
>  
>  	if (this_cpu_has(X86_FEATURE_PTS)) {
>  		rdmsrl(MSR_IA32_PACKAGE_THERM_STATUS, msr_val);
> -		if (therm_throt_process(msr_val & PACKAGE_THERM_STATUS_PROCHOT,
> +		therm_throt_process(msr_val & PACKAGE_THERM_STATUS_PROCHOT,
>  					THERMAL_THROTTLING_EVENT,
> -					PACKAGE_LEVEL) != 0)
> -			mce_log_therm_throt_event(PACKAGE_THROTTLED | msr_val);
> +					PACKAGE_LEVEL);
>  		if (this_cpu_has(X86_FEATURE_PLN))
> -			if (therm_throt_process(msr_val &
> +			therm_throt_process(msr_val &
>  					PACKAGE_THERM_STATUS_POWER_LIMIT,
>  					POWER_LIMIT_EVENT,
> -					PACKAGE_LEVEL) != 0)
> -				mce_log_therm_throt_event(PACKAGE_POWER_LIMIT
> -							  | msr_val);
> +					PACKAGE_LEVEL);
>  	}
>  }
>  
> -- 
> 1.6.0.3
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2011-12-05 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 21:11 Fenghua Yu
2011-12-05 13:18 ` Borislav Petkov [this message]
2011-12-05 22:18   ` Luck, Tony
2011-12-06 15:31     ` Borislav Petkov
2011-12-06 17:48       ` Yu, Fenghua
2011-12-06 19:06         ` Borislav Petkov
2011-12-06 19:26           ` Tony Luck
2011-12-06 19:56             ` Borislav Petkov
2011-12-06 19:27           ` Yu, Fenghua

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=20111205131825.GA31275@gere.osrc.amd.com \
    --to=bp@amd64.org \
    --cc=akpm@linux-foundation.org \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@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

Powered by JetHome