/[gxemul]/upstream/0.4.4.1/doc/misc.html

This is repository of my old source code which isn't updated any more. Go to git.rot13.org for current projects!

Diff of /upstream/0.4.4.1/doc/misc.html

Parent Directory | Revision Log | View Patch Patch

-revision 12 by dpavlin,
Mon Oct  8 16:18:38 2007 UTC
+revision 20 by dpavlin,
Mon Oct  8 16:19:23 2007 UTC
 Line 10
  <!--
- $Id: misc.html,v 1.50 2005/08/16 05:15:24 debug Exp $
+ $Id: misc.html,v 1.58 2005/11/25 22:35:44 debug Exp $
  Copyright (C) 2003-2005  Anders Gavare.  All rights reserved.
 Line 52 
 SUCH DAMAGE.
          developing firmware, using GXemul</a>
    <li><a href="#compilercontruct">Using GXemul in compiler contruction courses</a>
    <li><a href="#disk">How to start the emulator with a disk image</a>
+   <li><a href="#filexfer">Transfering files to/from the guest OS</a>
    <li><a href="#largeimages">How to extract large gzipped disk images</a>
    <li><a href="#userland">Running userland binaries</a>
    <li><a href="#promdump">Using a PROM dump from a real machine</a>
-Line 72 
 the Internet. If you are interested in t
+Line 73 
 the Internet. If you are interested in t
  reasons why networking is implemented in the emulator the way it currently
  is implemented, you might want to read the <a href="technical.html#net">
  networking section in the technical documentation</a>.
- <p>
- The guest OS running inside the emulator uses a private IPv4 address, such
+ <p><font color="#ff0000">This is still experimental, hackish, and
- as 10.0.0.1, and the emulator acts as a NAT-like gateway/firewall at IPv4
+ rather buggy. With NetBSD running as guest operating system, it mostly
- address 10.0.0.254. To the outside world it will seem like it is the host's
+ works.</font>
- OS that connects to other machines on the internet, not the guest OS.
- <p>
+ <p>When only one machine is being emulated, the following default values
- <font color="#ff0000">NOTE: This is still experimental!
+ apply:<pre>
- As of 2004-07-21, ARP + ICMP + UDP + TCP are emulated well enough to let
+         IPv4 address:                   10.0.0.1
- NetBSD and OpenBSD install via ftp, and use the network for many normal
+         Netmask:                        255.0.0.0
- activities, but not everything works yet.</font>
+         Gateway:                        10.0.0.254
+ </pre>
+ <p>The emulated machine must of course have a NIC which is emulated
+ correctly. At the moment, the following NICs should work:
+ <ul>
+   <li><tt><b>ether</b></tt>, the "fake" experimental ethernet device
+         (documented <a href="experiments.html#expdevices">here</a>)
+   <li><tt><b>le</b></tt>, Turbochannel Lance Ethernet, as used in
+         DECstation 5000/200 ("3max")
+   <li><tt><b>mec</b></tt>, the SGI O2's ethernet controller
+   <li><tt><b>dec21143</b></tt>, Digital's 21143 NIC (known as <tt>dc</tt>
+         in OpenBSD, or <tt>tlp</tt> in NetBSD)
+ </ul>
+ <p>The emulator acts as a NAT-like gateway/firewall; to the outside world
+ it will seem like it is the host's OS that connects to other machines on
+ the internet, not the guest OS.
-Line 94 
 activities, but not everything works yet
+Line 112 
 activities, but not everything works yet
  Is this a good idea?  The answer is yes and no, depending on the level of
  detail you need in your simulations. If you are developing an operating
- system or operating system kernel of your own, and wish to target
+ system or operating system kernel of your own, then the emulator can be a
- MIPS-like systems in general, then the answer might be yes, for
+ complement to testing on real hardware.
- experimental purposes.
- <p>Some examples of things that <i>don't</i> work, that you should keep in
+ <p>Important things to keep in mind:
- mind:
  <ul>
          <li>Porting code to a specific machine mode, e.g. a Silicon Graphics
-         machine, using GXemul, will not necessarily cause the code to
+         machine, using GXemul, will not "magically" cause the code to
          work on a real machine. Sometimes code works in GXemul which doesn't
          work on real hardware, sometimes it's the other way around.
-Line 111 
 mind:
+Line 127 
 mind:
          <li>GXemul contains bugs, and many things are not yet implemented.
          <p>
-         <li>I have only implemented devices in GXemul to the degree that
+         <li><b>Very important!</b> I have only implemented devices in GXemul
-         NetBSD, OpenBSD, etc, don't complain too much. One way to say it
+         to the degree that NetBSD, OpenBSD, Linux, etc don't complain too much.
-         is that the device implementations are "lazy hacks", based on the
+         <p>
-         assumption that the emulated OS is already developed and bug-free.
+         If you are developing a driver for a device which is emulated by
-         They are not intended to be used for development of new OS code,
+         GXemul, and your driver does not seem to be working, then the
-         so if you do that, then be prepared for bugs and inconsitencies.
+         probability of a bug in GXemul's implementation of the device is
+         very much higher than that of a bug in your driver.
+         <p>
+         The device implementations in GXemul are based on the assumption
+         that the emulated OS is already developed and bug-free. They are
+         not primarily intended to be used for development of new device
+         driver code in operating systems, so if you do that, then be
+         prepared for bugs and inconsitencies.
          <p>
          <li>CPU details in GXemul are usually wrong. If your code depends
          on, say, R10000 or MIPS64 specifics, chances are that GXemul will
