public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: pavel@suse.cz
Cc: alan@lxorguk.ukuu.org.uk, ldb@ldb.ods.org,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH 1 / ...] i386 dynamic fixup/self modifying code
Date: Thu, 29 Aug 2002 17:05:51 -0700 (PDT)	[thread overview]
Message-ID: <20020829.170551.98069822.davem@redhat.com> (raw)
In-Reply-To: <20020829232233.GA18573@atrey.karlin.mff.cuni.cz>

   From: Pavel Machek <pavel@suse.cz>
   Date: Fri, 30 Aug 2002 01:22:33 +0200

   Aha, making a list and just patching early at boot is even simpler
   than method I was thinking about.... Why not do it that way?

Even more cleverly you could use subsections, and thus:

1) __init free the patch code blocks at the end of boot
2) patch them more simply, the .subsection entries would
   be "kern_addr, insn" __u32 pairs on x86 for example.



  reply	other threads:[~2002-08-30  0:07 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 [this message]
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
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=20020829.170551.98069822.davem@redhat.com \
    --to=davem@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox