public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] ACPI: Kill overly verbose "power state" log messages
@ 2009-09-24 21:52 Roland Dreier
  2009-09-25  0:46 ` ykzhao
  0 siblings, 1 reply; 4+ messages in thread
From: Roland Dreier @ 2009-09-24 21:52 UTC (permalink / raw)
  To: Len Brown; +Cc: linux-kernel, linux-acpi

I was recently lucky enough to get a 64-CPU system.  The processors
actually have T-states, so my kernel log ends up with 64 lines like:

    ACPI: CPU0 (power states: C1[C1] C2[C3])

This is pretty useless clutter because this info is already available
after boot from both /sys/devices/system/cpu/cpu*/cpuidle/state?/ as
well as /proc/acpi/processor/CPU*/power.

So just delete the code that prints the throttling states in
processor_idle.c.

Signed-off-by: Roland Dreier <rolandd@cisco.com>
---
 drivers/acpi/processor_idle.c |    7 -------
 1 files changed, 0 insertions(+), 7 deletions(-)

diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index cc61a62..706eacf 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -1214,13 +1214,6 @@ int __cpuinit acpi_processor_power_init(struct acpi_processor *pr,
 		acpi_processor_setup_cpuidle(pr);
 		if (cpuidle_register_device(&pr->power.dev))
 			return -EIO;
-
-		printk(KERN_INFO PREFIX "CPU%d (power states:", pr->id);
-		for (i = 1; i <= pr->power.count; i++)
-			if (pr->power.states[i].valid)
-				printk(" C%d[C%d]", i,
-				       pr->power.states[i].type);
-		printk(")\n");
 	}
 #ifdef CONFIG_ACPI_PROCFS
 	/* 'power' [R] */

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] ACPI: Kill overly verbose "power state" log messages
  2009-09-24 21:52 [PATCH] ACPI: Kill overly verbose "power state" log messages Roland Dreier
@ 2009-09-25  0:46 ` ykzhao
  2009-09-25 16:01   ` Roland Dreier
  0 siblings, 1 reply; 4+ messages in thread
From: ykzhao @ 2009-09-25  0:46 UTC (permalink / raw)
  To: Roland Dreier
  Cc: Len Brown, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org

On Fri, 2009-09-25 at 05:52 +0800, Roland Dreier wrote:
> I was recently lucky enough to get a 64-CPU system.  The processors
> actually have T-states, so my kernel log ends up with 64 lines like:
> 
>     ACPI: CPU0 (power states: C1[C1] C2[C3])
> 
> This is pretty useless clutter because this info is already available
> after boot from both /sys/devices/system/cpu/cpu*/cpuidle/state?/ as
> well as /proc/acpi/processor/CPU*/power.
> 
> So just delete the code that prints the throttling states in
> processor_idle.c.
It seems that it is unnecessary to delete the C-state info.
Thanks.
> 
> Signed-off-by: Roland Dreier <rolandd@cisco.com>
> ---
>  drivers/acpi/processor_idle.c |    7 -------
>  1 files changed, 0 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index cc61a62..706eacf 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -1214,13 +1214,6 @@ int __cpuinit acpi_processor_power_init(struct acpi_processor *pr,
>  		acpi_processor_setup_cpuidle(pr);
>  		if (cpuidle_register_device(&pr->power.dev))
>  			return -EIO;
> -
> -		printk(KERN_INFO PREFIX "CPU%d (power states:", pr->id);
> -		for (i = 1; i <= pr->power.count; i++)
> -			if (pr->power.states[i].valid)
> -				printk(" C%d[C%d]", i,
> -				       pr->power.states[i].type);
> -		printk(")\n");
>  	}
>  #ifdef CONFIG_ACPI_PROCFS
>  	/* 'power' [R] */
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] ACPI: Kill overly verbose "power state" log messages
  2009-09-25  0:46 ` ykzhao
@ 2009-09-25 16:01   ` Roland Dreier
  2009-09-27  8:01     ` Len Brown
  0 siblings, 1 reply; 4+ messages in thread
From: Roland Dreier @ 2009-09-25 16:01 UTC (permalink / raw)
  To: ykzhao; +Cc: Len Brown, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org

Len, I see I messed up editing my changelog message, see below...

 > > I was recently lucky enough to get a 64-CPU system.  The processors
 > > actually have T-states, so my kernel log ends up with 64 lines like:
 > > 
 > >     ACPI: CPU0 (power states: C1[C1] C2[C3])
 > > 
 > > This is pretty useless clutter because this info is already available
 > > after boot from both /sys/devices/system/cpu/cpu*/cpuidle/state?/ as
 > > well as /proc/acpi/processor/CPU*/power.
 > > 
 > > So just delete the code that prints the throttling states in
 > > processor_idle.c.

 > It seems that it is unnecessary to delete the C-state info.

Sorry, this is a little too terse for me to know what you mean.
Certainly it's not useful to have 64 copies of

    ACPI: CPU0 (power states: C1[C1] C2[C3])

in the kernel log on a big box, when all 64 processors are going to
support the same C-states.  However, I don't see what the use of having
even one copy in the boot log is, when I can easily get that info at
runtime from /proc/acpi/processor/CPU*/power.


Anyway, Len, I see I copy-and-pasted too quickly from my T-state patch
submission... if you want to apply, a version with better changelog would be:

<--- snip --->

I was recently lucky enough to get a 64-CPU system, so my kernel log
ends up with 64 lines like:

    ACPI: CPU0 (power states: C1[C1] C2[C3])

This is pretty useless clutter because this info is already available
after boot from both /sys/devices/system/cpu/cpu*/cpuidle/state?/ as
well as /proc/acpi/processor/CPU*/power.

So just delete the code that prints the C-states in processor_idle.c.

Signed-off-by: Roland Dreier <rolandd@cisco.com>
---
 drivers/acpi/processor_idle.c |    7 -------
 1 files changed, 0 insertions(+), 7 deletions(-)

diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index cc61a62..706eacf 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -1214,13 +1214,6 @@ int __cpuinit acpi_processor_power_init(struct acpi_processor *pr,
 		acpi_processor_setup_cpuidle(pr);
 		if (cpuidle_register_device(&pr->power.dev))
 			return -EIO;
-
-		printk(KERN_INFO PREFIX "CPU%d (power states:", pr->id);
-		for (i = 1; i <= pr->power.count; i++)
-			if (pr->power.states[i].valid)
-				printk(" C%d[C%d]", i,
-				       pr->power.states[i].type);
-		printk(")\n");
 	}
 #ifdef CONFIG_ACPI_PROCFS
 	/* 'power' [R] */

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] ACPI: Kill overly verbose "power state" log messages
  2009-09-25 16:01   ` Roland Dreier
@ 2009-09-27  8:01     ` Len Brown
  0 siblings, 0 replies; 4+ messages in thread
From: Len Brown @ 2009-09-27  8:01 UTC (permalink / raw)
  To: Roland Dreier
  Cc: ykzhao, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org

> So just delete the code that prints the C-states in processor_idle.c.

applied

thanks,
Len Brown, Intel Open Source Technology Center


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-09-27  8:01 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-24 21:52 [PATCH] ACPI: Kill overly verbose "power state" log messages Roland Dreier
2009-09-25  0:46 ` ykzhao
2009-09-25 16:01   ` Roland Dreier
2009-09-27  8:01     ` Len Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox