From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.5 unwind problem with rp <- r0
Date: Thu, 06 May 2004 00:08:21 +0000 [thread overview]
Message-ID: <20213.1083802101@ocs3.ocs.com.au> (raw)
In-Reply-To: <4885.1083211711@kao2.melbourne.sgi.com>
On Wed, 5 May 2004 16:38:25 -0700,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Wed, 05 May 2004 10:04:58 +1000, Keith Owens <kaos@sgi.com> said:
>
> Keith> This ugly kludge handles unwinding from a value in r0. It
> Keith> gets the kernel unwinder working again, until it can be
> Keith> replaced by libunwind.
>
>I hate kludges.
>
>An alternative that might make you happy: in kernel_thread(),
>initialize regs.sw.r4 to 0, then change start_kernel_thread's
>prologue to:
>
> .prologue
> .save rp, r4
> .body
>
>Want to try this?
I would rather keep the ability to .save rp,r0 and fix the unwinder to
cope, even if it needs a kludge. After all, a great luminary said that
.save rp,r0 was the correct fix back in March 2003.
http://marc.theaimsgroup.com/?l=linux-ia64&m\x105590709806090&w=2
next prev parent reply other threads:[~2004-05-06 0:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 4:08 2.6.5 unwind problem with rp <- r0 Keith Owens
2004-05-03 22:28 ` David Mosberger
2004-05-04 2:07 ` Keith Owens
2004-05-04 16:40 ` David Mosberger
2004-05-05 0:04 ` Keith Owens
2004-05-05 23:38 ` David Mosberger
2004-05-06 0:08 ` Keith Owens [this message]
2004-05-06 0:19 ` David Mosberger
2004-05-06 2:04 ` Keith Owens
2004-05-06 3:42 ` David Mosberger
2004-05-07 8:12 ` Keith Owens
2004-05-11 7:03 ` David Mosberger
2004-05-11 11:32 ` Keith Owens
2004-05-11 16:55 ` 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=20213.1083802101@ocs3.ocs.com.au \
--to=kaos@sgi.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