Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: linux@cthulhu.engr.sgi.com (SGI/Linux mailing list)
Subject: Re: get_mmu_context()
Date: Mon, 19 Oct 1998 21:21:28 -0700 (PDT)	[thread overview]
Message-ID: <199810200421.VAA17379@oz.engr.sgi.com> (raw)

Forwarding message from David, his email probably changed
so it bounced...

----- Forwarded message from owner-linux@cthulhu -----

From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: imp@village.org
CC: ralf@uni-koblenz.de, linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
In-reply-to: <199810200407.WAA03233@harmony.village.org> (message from Warner
	Losh on Mon, 19 Oct 1998 22:07:26 -0600)
Subject: Re: get_mmu_context()
References: <19981019121804.F387@uni-koblenz.de>  <Pine.SV4.3.91.981016185136.876A-100000@mech.math.msu.su> <XFMail.981018215318.harald.koerfgen@netcologne.de> <199810200407.WAA03233@harmony.village.org>

   Date: Mon, 19 Oct 1998 22:07:26 -0600
   From: Warner Losh <imp@village.org>

   Wouldn't it be easier to have ld to have variant fixup records?
   That way you could patch all instances at run time, much like we do
   when we load stuff now...

See sparc32's btfixup in the kernel sources for the best
implementation I've ever seen.

Later,
David S. Miller
davem@dm.cobaltmicro.com

----- End of forwarded message from owner-linux@cthulhu -----

-- 
Peace, Ariel

WARNING: multiple messages have this Message-ID (diff)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Re: get_mmu_context()
Date: Mon, 19 Oct 1998 21:21:28 -0700 (PDT)	[thread overview]
Message-ID: <199810200421.VAA17379@oz.engr.sgi.com> (raw)
Message-ID: <19981020042128.CgihFwgFr_vuDKH467jiO-tSV-zV_9xamxicVj-ssIo@z> (raw)

Forwarding message from David, his email probably changed
so it bounced...

----- Forwarded message from owner-linux@cthulhu -----

From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: imp@village.org
CC: ralf@uni-koblenz.de, linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
In-reply-to: <199810200407.WAA03233@harmony.village.org> (message from Warner
	Losh on Mon, 19 Oct 1998 22:07:26 -0600)
Subject: Re: get_mmu_context()
References: <19981019121804.F387@uni-koblenz.de>  <Pine.SV4.3.91.981016185136.876A-100000@mech.math.msu.su> <XFMail.981018215318.harald.koerfgen@netcologne.de> <199810200407.WAA03233@harmony.village.org>

   Date: Mon, 19 Oct 1998 22:07:26 -0600
   From: Warner Losh <imp@village.org>

   Wouldn't it be easier to have ld to have variant fixup records?
   That way you could patch all instances at run time, much like we do
   when we load stuff now...

See sparc32's btfixup in the kernel sources for the best
implementation I've ever seen.

Later,
David S. Miller
davem@dm.cobaltmicro.com

----- End of forwarded message from owner-linux@cthulhu -----

-- 
Peace, Ariel

             reply	other threads:[~1998-10-20  4:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-20  4:21 Ariel Faigon [this message]
1998-10-20  4:21 ` get_mmu_context() Ariel Faigon
  -- strict thread matches above, loose matches on Subject: below --
1998-10-13 19:59 get_mmu_context() ralf
     [not found] ` <Pine.LNX.3.96.981014144230.10483B-100000@mirkwood.dummy.home>
1998-10-14 23:49   ` get_mmu_context() ralf
     [not found] ` <3625D799.7D923FA9@niisi.msk.ru>
1998-10-15 20:21   ` get_mmu_context() ralf
     [not found]     ` <Pine.SV4.3.91.981016185136.876A-100000@mech.math.msu.su>
1998-10-18 19:53       ` get_mmu_context() Harald Koerfgen
1998-10-19 10:18         ` get_mmu_context() ralf
1998-10-20  4:07           ` get_mmu_context() Warner Losh
1998-10-20 17:31             ` get_mmu_context() ralf
1998-10-20 23:36               ` get_mmu_context() Warner Losh
1998-10-21 19:31           ` get_mmu_context() Harald Koerfgen
1998-10-19  1:29       ` get_mmu_context() ralf
1998-10-16 22:44   ` get_mmu_context() ralf

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=199810200421.VAA17379@oz.engr.sgi.com \
    --to=ariel@oz.engr.sgi.com \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=linux@cthulhu.engr.sgi.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