source: trunk/platforms/linux_monocluster/README @ 672

Last change on this file since 672 was 669, checked in by porquet, 11 years ago

linux_monocluster: hints about working revisions for soclib and tsar

File size: 2.2 KB
Line 
1April 2014, Joel Porquet
2
3This platform is known for being able to run Linux.
4
5----
6Pre-requisites:
7
8* A working version of SoCLib (r2558)
9    - the command `soclib-cc --getpath` should return where SoCLib is installed
10* A working version of TSAR (r668)
11    - TSAR directory should be properly added to SoCLib's configuration: either
12      globally, or through the `soclib.conf` file present in this directory (in
13      which case, the environment variable `TSARDIR` should be defined to point
14      on TSAR directory)
15
16
17----
18Targets of the Makefile:
19
20* clean: clean the compilation files
21* all (or none): compile the simulation system
22* run_tsar_boot: runs the simulation system using a boot loader (in this case,
23  you want to use a blockdevice image that contains the kernel: see `DSK`
24  option below)
25* run_dummy_boot: runs the simulation system using directly Linux instead of a
26  boot loader (i.e. Linux is already loaded in RAM before execution).
27
28
29----
30Options for running:
31
32These options apply when using either `run_tsar_boot` or `run_dummy_boot`
33targets. Example: `make run_dummy_boot GDB=1 VMLINUX=../vmlinux DSK=dsk.img`
34
35* GDB=1|[FXSCTZW]: options to the GDB server (1 means FCX which is a good
36  default)
37* NCPUS=[1-4]: number of processors
38* DSK=[pathname]: path to a filesystem to use with the BlockDevice component
39  (also implies creating a system with such a component, other the component is
40  deactivated)
41* TRACE=[number]: enables tracing the simulation starting from a certain cycle
42* NCYCLES=[number]: runs the simulation for a certain number of cycles
43
44    Only for run_dummy_boot:
45    * VMLINUX=[pathname]: path to Linux `vmlinux` image
46
47
48----
49Using GDB server:
50
51A file named `.gdbinit` contains a few macros that can be useful for debugging
52Linux when using the GDB server.
53
54* connect: connect to the GDB server that runs within the simulation
55* dmesg: print the content of the kernel message buffer
56* thread_info: print the thread_info structure of the current task
57* task_struct: print the task_struct structure of the current task
58* active_mm: print the active_mm structure of the current task
59* pgd: print the content of the page table of the current task
60* ps: print the list of running tasks
61
Note: See TracBrowser for help on using the repository browser.