-         not be sufficient. Again, this was done as "lazy hacks", and pretty
+         not be sufficient. One example is different revisions of ISAs;
-         much assumes that the OS being emulated is already developed
+-bit MIPS instructions which should trigger an exception on a
-         and bug-free.
+         real 32-bit MIPS processor usually execute anyway in GXemul. Another
+         example is if userland code tries to access kernel memory; in some
+         cases there is protection against this, but not in all cases (to get
+         higher performance).
          <p>
          <li>Caches. There is no cache emulation in GXemul right now. Caches
          for R2000/R3000 are faked well enough to run NetBSD, Ultrix, etc
-Line 145 
 your code during development, but it sho
+Line 169 
 your code during development, but it sho
  <h3>Using GXemul in compiler contruction courses:</h3>
  If you are learning how to write a compiler, and wish to target a
- realistic target platform, then MIPS (as emulated by GXemul)
+ realistic target platform, then MIPS or ARM (as emulated by GXemul)
- might be a suitable choice.
+ might be suitable choices.
  <ul>
    <li><b>(+)</b>&nbsp;&nbsp;Your compiler needs to output real assembly
-Line 182 
 emulated DECstation machine, you would u
+Line 206 
 emulated DECstation machine, you would u
  <pre>
          $ <b>gxemul -e 3max -d pmax_diskimage.fs netbsd-pmax-INSTALL</b>
  </pre>
- <p>
- NOTE: For some emulation modes, such as the DECstation mode, you do
+ <p>NOTE: For some emulation modes, such as the DECstation mode, you do
- <i>not</i> have to specify the name of the kernel, if the disk image is
+ <i>not</i> actually have to specify the name of the kernel, if the disk
- bootable!
+ image is bootable!
- <p>
- It is possible to have more than one disk. For each -d argument, a disk
+ <p>It is possible to have more than one disk. For each -d argument, a disk
  image is added; the first will be SCSI target 0, the second will be target 1, and so on,
  unless you specify explicitly which ID number the devices should have.
  <pre>
          $ <b>gxemul -e 3max -d disk0.raw -d disk1.raw -d 5:disk2.raw netbsd-pmax-INSTALL</b>
  </pre>
  Note: In the example above, disk2.raw will get scsi id 5.
- <p>
- If a filename has a 'c' prefix, or ends with ".iso", then it is assumed to be
+ <p>If a filename has a 'c' prefix, or ends with ".iso", then it is assumed to be
  a CDROM device (this can be overridden with a 'd' prefix, to force a read/write disk).
  For example, the following command would start the emulator with two
  CDROM images, and one harddisk image:
-Line 266 
 you can "switch tapes" without quiting a
+Line 290 
 you can "switch tapes" without quiting a
+ <p><br>
+ <a name="filexfer"></a>
+ <h3>Transfering files to/from the guest OS:</h3>
+ If the emulated machine supports networking (see
+ <a href="#networking">above</a>), then transfering files via FTP is
+ probably easiest.
+ <p>There is another way of transfering files which works for any kind of
+ emulated machine which supports disks (either SCSI or IDE). Any file can
+ be supplied as a disk image. For example, consider the following:<pre>
+         $ <b>gxemul -XEcats -d nbsd_cats.img -d archive.tar.gz netbsd-GENERIC</b>
+ </pre>
+ This will start NetBSD/cats with <tt>nbsd_cats.img</tt> as IDE master on
+ controller 0 (wd0), and <tt>archive.tar.gz</tt> as IDE slave on controller
+(wd1). From inside NetBSD, it is now possible to extract the files using
+ the following command:<pre>
+         (inside emulated NetBSD/cats)
+         # <b>tar zxvf /dev/wd1c</b>
+ </pre>
+ Don't worry if NetBSD complains about lack of disklabel; it doesn't
+ matter. On some machines, NetBSD uses <tt>wd1d</tt> instead of
+ <tt>wd1c</tt> for the entire disk.
+ There is also a minor problem: reading the end of the disk image. If you
+ experience problems untaring archives like this, then pad out the archive
+ first with some zeroes.
+ <p>Transfering files <i>out</i> from the emulated operating system to the
+ host can be done the same way. First, prepare an empty archive file:<pre>
+         $ <b>dd if=/dev/zero of=newarchive.tar bs=1024 count=1 seek=10000</b>
+ </pre>This example created a 10 MB empty file. Then, start the emulator
+ like this:<pre>
+         $ <b>gxemul -XEcats -d nbsd_cats.img -d archive.tar netbsd-GENERIC</b>
+ </pre>
+ and transfer files by creating an archive directly onto the disk image:<pre>
+         (inside emulated NetBSD/cats)
+         # <b>tar cvf /dev/wd1c filenames</b>
+ </pre>
+ where filenames are the files or directories to transfer.
  <p><br>
  <a name="largeimages"></a>
  <h3>How to extract large gzipped disk images:</h3>
