Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Warner Losh <imp@village.org>
To: ralf@uni-koblenz.de
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: get_mmu_context()
Date: Tue, 20 Oct 1998 17:36:53 -0600	[thread overview]
Message-ID: <199810202336.RAA29729@harmony.village.org> (raw)
In-Reply-To: Your message of "Tue, 20 Oct 1998 19:31:16 +0200." <19981020193116.C478@uni-koblenz.de>

In message <19981020193116.C478@uni-koblenz.de> ralf@uni-koblenz.de writes:
: running on the target machine.  On the other side as soon as we run on
: the machine we know these details.  They're constants, so why not making
: optimal use of them?

I'm confused then...

: You're right in that things should become more generic and I have ideas
: to make them more generic.  For the moment being I don't want to continue
: on that since 2.2 is coming soon and more important things are still to do.
: That's should however be an interesting 2.3 project.

Yes.  Basically something has load the kernel, and that something
could do the fixups.  Basically it would be a relocation record with a
"tag" on it that said what systems to do it on.

However, I do see your point that when you want to have the varients
based on cache size, memory controller, cache line size, etc it gets
really ugly....

It would be a cool project, however...

Warner

  reply	other threads:[~1998-10-20 23:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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               ` Warner Losh [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
1998-10-20  4:21 get_mmu_context() Ariel Faigon
1998-10-20  4:21 ` get_mmu_context() Ariel Faigon

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=199810202336.RAA29729@harmony.village.org \
    --to=imp@village.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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