From: Gregory Haskins <ghaskins@novell.com>
To: mingo@elte.hu
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
ghaskins@novell.com
Subject: [PATCH 0/2] RT: Enhance PREEMPT_TRACE with deeper stacks
Date: Fri, 10 Aug 2007 08:14:08 -0600 [thread overview]
Message-ID: <20070810140745.12966.8464.stgit@lsg> (raw)
This series changes the PREEMPT-TRACE behavior for reporting critical
sections. The previous code reported 2 frames per section. The new code uses
the save_stack_trace facility to save an arbitrary number of frames (currently
set to 5 via a #define)
For what its worth, these patches assisted me with debugging some issues in
-rt. The second patch is really a workaround for where X86_64 frame-pointers
apparently are not working under certain circumstances.
Signed-off-by: Gregory Haskins <ghaskins@novell.com>
next reply other threads:[~2007-08-10 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 14:14 Gregory Haskins [this message]
2007-08-10 14:14 ` [PATCH 1/2] Adds full stack to critical-section tracing Gregory Haskins
2007-08-30 0:48 ` Daniel Walker
2007-08-10 14:14 ` [PATCH 2/2] Some stacks show up untracable, so fall back to old method in this case Gregory Haskins
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=20070810140745.12966.8464.stgit@lsg \
--to=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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