-Line 480 
 This binary image can now be used in the
+Line 551 
 This binary image can now be used in the
           osconsole=3
          >>
  </pre>
- <i>(Note: at the moment, this doesn't work. I must have broken something when
- fixing something else, but this is what it looked like at the time.)</i>
+ <p><font color="#ff0000">(Note: at the moment, this doesn't work.
- <p>
+ I must have broken something when fixing something else, but this
- During bootup, the PROM complains <i>a lot</i> about hardware failures.
+ is what it looked like at the time.)</font>
+ <p>During bootup, the PROM complains <i>a lot</i> about hardware failures.
  That's because the emulator doesn't emulate the hardware well enough yet.
- <p>
- The command line options used are: -e 3min for
+ <p>The command line options used are: <tt>-e 3min</tt> for
- "DECstation 3min" (5000/1xx), -Q to supress the emulator's own PROM
+ "DECstation 3min" (5000/1xx), <tt>-Q</tt> to supress the emulator's own PROM
- call emulation, -M128 for 128MB RAM (because GXemul doesn't correctly
+ call emulation, <tt>-M128</tt> for 128MB RAM (because GXemul doesn't correctly
  emulate memory detection well enough for the PROM to accept, so it will
- always believe there is 128MB ram anyway), and -q to supress debug messages.
+ always believe there is 128MB ram anyway), and <tt>-q</tt> to supress debug messages.
- The 0xbfc00000 in front of the filename tells GXemul that it is a raw
+ The <tt>0xbfc00000</tt> in front of the filename tells GXemul that it is a raw
  binary file which should be loaded at a specific virtual address.
-Line 499 
 binary file which should be loaded at a
+Line 572 
 binary file which should be loaded at a
  <h4>Dumping the PROM on a SGI O2:</h4>
  The general ideas in this section applies to using ROM images from other
- machines as well. Besides DECstation, I've also tried this on an SGI IP32
+ machines as well. I have also tried this on an SGI IP32 ("O2"), in addition
- ("O2").
+ to the DECstation.
- <p>
- For the O2, a suitable command to dump the prom memory range is
+ <p>For the O2, a suitable command to dump the prom memory range is
  <pre>
          &gt;&gt; <b>dump -b 0xBFC00000:0xBFC80000</b>
  </pre>
  Make sure you capture all the output (via serial console) into a file,
- and then run experiments/sgiprom_to_bin on the captured file.
+ and then run <tt>experiments/sgiprom_to_bin</tt> on the captured file.
- <p>
- (2005-01-16: The emulator doesn't really emulate the IP32 well enough to
- actually run the PROM image without using special hacks, but it might do
- so some time in the future.)
+ <p>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <a href="sgi-o2-real.jpg"><img src="sgi-o2-real_small.jpg"></a>
+ &nbsp;&nbsp;&nbsp;
+ <a href="20050817-sgi-o2-success-7.png"><img src="20050817-sgi-o2-success-7_small.png"></a>
+ &nbsp;&nbsp;&nbsp;
+ <a href="20050817-sgi-o2-success-8.png"><img src="20050817-sgi-o2-success-8_small.png"></a>
+ <p>The photo on the left is from the real machine. The other two are
+ screenshots of the PROM running experimentally in GXemul, using <tt>-Y2</tt>
+ framebuffer scaledown.
+ <p>Normally during bootup, the IP32 PROM does a Power-On test which makes
+ sure that the caches and other things are working properly. GXemul doesn't
+ emulate all those things well enough for the tests to pass. The
+ experimental screenshots above were taken with cache detection skipped
+ manually.
+ <p><font color="#ff0000">
+ In other words: don't expect this to work out-of-the-box with GXemul right
+ now. It might work once I've added correct cache emulation.</font>
+ <p>The command line used to start the emulator, once correct cache
+ emulation has been implemented, would be something like <tt>gxemul -XQeo2
+xbfc00000:prom.bin</tt>.
+ <p>The same caution applies when dealing with SGI PROMs as with
+ DECstation PROMs: GXemul doesn't really emulate the hardware, it only
+ "fakes" devices well enough to fool some things, primarily NetBSD, that
+ it is emulating a real machine. ROM code is usually a <i>lot</i> more
+ picky about the details.
+ <p>The graphics used in the O2 is (as far as I know) undocumented. Combining
+ some traces of info from how Linux/O2 draws to the screen with some
+ reverse-engineering of my own, I've implemented enough of the controller to
+ let the PROM draw rectangles and bitmaps, but not much more. The SCSI
+ controller is not implemented yet either.

 Legend:



Removed from v.12
 


changed lines


 
Added in v.20
 Legend:



Removed from v.12
 


changed lines


 
Added in v.20
-Removed from v.12
+Added in v.20

	ViewVC Help
Powered by ViewVC 1.1.26