From: Mike Travis <travis@sgi.com>
To: David Rientjes <rientjes@google.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Roland Dreier <rdreier@cisco.com>,
Randy Dunlap <rdunlap@xenotime.net>, Tejun Heo <tj@kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Yinghai Lu <yhlu.kernel@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Jack Steiner <steiner@sgi.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] ACPI: Limit the number of per cpu ACPI bootup messages
Date: Fri, 13 Nov 2009 05:53:51 -0800 [thread overview]
Message-ID: <4AFD64EF.20807@sgi.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0911121324280.17797@chino.kir.corp.google.com>
David Rientjes wrote:
> On Thu, 12 Nov 2009, Mike Travis wrote:
>
>>>> --- linux.orig/drivers/acpi/tables.c
>>>> +++ linux/drivers/acpi/tables.c
>>>> @@ -66,11 +66,15 @@
>>>> {
>>>> struct acpi_madt_local_x2apic *p =
>>>> (struct acpi_madt_local_x2apic *)header;
>>>> - printk(KERN_INFO PREFIX
>>>> - "X2APIC (apic_id[0x%02x] uid[0x%02x] %s)\n",
>>>> - p->local_apic_id, p->uid,
>>>> - (p->lapic_flags & ACPI_MADT_ENABLED) ?
>>>> - "enabled" : "disabled");
>>>> + /*
>>>> + * Per cpu tracing clogs console output when NR_CPUS
>>>> + * is large. Send only to kernel log buffer.
>>>> + */
>>>> + printk(KERN_DEBUG PREFIX
>>>> + "X2APIC (apic_id[0x%02x] uid[0x%02x] %s)\n",
>>>> + p->local_apic_id, p->uid,
>>>> + (p->lapic_flags & ACPI_MADT_ENABLED) ?
>>>> + "enabled" : "disabled");
>>>> }
>>>> break;
>>>>
>>> You can still use dev_dbg(PREFIX "...") here.
>> I thought dev_dbg needed the 'dev' structure and I wasn't sure how to get
>> that...?
>>
>
> Ah, ok, it needs to be pr_debug(PREFIX "...") then.
The primary reason I'm using KERN_DEBUG instead of pr_debug is that the
messages will end up in the log in the former case, so dmesg can print
them out, whether it's a DEBUG kernel or not. This helps diagnose problems
without requiring a reboot of a DEBUG kernel to reproduce a problem, which
often is not acceptable to many customers (security and system availability
being the primary concerns.)
> Any reason why the other printk's in acpi_table_print_madt_entry() weren't
> converted to use KERN_DEBUG? It might make more sense to convert all
> those to use a new acpi=verbose flag.
I thought of that, but the ACPI debug infrastructure is complex to understand,
and since I can't really test most cases, I wanted to tread lightly.
>
> I'm not sure if Ingo is the right person to go through for acpi patches, I
> think this should probably be submitted to Len Brown <lenb@kernel.org> and
> linux-acpi@vger.kernel.org instead.
I can do that.
Thanks,
Mike
next prev parent reply other threads:[~2009-11-13 13:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 17:19 [PATCH 0/7] Limit console output by suppressing repetitious messages Mike Travis
2009-11-12 17:19 ` [PATCH 1/7] x86: Limit the number of processor bootup messages Mike Travis
2009-11-12 18:09 ` Ingo Molnar
2009-11-12 20:05 ` Mike Travis
2009-11-13 9:52 ` Ingo Molnar
2009-11-13 13:43 ` Mike Travis
2009-11-12 22:10 ` Yinghai Lu
2009-11-13 13:46 ` Mike Travis
2009-11-13 21:58 ` Yinghai Lu
2009-11-12 17:19 ` [PATCH 2/7] ACPI: Limit the number of per cpu ACPI " Mike Travis
2009-11-12 21:02 ` David Rientjes
2009-11-12 21:19 ` Mike Travis
2009-11-12 21:28 ` David Rientjes
2009-11-13 13:53 ` Mike Travis [this message]
2009-11-12 17:19 ` [PATCH 3/7] INIT: Limit the number of per cpu INIT " Mike Travis
2009-11-12 21:06 ` David Rientjes
2009-11-12 21:20 ` Mike Travis
2009-11-12 17:19 ` [PATCH 4/7] firmware: Limit the number of per cpu firmware messages during bootup Mike Travis
2009-11-12 17:19 ` [PATCH 5/7] x86: Limit the number of per cpu MCE bootup messages Mike Travis
2009-11-12 17:19 ` [PATCH 6/7] sched: Limit the number of scheduler debug messages Mike Travis
2009-11-12 17:19 ` [PATCH 7/7] x86: Limit number of per cpu TSC sync messages Mike Travis
2009-11-12 20:48 ` [patch] x86: reduce srat verbosity in the kernel log David Rientjes
2009-11-13 9:53 ` Ingo Molnar
2009-11-13 10:02 ` David Rientjes
2009-11-13 10:13 ` Ingo Molnar
2009-11-13 10:29 ` David Rientjes
2009-11-13 10:57 ` Ingo Molnar
2009-11-20 18:37 ` Pavel Machek
2009-11-20 18:58 ` Mike Travis
2009-11-12 22:16 ` [PATCH 0/7] Limit console output by suppressing repetitious messages Yinghai Lu
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=4AFD64EF.20807@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdreier@cisco.com \
--cc=rdunlap@xenotime.net \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.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 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.