From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Zack Weinberg <zack@codesourcery.com>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Set TIF_IRET in more places
Date: Wed, 8 Jan 2003 16:29:07 +0000 [thread overview]
Message-ID: <20030108162906.GA5995@bjl1.asuk.net> (raw)
In-Reply-To: <20030107172128.A9592@twiddle.net>
Richard Henderson wrote:
> On Tue, Jan 07, 2003 at 11:27:32AM -0800, Zack Weinberg wrote:
> > > It explicitly checks for the opcode sequences 0x58b877000000cd80 and
> > > 0xb8ad000000cd80 in order to unwind exception frames around a
> > > handled signal. Ugly, isn't it?
> >
> > We're open to better ideas ...
>
> Something like having dwarf2 unwind information for the
> vsyscall page on the page as well?
It would be quite nice just to have dwarf2 unwind information, with an
unwind handler, for the classic non-vsyscall restorer in Glibc.
Then MD_FALLBACK_FRAME_STATE_FOR could be removed from GCC on all
Linux targets, regardless of kernel version.
Once that is working it will be much clearer what exactly to send
Linus for the vsyscall page.
-- Jamie
next prev parent reply other threads:[~2003-01-08 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 21:34 [PATCH] Set TIF_IRET in more places Zack Weinberg
2003-01-07 11:19 ` Jamie Lokier
2003-01-07 17:42 ` Linus Torvalds
2003-01-07 19:27 ` Zack Weinberg
2003-01-08 1:21 ` Richard Henderson
2003-01-08 2:33 ` Linus Torvalds
2003-01-08 3:32 ` Daniel Jacobowitz
2003-01-08 16:29 ` Jamie Lokier [this message]
2003-01-09 6:49 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 14:46 Luca Barbieri
2003-01-06 16:04 ` Linus Torvalds
2003-01-06 18:17 ` Luca Barbieri
2003-01-06 18:42 ` Ulrich Drepper
2003-01-06 18:49 ` Linus Torvalds
2003-01-06 20:26 ` Luca Barbieri
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=20030108162906.GA5995@bjl1.asuk.net \
--to=lk@tantalophile.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zack@codesourcery.com \
/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