From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: ia64 cache flushing?
Date: Tue, 17 Dec 2002 03:50:53 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805596@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805582@msgid-missing>
>>>>> On Mon, 16 Dec 2002 19:42:51 -0800, Richard Henderson <rth@twiddle.net> said:
Richard> On Mon, Dec 16, 2002 at 06:15:28PM -0800, David Mosberger
Richard> wrote:
>> For someone who cares about modules and ia64 performance: you
>> might want to consider to use "brl" in the PLT stub instead of
>> the standardized code sequence.
Richard> You'll have to figure out how to find the plt stub though.
Richard> It's not marked in any way. The only thing you get a
Richard> pointer to is the .IA_64.pltoff entry.
Richard> For userland, the .plt stub has to use an indirect branch
Richard> because the first invocation goes through the dynamic
Richard> linker. Then we update the .pltoff entry and so subsequent
Richard> calls go direct to the target.
I assume you do early binding of the PLTs for kernel modules, right?
If so, patching the PLT code stub is trivial (even in user-land you
could do code patching, but that's obviously (a) not so trivial for
multi-threaded programs and (b) hurts sharing).
For user-level land, we should offer PLT-stub-inlining, but we
discussed this in private already...
--david
next prev parent reply other threads:[~2002-12-17 3:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 23:22 [Linux-ia64] Re: ia64 cache flushing? Rusty Russell
2002-12-17 0:25 ` Richard Henderson
2002-12-17 0:27 ` Rusty Russell
2002-12-17 1:14 ` Rusty Russell
2002-12-17 1:32 ` Richard Henderson
2002-12-17 2:11 ` Rusty Russell
2002-12-17 2:15 ` David Mosberger
2002-12-17 3:42 ` Richard Henderson
2002-12-17 3:50 ` David Mosberger [this message]
2002-12-17 7:20 ` Richard Henderson
2002-12-19 23:15 ` David Mosberger
2002-12-20 0:56 ` Richard Henderson
2002-12-20 1:07 ` David Mosberger
2002-12-20 1:18 ` Richard Henderson
2002-12-20 1:20 ` 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=marc-linux-ia64-105590709805596@msgid-missing \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.