Linux ACPI
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Len Brown <lenb@kernel.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Janne Kulmala <janne.t.kulmala@tut.fi>,
	Frans Pop <elendil@planet.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	johnstul@us.ibm.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: Idle C-states disabled by max_cstate should not disable the TSC
Date: Fri, 15 May 2009 10:27:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0905151027130.3561@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0905150138001.10065@localhost.localdomain>

On Fri, 15 May 2009, Len Brown wrote:

> From: Len Brown <len.brown@intel.com>
> 
> Processor idle power states C2 and C3 stop the TSC on many machines.
> Linux recognizes this situation and marks the TSC as unstable:
> 
> Marking TSC unstable due to TSC halts in idle
> 
> But if those same machines are booted with "processor.max_cstate=1",
> then there is no need to validate C2 and C3, and no need to
> disable the TSC, which can be reliably used as a clocksource.
> 
> Signed-off-by: Len Brown <len.brown@intel.com>

Acked-by: Thomas Gleixner <tglx@linutronix.de>

> ---
>  drivers/acpi/processor_idle.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index e39a40a..e65476f 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -582,7 +582,7 @@ static int acpi_processor_power_verify(struct acpi_processor *pr)
>  
>  	pr->power.timer_broadcast_on_state = INT_MAX;
>  
> -	for (i = 1; i < ACPI_PROCESSOR_MAX_POWER; i++) {
> +	for (i = 1; i < ACPI_PROCESSOR_MAX_POWER && i <= max_cstate; i++) {
>  		struct acpi_processor_cx *cx = &pr->power.states[i];
>  
>  		switch (cx->type) {
> -- 
> 1.6.3.1.9.g95405b
> 

      parent reply	other threads:[~2009-05-15  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.0905072359530.28378@gandalf.stny.rr.com>
     [not found] ` <200905110226.50115.elendil@planet.nl>
     [not found]   ` <alpine.LFD.2.00.0905111614570.3561@localhost.localdomain>
     [not found]     ` <4A0855A5.8040109@tut.fi>
     [not found]       ` <alpine.LFD.2.00.0905141545280.24833@localhost.localdomain>
     [not found]         ` <alpine.LFD.2.00.0905141608070.24833@localhost.localdomain>
     [not found]           ` <alpine.LFD.2.00.0905142217340.3561@localhost.localdomain>
     [not found]             ` <alpine.LFD.2.00.0905141750100.24833@localhost.localdomain>
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                 ` Thomas Gleixner [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=alpine.LFD.2.00.0905151027130.3561@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=elendil@planet.nl \
    --cc=janne.t.kulmala@tut.fi \
    --cc=johnstul@us.ibm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=venkatesh.pallipadi@intel.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