linux-mips-fnet
[Top] [All Lists]

Re: get_mmu_context()

To: ralf@uni-koblenz.de
Subject: Re: get_mmu_context()
From: Warner Losh <imp@village.org>
Date: Tue, 20 Oct 1998 17:36:53 -0600
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
In-reply-to: Your message of "Tue, 20 Oct 1998 19:31:16 +0200." <19981020193116.C478@uni-koblenz.de>
References: <19981020193116.C478@uni-koblenz.de> <19981019121804.F387@uni-koblenz.de> <Pine.SV4.3.91.981016185136.876A-100000@mech.math.msu.su> <XFMail.981018215318.harald.koerfgen@netcologne.de> <19981019121804.F387@uni-koblenz.de> <199810200407.WAA03233@harmony.village.org>
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

<Prev in Thread] Current Thread [Next in Thread>