From: "Jan Beulich" <jbeulich@novell.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: "Randy Dunlap" <randy.dunlap@oracle.com>,
"Andi Kleen" <ak@suse.de>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fully support linker generated .eh_frame_hdr section
Date: Wed, 06 Dec 2006 07:57:52 +0000 [thread overview]
Message-ID: <45768610.76E4.0078.0@novell.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0612052052230.18570@yvahk01.tjqt.qr>
>>> Jan Engelhardt <jengelh@linux01.gwdg.de> 05.12.06 20:52 >>>
>
>>>> Now that binutils' ld is able to properly populate .eh_frame_hdr in the
>>>> Linux kernel case, here's a patch to add some functionality to the Dwarf2
>>>> unwinder to actually be able to make use of this (applies on firstfloor
>>>> tree with the previously sent patch to add debug output, but not on plain
>>>> 2.6.19).
>>>
>>>Requires what version of binutils / ld?
>>
>>mainline - the second of the required patches went in just yesterday.
>
>Which means people using distros will have it in some 6 months, unless
>vendors give an earlier update.
That's not the point here - the point is that the kernel should be ready to take
advantage of this whenever somebody tries to build with newer binutils. Also,
the patch adds a previously missing check that would result in not creating a
runtime allocated table (assuming the linker created one is usable), but failing
to read from that table during later lookups (resulting in the originally
observed long boot time due to lockdep making heavy use of this code).
Jan
prev parent reply other threads:[~2006-12-06 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 16:23 [PATCH] fully support linker generated .eh_frame_hdr section Jan Beulich
2006-12-04 22:58 ` Randy Dunlap
2006-12-05 8:23 ` Jan Beulich
2006-12-05 19:52 ` Jan Engelhardt
2006-12-06 7:57 ` Jan Beulich [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=45768610.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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