From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] conditionalize call from panic() to smp_send_stop()
Date: Thu, 15 Jan 2009 09:16:11 +0000 [thread overview]
Message-ID: <496F0CEB.76E4.0078.0@novell.com> (raw)
In-Reply-To: <87wscxdyyf.fsf@basil.nowhere.org>
>>> Andi Kleen <andi@firstfloor.org> 15.01.09 04:34 >>>
>"Jan Beulich" <jbeulich@novell.com> writes:
>
>> ... avoiding nested warnings and/or oopses as much as possible (namely
>> durin early boot).
>
>Better would be to fix smp_send_stop than to work around it for this
>very limited case. I've been running into this with machine checks
>too. The new fancy smp_call_function() that is there now just doesn't
>work in any unusual situation like early boot or fatal exceptions,
Indeed - I wasn't used to smp_call_function...() to be generic functions
that can be fixed for all architectures at once. I simply wanted to avoid
needing individual changes in all architectures...
Jan
prev parent reply other threads:[~2009-01-15 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 12:25 Jan Beulich
2009-01-15 3:34 ` Andi Kleen
2009-01-15 9:16 ` Jan Beulich [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=496F0CEB.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@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
Powered by JetHome