From: "Gary Shi" <garyu.shi@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: get a still sysrq-t call trace, not a moving one
Date: Fri, 11 Apr 2008 18:43:52 -0300 [thread overview]
Message-ID: <7b97a12b0804111443j5ecacfe8i753f54a39093a1ed@mail.gmail.com> (raw)
Hi friends,
when I read sysrq-t call trace, I find the collected call trace for
some cases is not a still snapshot, but a moving one. After checking
show_state src, I realize other cpus are not frozen when one cpu is
doing show_state; thus some task switching can occur among those cpus,
even the cpu doing sysrq for some kind of kernels.
This moving call traces make debugging much more difficult, or even
impossible for some cases, since some tasks have been switched in/out
which make us lose the trace of some important data, like who is
holding a lock when lots of threads are blocked on the lock.
In order to get a still image of sysrq-t call trace, I'd like to
suggest freezing all other cpus and disabling irq of local cpu.
Any ideas about this?
Thanx
-gys
pls cc me when you reply since I haven't subscribed to the mailing list.
reply other threads:[~2008-04-11 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7b97a12b0804111443j5ecacfe8i753f54a39093a1ed@mail.gmail.com \
--to=garyu.shi@gmail.com \
--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®