All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janne Kulmala <janne.t.kulmala@tut.fi>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Frans Pop <elendil@planet.nl>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	len.brown@intel.com, mingo@elte.hu, johnstul@us.ibm.com
Subject: Re: [PATCH] ACPI: do not mark TSC unstable for invalid C-states
Date: Mon, 11 May 2009 19:43:17 +0300	[thread overview]
Message-ID: <4A0855A5.8040109@tut.fi> (raw)
In-Reply-To: <alpine.LFD.2.00.0905111614570.3561@localhost.localdomain>

Thomas Gleixner wrote:
> commit a71e4917dc0ebbcb5a0ecb7ca3486643c1c9a6e2 (ACPI: idle:
> mark_tsc_unstable() at init-time, not run-time) marks TSC unstable
> even on non affected systems.
> 
> The reason is that the state enumeration does not check the cx->valid
> flag before calling tsc_halts_in_c(), so it marks TSC unstable for any
> enumerated albeit invalid C state which is known to turn off TSC.
> 
> Check cx->valid before checking whether the TSC might become unstable.
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
>  drivers/acpi/processor_idle.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: linux-2.6/drivers/acpi/processor_idle.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/processor_idle.c
> +++ linux-2.6/drivers/acpi/processor_idle.c
> @@ -583,7 +583,7 @@ static int acpi_processor_power_verify(s
>  
>  #if defined (CONFIG_GENERIC_TIME) && defined (CONFIG_X86)
>  		/* TSC could halt in idle, so notify users */
> -		if (tsc_halts_in_c(cx->type))
> +		if (cx->valid && tsc_halts_in_c(cx->type))
>  			mark_tsc_unstable("TSC halts in idle");;

Small suggestion: can we fix the double ';' here at the same time?

>  #endif
>  		switch (cx->type) {
> 
> 

Janne

  parent reply	other threads:[~2009-05-11 20:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  4:14 regression in TSC unstable? Steven Rostedt
2009-05-08  5:21 ` Len Brown
2009-05-08 12:07   ` Ingo Molnar
2009-05-11  0:26 ` Regression in TSC unstable -- confirmed Frans Pop
2009-05-11 14:22   ` [PATCH] ACPI: do not mark TSC unstable for invalid C-states Thomas Gleixner
2009-05-11 15:00     ` Steven Rostedt
2009-05-11 15:03     ` Frans Pop
2009-05-11 16:43     ` Janne Kulmala [this message]
2009-05-14 19:46       ` Len Brown
2009-05-14 20:09         ` Len Brown
2009-05-14 20:19           ` Thomas Gleixner
2009-05-14 21:55             ` [PATCH] ACPI: idle: fix init-time TSC check regression Len Brown
2009-05-14 22:27               ` Thomas Gleixner
2009-05-15  3:36                 ` Len Brown
2009-05-14 22:31               ` Frans Pop
2009-05-15  5:40               ` [PATCH] ACPI: Idle C-states disabled by max_cstate should not disable the TSC Len Brown
2009-05-15  6:18                 ` [PATCH] ACPI: idle: rename lapic timer workaround routines Len Brown
2009-05-15  8:28                   ` Thomas Gleixner
2009-05-15  8:27                 ` [PATCH] ACPI: Idle C-states disabled by max_cstate should not disable the TSC Thomas Gleixner
2009-05-15 10:57               ` [PATCH] ACPI: idle: fix init-time TSC check regression Frans Pop

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=4A0855A5.8040109@tut.fi \
    --to=janne.t.kulmala@tut.fi \
    --cc=elendil@planet.nl \
    --cc=johnstul@us.ibm.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.