From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Question about ia64 linux
Date: Tue, 23 Mar 2004 21:57:02 +0000 [thread overview]
Message-ID: <16480.45742.317088.475004@napali.hpl.hp.com> (raw)
In-Reply-To: <BAY14-F301ImxoKYUVs0007e432@hotmail.com>
>>>>> On Sun, 21 Mar 2004 22:13:23 -0800, "Luck, Tony" <tony.luck@intel.com> said:
Tony> The software developers manual covers everything that
Tony> you need to know.
True, but if you modify code in such a way that it affects a
procedure's call-frame, then you need to patch the unwind info as
well, and that's not discussed in these manuals. The Software
Convention and Runtime Architecture does discuss unwind info, but
doesn't directly address the issue of runtime-generated code. The
libunwind API (http://www.hpl.hp.com/research/linux/libunwind/) has
support for (efficiently) describing runtime-generated code but, alas,
this API isn't used in the kernel yet. And even if it were, it's
unlikely the dynamic unwind info support would be enabled for the
kernel (not until someone demonstrates a real need for having a JIT in
the kernel, at least ;-).
--david
prev parent reply other threads:[~2004-03-23 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 3:00 Question about ia64 linux Raj Pati
2004-03-22 6:13 ` Luck, Tony
2004-03-22 22:09 ` Raj Pati
2004-03-23 21:57 ` 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=16480.45742.317088.475004@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