Age | Commit message (Collapse) | Author |
|
big anyways.
However, getting rid of the various constants (expanding to 0 for logs and
shifts, and 1 for size) allows us to do further simplifications in some pmap
loops, as there is no risk anymore of address wrapround.
While there, fix some typos and comments.
|
|
|
|
|
|
|
|
- remove unused routines (which were mostly here for debugging anyway)
- do not include <machine/m88*.h> from <machine/cmmu.h> but rather only
from the modules which need them
- try to simplify the MVME187 codepath in the 8820x code, whenever possible
|
|
typedefs.
|
|
|
|
|
|
|
|
|
|
|
|
While there, KNF data_access_exception().
|
|
process, remove duplicate batc defines.
|
|
There are more occurences hiding in binutils, lynx and afs but I am too
lazy to report them upstream at the moment.
|
|
Also clean <machine/psl.h> contents while there.
|
|
more realistic.
|
|
- always give C routines invoked by the assembly code some breathing room on
the stack
- merge error and reset exception handlers -- gets us rid of error_fault()
and error_reset().
- remove all references to SR0 and "threads" inherited from Mach. In fact,
we do not use SR0 at all now.
- only use double load and stores instructions when we are 200% sure we are
accessing a correctly aligned area. I am not fond of unaligned kernel
accesses, and forcing every pgb to be aligned on an 8 byte boundary is
gross.
|
|
which is only used to obfuscate things.
Doing this points out that the BUG memory is not at the same address on
187 and 197 (the 197 BUG is inside obio), so provide distinct constants,
and treat 187 and 197 slightly differently in pmap_bootstrap(). However, we
now need to map the 197 flash memory as well...
While there, simplify and constify pmap_table_build() and its associated data.
|
|
includable even without option DDB, in which case it will only define
the PC_REGS(), inst_return() and inst_call() macros; this removes the need
to declare them a second time in trap.c.
|
|
|
|
switch to another, safe, unused bit.
From the MC88110UM via deraadt@
|
|
trap vector contents, putting the bugtrap() stub in place, and switching
back and forth between them when the kernel needs to invoke BUG functions.
|
|
- the 88410 handling code is not working correctly. Check whether we are
operating with 88410's, and only invoke these routines if necessary.
- force serial mode execution in the PSR for the moment (hopefully only
temporary)
- disable branch prediction and data matching in the PSR, the 88110 errata
is simply too scary about them.
- a better pipeline flush after changing the ictl control register.
These changes let 197LE (but not 197SP/DP) boot up to autoconf.
Userland process do not work at the moment.
|
|
priorities because we are nice people.
|
|
pollution. Makes warnings in binutils compilation disappear...
|
|
constants.
|
|
|
|
|
|
necessary for proper gcc 2.95 operation.
|
|
Gets us a working perl 5.8.
|
|
|
|
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
using a 3 clause licence.
|
|
|
|
|
|
This allows us to remove some ambiguities on how some functions are called,
remove some diagnostic checks for conditions that can never happen and
remove the ugly hack with "pmap_initialized".
Then, rework internal function interfaces and some logic so as to stop
fetching vm_page from a pa and the reverse every now and then - this makes
some pmap operations run much faster.
While there, various KNF and whitespace fixes, and rename some structure
fields to be closer to the m68k pmap.
per art@'s idea.
|
|
|
|
macros, rather than include files - no need to pollute <machine/> area...
|
|
and check input level in setipl() if DIAGNOSTIC.
Doing this pointed out an horrible bug where exception frames would refer
to the saved ipl at the time the exception was processed, but would not
save it before, and the joys of stack values would make it a correct value
90% of the time. Of course, bad things could happen when restoring the
``saved'' ipl...
|
|
|
|
|
|
|
|
|
|
|
|
can link against libc without unresolved symbols again.
Anyone who correctly guessed that my m88k hard drive has been recovered,
wins a strawberry lollipop.
|
|
The only OSes I've seen that use SIZE_T_MAX are 4.4BSD-derived whereas
SYSV things seem to use SIZE_MAX. It is also consistent with SSIZE_MAX
(which we already have). deraadt@ OK
|
|
|
|
|
|
|