From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>, Dave Jones <davej@redhat.com>,
kvm@vger.kernel.org,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>
Subject: Re: CPU softlockup due to smp_call_function()
Date: Thu, 05 Apr 2012 15:51:00 +0300 [thread overview]
Message-ID: <4F7D9534.90604@redhat.com> (raw)
In-Reply-To: <CA+1xoqeeagx=OwV2XFQYb=ATOGtW0Zpyx6BOcVbu3hg+eiMqSA@mail.gmail.com>
On 04/05/2012 03:32 PM, Sasha Levin wrote:
> >
> > It would be good to enhance smp_call_function_*() to do this
> > automatically when it happens - it's spinning there anyway, so it might
> > as well count the iterations and NMI the lagging cpu if it waits for too
> > long.
>
> What do you think about modifying the softlockup detector to NMI all
> CPUs if it's going to panic because it detected a lockup?
Fine by me. The triggering cpu should be dumped first though.
We lose knowledge of exactly which cpu is hung, but it should usually be
easily seen from the traces (the exceptional case would be a busy server
that is handling a lot of IPIs at the moment we trigger the traces).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-04-05 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 20:12 CPU softlockup due to smp_call_function() Sasha Levin
2012-04-05 4:06 ` Milton Miller
2012-04-05 8:25 ` Sasha Levin
2012-04-05 12:24 ` Avi Kivity
2012-04-05 12:32 ` Sasha Levin
2012-04-05 12:51 ` Avi Kivity [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=4F7D9534.90604@redhat.com \
--to=avi@redhat.com \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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