From: "Gary Shi" <garyu.shi@gmail.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysrq: freeze other CPUs during sysrq-t
Date: Wed, 20 Aug 2008 19:28:37 -0300 [thread overview]
Message-ID: <7b97a12b0808201528o5bab7840w1226d1faadb2c924@mail.gmail.com> (raw)
In-Reply-To: <48A70DF4.5040901@goop.org>
On 8/16/08, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Why not use stop_machine()?
Just know about stop_machine() from your reply. Thanx. But after
checking its src, I feel its too demanding to fit sysrq-t use; e.g.,
when other cpus got deadlocked on some spin locks with preempt
disabled, then the kernel threads of stopmachine won't get a chance to
run on other cpus.
We would expect one or more cpus response only to irqs, when we try to
collect sysrq data; most of the time, only when the systems hang for
whatever reasons does the sysrq data need to be collected, right?
--gys
prev parent reply other threads:[~2008-08-20 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 0:38 Gary Shi
2008-08-16 17:27 ` Jeremy Fitzhardinge
2008-08-20 22:28 ` Gary Shi [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=7b97a12b0808201528o5bab7840w1226d1faadb2c924@mail.gmail.com \
--to=garyu.shi@gmail.com \
--cc=jeremy@goop.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
all inboxes | Powered by JetHome®