From: Christophe Lucas <clucas@rotomalug.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 1/1] printk : arch/ia64/kernel/smp.c
Date: Wed, 23 Mar 2005 10:02:09 +0000 [thread overview]
Message-ID: <20050323100209.GA9206@rhum.iomeda.fr> (raw)
In-Reply-To: <20050319131906.E934A1F245@trashy.coderock.org>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Luck, Tony (tony.luck@intel.com) wrote:
> > if (cpuid == me) {
> >- printk("%s: trying to call self\n", __FUNCTION__);
> >+ printk(KERN_INFO "%s: trying to call self\n", __FUNCTION__);
> > put_cpu();
> > return -EBUSY;
> > }
>
> I think this is a bit higher priority than KERN_INFO. If we
> get here, then someone did something wrong at a higher level,
> and they may be disapponited that the function they want called
> isn't going to be called.
>
> Perhaps KERN_WARNING would be more appropriate?
>
> It might also be kind to anyone trying to debug this to print
> the "func" argument.
>
> -Tony
>
Perhaps this could do the job:
[-- Attachment #2: patch-linux-2.6.12-rc1_arch_ia64_kernel_smp.c.diff --]
[-- Type: text/plain, Size: 548 bytes --]
diff -uprN -X dontdiff a/arch/ia64/kernel/smp.c b/arch/ia64/kernel/smp.c
--- a/arch/ia64/kernel/smp.c 2005-03-18 02:34:36.000000000 +0100
+++ b/arch/ia64/kernel/smp.c 2005-03-23 10:35:18.000000000 +0100
@@ -269,7 +269,7 @@ smp_call_function_single (int cpuid, voi
int me = get_cpu(); /* prevent preemption and reschedule on another processor */
if (cpuid == me) {
- printk("%s: trying to call self\n", __FUNCTION__);
+ printk(KERN_WARNING "%s: trying to call self with info:%08x\n", __FUNCTION__, info);
put_cpu();
return -EBUSY;
}
next prev parent reply other threads:[~2005-03-23 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 13:19 [patch 1/1] printk : arch/ia64/kernel/smp.c domen
2005-03-22 21:52 ` Luck, Tony
2005-03-23 10:02 ` Christophe Lucas [this message]
2005-03-23 11:31 ` Domen Puncer
2005-06-20 21:49 ` domen
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=20050323100209.GA9206@rhum.iomeda.fr \
--to=clucas@rotomalug.org \
--cc=linux-ia64@vger.kernel.org \
/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