|
![]() NetBSD/pmax 1.6.2 with X11 |
The processor architecture best emulated by GXemul is MIPS, but other architectures such as ARM and PowerPC are also partially emulated.
Devices and CPUs are not simulated with 100% accuracy. They are only ``faked'' well enough to allow guest operating systems run without complaining too much. Still, the emulator could be of interest for academic research and experiments, such as when learning how to write operating system code.
The emulator is written in C, does not depend on third-party libraries, and should compile and run on most 64-bit and 32-bit Unix-like systems.
The emulator contains code which tries to emulate the workings of CPUs and surrounding hardware found in real machines, but it does not contain any ROM code. You will need some form of program (in binary form) to run in the emulator. For many emulation modes, PROM calls are handled by the emulator itself, so you do not need to use any ROM image at all.
You can use pre-compiled kernels (for example NetBSD kernels, or Linux), or other programs that are in binary format, and in some cases even actual ROM images. A couple of different file formats are supported (ELF, a.out, ECOFF, SREC, and raw binaries).
If you do not have a kernel as a separate file, but you have a bootable disk image, then it is sometimes possible to boot directly from that image. (This works for example with DECstation emulation, or when booting from ISO9660 CDROM images.)
The code I have written is released under a 3-clause BSD-style license (or "revised BSD-style" if one wants to use GNU jargon). Apart from the code I have written, some files are copied from other sources such as NetBSD, for example header files containing symbolic names of bitfields in device registers. They are also covered by similar licenses, but with some additional clauses. The main point, however, is that the licenses require that the original Copyright and license terms are included when you make a copy or modification.
If you plan to redistribute GXemul without supplying the source code, then you need to comply with each individual source file some other way, for example by writing additional documentation containing copyright notes. I have not done this, since I do not plan on making distributions without source code. You need to check all individual files for details. The "easiest way out" if you plan to redistribute code from GXemul is, of course, to let it remain open source and simply supply the source code.
In case you want to reuse parts of GXemul, but you need to do that under a different license (e.g. the GPL), then contact me and I might re-license/dual-license files on a case-by-case basis.
$ ./configure $ make
This should work on most Unix-like systems. GXemul does not require any specific libraries to build, however, if you build on a system which does not have X11 libraries installed, some functionality will be lost.
The emulator's performance is highly dependent on both runtime settings and on compiler settings, so you might want to experiment with different CC and CFLAGS environment variable values. For example, on an AMD Athlon host, you might want to try setting CFLAGS to -march=athlon -O3 before running configure.
To get some ideas about what is possible to run in the emulator, please read the section about installing "guest" operating systems. If you are interested in using the emulator to develop code on your own, then you should also read the section about Hello World.
To exit the emulator, type CTRL-C to enter the single-step debugger, and then type quit.
If you are starting an emulation by entering settings directly on the command line, and you are not using the -x option, then all terminal input and output will go to the main controlling terminal. CTRL-C is used to break into the debugger, so in order to send CTRL-C to the running (emulated) program, you may use CTRL-B. (This should be a reasonable compromise to allow the emulator to be usable even on systems without X Windows.)
There is no way to send an actual CTRL-B to the emulated program, when typing in the main controlling terminal window. The solution is to either use configuration files, or use -x. Both these solutions cause new xterms to be opened for each emulated serial port that is written to. CTRL-B and CTRL-C both have their original meaning in those xterm windows.
(For MIPS emulation, I have written an experimental dynamic binary translation subsystem, for Alpha and i386 hosts. This gives higher total performance than interpreting one instruction at a time and executing it. If you wish to disable bintrans, add -B to the command line.)
Non-MIPS emulation modes use dynamic translation, but not recompilation into native code. This makes it possible to run on any host platform.
Caches are by default not emulated. In some cases, the existance of caches is "faked" to let operating systems think that they are there. (There is some old code for R2000/R3000 caches, but it has probably suffered from bitrot by now.)
The emulator is not timing-accurate. It can be run in a "deterministic" mode, -D. The meaning of deterministic is simply that running two emulations with the same settings will result in identical runs. Obviously, this requires that no user interaction is taking place, and that clock speeds are fixed with the -I option. (Deterministic in this case does not mean that the emulation will be identical to some actual real-world machine.)
(Oops/TODO: User interaction means both input to the emulated program/OS, and interacting with the emulator itself. Breaking into the debugger and then continuing execution may affect when/how interrupts occur.)
(
There is code in GXemul for emulation of many other machine types; the degree to which these work range from almost being able to run a complete OS, to almost completely unsupported (perhaps just enough support to output a few boot messages via serial console).
In addition to emulating real machines, there is also a "test-machine". A test-machine consists of one or more CPUs and a few experimental devices such as:
This mode is useful if you wish to run experimental code, but do not wish to target any specific real-world machine type, for example for educational purposes.
You can read more about these experimental devices here.