From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.3 sync unwind code with 2.4.25
Date: Mon, 23 Feb 2004 21:47:40 +0000 [thread overview]
Message-ID: <16442.29948.177970.936607@napali.hpl.hp.com> (raw)
In-Reply-To: <4545.1077507994@kao2.melbourne.sgi.com>
>>>>> On Tue, 24 Feb 2004 08:38:16 +1100, Keith Owens <kaos@sgi.com> said:
Keith> On Mon, 23 Feb 2004 12:07:39 -0800,
Keith> David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>>> On Mon, 23 Feb 2004 14:46:34 +1100, Keith Owens <kaos@sgi.com> said:
Keith> The unwind code in 2.6.3 is missing a debug patch. This
Keith> patch is in 2.4.25 and makes it much easier to diagnose
Keith> unwind problems. printk output does not appear when
Keith> in_interrupt(), kdb_printf output does. This brings 2.6.3
Keith> unwind closer to 2.4.25.
>> Sorry, but I just don't see why there should be KDB-stuff in unwind.c
>> when KDB isn't part of the official Linux tree.
Keith> You took the same patch for unwind.c in the 2.4 kernel.
Well, that was 2.4. I don't recall the details, but like I said, I
don't see a good reason for including KDB patches in the default
kernel when KDB isn't part of it.
--david
next prev parent reply other threads:[~2004-02-23 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 3:46 [patch] 2.6.3 sync unwind code with 2.4.25 Keith Owens
2004-02-23 20:07 ` David Mosberger
2004-02-23 21:38 ` Keith Owens
2004-02-23 21:47 ` David Mosberger [this message]
2004-02-23 23:09 ` David Mosberger
2004-02-23 23:28 ` Keith Owens
2004-02-23 23:34 ` David Mosberger
2004-02-23 23:53 ` Keith Owens
2004-02-24 0:02 ` David Mosberger
2004-02-24 0:03 ` David Mosberger
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=16442.29948.177970.936607@napali.hpl.hp.com \
--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