Defining ISAs (as of M5 2.0 beta 3)
- NOTE: THIS PAGE IS UNDER CONSTRUCTION. HOPE TO FINISH SOON!!!
- 1 Overview
- 2 Syscall Emulation (SE) MyISA
- 3 Full-System (FS) MyISA
- 4 Summary
First, make sure you have basic understanding of how an ISA description generates instructions within the M5 framework. A good start is the The M5 ISA description language page.
For this example, we will be constructing an ISA called MyISA which will just be a renamed version of the MIPS ISA. We will go through the steps of creating the files and configuration opions for an M5 ISA description.
Your new ISA description, MyISA, will need to generate correct instructions for the different CPU models. More specifically, your MyISA description will allow your MyISA architecture (analagous to ALPHA,MIPS,SPARC,etc.) to be plugged into System-Call Emulation (SE) and Full-System (FS) simulations of any M5 CPU Model.
Syscall Emulation (SE) MyISA
Creating the Files for MyISA
Making M5 Recognize MyISA
- src/arch/isa_specific.hh - Edit this file by adding a constant for MyISA and then adding MyISA to the #define if/else structure.
... #define ALPHA_ISA 21064 ... #define MY_ISA 6400 ... #if THE_ISA == ALPHA_ISA #define TheISA AlphaISA #elif THE_ISA == SPARC_ISA #define TheISA SparcISA ... #elif THE_ISA == MY_ISA #define TheISA MyISA #else #error "THE_ISA not set" #endif
MyISA Architecture - src/arch/MyISA/isa_traits.hh
MyISA Formats & Templates - src/arch/MyISA/formats/*.isa
MyISA Decoder - src/arch/MyISA/decoder.isa
Now Build Your Decoder:
scons build/MYISA_SE/arch/MyISA/atomic_simple_cpu_exec.cc CPU_MODELS=AtomicSimpleCPU