From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Luca Barbieri <ldb@ldb.ods.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Pavel Machek <pavel@suse.cz>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH 1 / ...] i386 dynamic fixup/self modifying code
Date: Tue, 3 Sep 2002 22:35:03 +0100 [thread overview]
Message-ID: <20020903223503.B6848@kushida.apsleyroad.org> (raw)
In-Reply-To: <1030663772.1491.107.camel@ldb>; from ldb@ldb.ods.org on Fri, Aug 30, 2002 at 01:29:32AM +0200
Luca Barbieri wrote:
> > For the other fixups though you -have- to do them before you
> > run the code. That isnt hard (eg sparc btfixup). You generate a list of
> > the addresses in a segment, patch them all and let the init freeup blow
> > the table away
> Is doing them at runtime with the aforementioned workaround fine?
I would suggest that the init time table is infinitely saner, but if
there will be compiler generated instructions that are hard to catch, do
both: init time fixups for the __asm__ statements, and run time for
compiler generated instructions.
You really want the init time fixups anyway, because a really _really_
obvious optimisation is to remove `lock' prefixes on UP.
-- Jamie
next prev parent reply other threads:[~2002-09-03 21:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 3:41 [PATCH 1 / ...] i386 dynamic fixup/self modifying code Luca Barbieri
2002-08-28 12:11 ` Pavel Machek
2002-08-29 22:57 ` Luca Barbieri
2002-08-29 23:19 ` Alan Cox
2002-08-29 23:22 ` Pavel Machek
2002-08-30 0:05 ` David S. Miller
2002-08-30 0:21 ` Luca Barbieri
2002-08-29 23:29 ` Luca Barbieri
2002-08-29 23:32 ` Alan Cox
2002-08-30 0:10 ` Luca Barbieri
2002-08-30 11:17 ` Alan Cox
2002-09-03 21:31 ` Jamie Lokier
2002-09-03 21:35 ` Jamie Lokier [this message]
2002-08-30 0:08 ` David S. Miller
2002-08-28 15:53 ` Mikael Pettersson
2002-08-28 16:16 ` Luca Barbieri
2002-08-28 19:48 ` Mikael Pettersson
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=20020903223503.B6848@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.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 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.