e5b1654f2f
in the window trap vectors were mixed up. All this did is cause unnecesary traps and look wierd in traces. Superfluous traps happen a lot in normal operation, so we are rather good at recovering from them. 2. Store the arguments for a ktr trace in the right place. 3. Use a generic trap vector for breakpoints. It should not be special. 4. Save the frame pointer in the trap frame for kernel traps if DDB is compiled in, otherwsie we don't save the out registers for kernel traps and stack traces can't go through nested traps. 5. Apply the same fix to the return from kernel mode trap code as for user mode traps. Ensure that the window we're returning to is the same one that we restore to by fiddling the cwp in the saved tstate. This requires that we transfer the values loaded from the trap frame into alternate globals before restore-ing, but doing so is not very expensive and not worth worrying about. Not changing the saved cwp can result in the register values magically changing on return from traps if we happen to have slept and the windows don't work out exactly the same. Fix the trace just before the retry to account for different register usage. 6. Use a SET macro for loading address constants rather than a variation of set and setx. set only works for 32 bit constants, while setx works for 64 bit constants as well, but produces bloated code when unnecessary. Gas always generates the canonical 2 register, 6 instruction form, even when it could be optimized; set uses 1 register and 2 instructions. At the moment we assume that the kernel binary is below 4GB so set is always sufficient, but the macro allows it to be configured. Note that this has nothing to do with 32 vs. 64 bit address space, it only applies to addresses of symbols which are known at compile/link time. Submitted by: tmm (6)
This is the top level of the FreeBSD source directory. This file was last revised on: $FreeBSD$ For copyright information, please see the file COPYRIGHT in this directory (additional copyright information also exists for some sources in this tree - please see the specific source directories for more information). The Makefile in this directory supports a number of targets for building components (or all) of the FreeBSD source tree, the most commonly used one being ``world'', which rebuilds and installs everything in the FreeBSD system from the source tree except the kernel, the kernel-modules and the contents of /etc. The ``buildkernel'' and ``installkernel'' targets build and install the kernel and the modules (see below). Please see the top of the Makefile in this directory for more information on the standard build targets and compile-time flags. Building a kernel is a somewhat more involved process, documentation for which can be found at: http://www.freebsd.org/handbook/kernelconfig.html And in the config(8) man page. Note: If you want to build and install the kernel with the ``buildkernel'' and ``installkernel'' targets, you have to build world before. More information is available in the handbook. The sample kernel configuration files reside in the sys/i386/conf sub-directory (assuming that you've installed the kernel sources), the file named GENERIC being the one used to build your initial installation kernel. The file NOTES contains entries and documentation for all possible devices, not just those commonly used. It is the successor of the ancient LINT file, but in contrast to LINT, it is not buildable as a kernel but a pure reference and documentation file. Source Roadmap: --------------- bin System/User commands. contrib Packages contributed by 3rd parties. crypto Cryptography stuff (see crypto/README). etc Template files for /etc games Amusements. gnu Various commands and libraries under the GNU Public License. Please see gnu/COPYING* for more information. include System include files. kerberosIV Kerberos package. lib System libraries. libexec System daemons. release Release building Makefile & associated tools. sbin System commands. secure Cryptographic libraries and commands. share Shared resources. sys Kernel sources. tools Utilities for regression testing and miscellaneous tasks. usr.bin User commands. usr.sbin System administration commands. For information on synchronizing your source tree with one or more of the FreeBSD Project's development branches, please see: http://www.freebsd.org/handbook/synching.html