From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [patch] 2.4.20 unwind.c to handle multiple struct pt_regs
Date: Wed, 19 Feb 2003 19:21:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805875@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805864@msgid-missing>
Hi Keith,
Keith> This patch has been running inside SGI for 2 months. It
Keith> handles kernel stacks with multiple struct pt_regs, as found
Keith> while debugging the kernel. The debugging statements in the
Keith> unwind code were awkward to use and inconsistent in what was
Keith> being dumped and when, I ended up changing almost all the
Keith> unwind debugging code while tracking down this problem.
The patch basically looks fine to me, except that I'd really like to
prefer to have it split up into one patch that does the pt_regs fixes
and one that does the debug enhancements. And while you're at it,
please use something a bit more concise than UNW_DEBUG_PRINT
(something like DPRINT or UNW_DPRINT should be sufficient).
Thanks,
--david
prev parent reply other threads:[~2003-02-19 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 6:16 [Linux-ia64] [patch] 2.4.20 unwind.c to handle multiple struct pt_regs Keith Owens
2003-02-19 19:21 ` David Mosberger [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=marc-linux-ia64-105590709805875@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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