3.6. In order to port...

Although UML has a concept of architecture dependent and architecture independent pieces, some architecture dependent pieces are still found in generic files which need a clean segregation. The main work involves filling up the details for some files that are Sparc64 specific by looking at Intel i386 specific files. UML also contains a considerable amount of Intel assembly code in i386 specific files. This means it is very much essential for a person doing this port to learn Sparc assembly language to understand and fill up the corresponding files. This stage takes up a lot of time wherein the obscure, architecture specific code for ptrace, registers, sigcontext, etc needs to be clearly understood for the gaps to be correctly filled in.

  1. arch/um/Makefile-sparc64. This file contains the definitions for:

  2. Sparc64 needs to provide a set of headers located in include/asm-um. Uml mostly uses the headers of the underlying architecture by creating a symlink from include/asm-um/arch to include/asm-sparc64. Some of the architecture-dependent headers which need to be present in include/asm-um are:

  3. Architecture headers: These are the headers that need to go in arch/um/include/sysdep-sparc64.

  4. Implementation files: The actual implementation of the Uml/Sparc64 port is contained in sys-sparc64 directory which defines the following files: