From: Joe Perches <joe@perches.com>
To: Youquan Song <youquan.song@intel.com>, Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, hpa@linux.intel.com,
suresh.b.siddha@intel.com, arjan@linux.intel.com, trenn@suse.de,
kent.liu@intel.com, chaohong.guo@intel.com,
Youquan Song <youquan.song@linux.intel.com>
Subject: Re: [PATCH 2/2] apic: Add print error interrupt reason
Date: Wed, 05 Jan 2011 20:34:51 -0800 [thread overview]
Message-ID: <1294288492.12561.46.camel@Joe-Laptop> (raw)
In-Reply-To: <1294284532-24285-3-git-send-email-youquan.song@intel.com>
On Thu, 2011-01-06 at 11:28 +0800, Youquan Song wrote:
> End user worry about the error interrupt information and intend to know what
> kind of error interrupts are generated, so this patch add printing out the
> detail debug information of error interrupt.
>
> Signed-off-by: Youquan Song <youquan.song@intel.com>
> ---
> arch/x86/kernel/apic/apic.c | 28 +++++++++++++++++++++++++++-
> 1 files changed, 27 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
[]
> +static const char *error_interrupt_reason[] = {
static const char * const etc[]
> + "Send CS error",
> + "Receive CS error",
> + "Send accept error",
> + "Receive accept error",
> + "Redirectable IPI",
> + "Send illegal vector",
> + "Received illegal vector",
> + "Illegal register address",
> +};
> +
> +static void print_error_interrupt_reason(u32 reason)
> +{
> + u32 i = 0;
> + reason = reason & 0xff;
> + do {
> + if (reason & 0x1)
> + pr_debug(" : %s", error_interrupt_reason[i]);
This isn't correct as it will emit <7> for each reason.
You want pr_cont surrounded by #ifdef DEBUG
or some new #define pr_debug_cont in printk.h
but that won't play well with dynamic_debug.
Jason? Got a cure for this?
next prev parent reply other threads:[~2011-01-06 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 3:28 [PATCH 0/2] apic: Fix error interrupt report at all APs Youquan Song
2011-01-06 3:28 ` [PATCH 1/2] " Youquan Song
2011-01-06 3:28 ` [PATCH 2/2] apic: Add print error interrupt reason Youquan Song
2011-01-06 4:34 ` Joe Perches [this message]
2011-01-06 22:13 ` Jason Baron
2011-01-06 9:27 ` [PATCH 1/2] apic: Fix error interrupt report at all APs Yong Wang
2011-01-07 2:04 ` Youquan Song
2011-01-07 2:01 ` Suresh Siddha
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=1294288492.12561.46.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=arjan@linux.intel.com \
--cc=chaohong.guo@intel.com \
--cc=hpa@linux.intel.com \
--cc=jbaron@redhat.com \
--cc=kent.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=trenn@suse.de \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.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
Powered by JetHome