Single Cycle Mips
Single Cycle Mips
1
Single-cycle implementation
We will describe the implementation a simple MIPS-based instruction set
supporting just the following operations.
2
Computers are state machines
A computer is just a big fancy state machine.
— Registers, memory, hard disks and other storage form the state.
— The processor keeps reading and updating the state, according to the
instructions in some program.
CPU
State
3
John von Neumann
In the old days, ―programming‖ involved actually changing a machine’s
physical configuration by flipping switches or connecting wires.
— A computer could run just one program at a time.
— Memory only stored data that was being operated on.
Then around 1944, John von Neumann and others got the idea to encode
instructions in a format that could be stored in memory just like data.
— The processor interprets and executes instructions from memory.
— One machine could perform many different tasks, just by loading
different programs into memory.
— The ―stored program‖ design is often called a Von Neumann machine.
4
Memories
It’s easier to use a Harvard architecture at first, with
programs and data stored in separate memories. Read Instruction
To fetch instructions and read & write words, we address [31-0]
instruction memory.
MemRead
— Pretend it’s already loaded with a program,
which doesn’t change while it’s running.
5
Instruction fetching
The CPU is always in an infinite loop, fetching
instructions from memory and executing them.
The program counter or PC register holds the Add
Instruction
memory
6
Encoding R-type instructions
Last lecture, we saw encodings of MIPS instructions as 32-bit values.
Register-to-register arithmetic instructions use the R-type format.
— op is the instruction opcode, and func specifies a particular arithmetic
operation (see textbook).
— rs, rt and rd are source and destination registers.
op rs rt rd shamt func
6 bits 5 bits 5 bits 5 bits 5 bits 6 bits
add $s4, $t1, $t2 000000 01001 01010 10100 00000 1000000
7
Registers and ALUs
R-type instructions must access registers and an ALU. RegWrite
Read Read
register 1 data 1
Our register file stores thirty-two 32-bit values. Read
— Each register specifier is 5 bits long. register 2 Read
data 2
Write
— You can read from two registers at a time. register
Registers
— RegWrite is 1 if a register should be written. Write
data
ALUOp Function
000 and ALUOp
001 or
010 add
110 subtract
111 slt
8
Executing an R-type instruction
1. Read an instruction from the instruction memory.
2. The source registers, specified by instruction fields rs and rt, should be
read from the register file.
3. The ALU performs the desired operation.
4. Its result is stored in the destination register, which is specified by field
rd of the instruction word.
RegWrite
op rs rt rd shamt func
31 26 25 21 20 16 15 11 10 6 5 0
9
Encoding I-type instructions
The lw, sw and beq instructions all use the I-type encoding.
— rt is the destination for lw, but a source for beq and sw.
— address is a 16-bit signed constant.
op rs rt address
6 bits 5 bits 5 bits 16 bits
10
Accessing data memory
For an instruction like lw $t0, –4($sp), the base register $sp is added to
the sign-extended constant to get a data memory address.
This means the ALU must accept either a register operand for arithmetic
instructions, or a sign-extended immediate operand for lw and sw.
We’ll add a multiplexer, controlled by ALUSrc, to select either a register
operand (0) or a constant operand (1).
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
11
MemToReg
The register file’s ―Write data‖ input has a similar problem. It must be
able to store either the ALU output of R-type instructions, or the data
memory output for lw.
We add a mux, controlled by MemToReg, to select between saving the
ALU result (0) or the data memory output (1) to the registers.
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
12
RegDst
A final annoyance is the destination register of lw is in rt instead of rd.
op rs rt address
lw $rt, address($rs)
We’ll add one more mux, controlled by RegDst, to select the destination
register from either instruction field rt (0) or field rd (1).
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
13
Branches
For branch instructions, the constant is not an address but an instruction
offset from the current program counter to the desired address.
The target address L is three instructions past the beq, so the encoding of
the branch instruction has 0000 0000 0000 0011 for the address field.
Instructions are four bytes long, so the actual memory offset is 12 bytes.
14
The steps in executing a beq
1. Fetch the instruction, like beq $at, $0, offset, from memory.
2. Read the source registers, $at and $0, from the register file.
3. Compare the values by subtracting them in the ALU.
4. If the subtraction result is 0, the source operands were equal and the PC
should be loaded with the target address, PC + 4 + (offset x 4).
5. Otherwise the branch should not be taken, and the PC should just be
incremented to PC + 4 to fetch the next instruction sequentially.
15
Branching hardware
We need a second adder, since the ALU
is already doing subtraction for the beq.
0 PCSrc=1 branches
M to PC+4+(offset 4).
Add u
x
PCSrc=0 continues
PC 4
Multiply constant Add 1
to PC+4.
Shift
by 4 to get offset. left 2
PCSrc
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
16
The final datapath
0
M
Add u
x
PC 4
Add 1
Shift
left 2
PCSrc
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
17
Control
The control unit is responsible for setting all the control signals so that
each instruction is executed properly.
— The control unit’s input is the 32-bit instruction word.
— The outputs are values for the blue control signals in the datapath.
Most of the signals can be generated from the instruction opcode alone,
and not the entire 32-bit word.
To illustrate the relevant control signals, we will show the route that is
taken through the datapath by R-type, lw, sw and beq instructions.
18
R-type instruction path
The R-type instructions include add, sub, and, or, and slt.
The ALUOp is determined by the instruction’s ―func‖ field.
0
M
Add u
x
PC 4
Add 1
Shift
left 2
PCSrc
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
19
lw instruction path
An example load instruction is lw $t0, –4($sp).
The ALUOp must be 010 (add), to compute the effective address.
0
M
Add u
x
PC 4
Add 1
Shift
left 2
PCSrc
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
20
sw instruction path
An example store instruction is sw $a0, 16($sp).
The ALUOp must be 010 (add), again to compute the effective address.
0
M
Add u
x
PC 4
Add 1
Shift
left 2
PCSrc
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
21
beq instruction path
One sample branch instruction is beq $at, $0, offset.
The ALUOp is 110 (subtract), to test for equality. The branch may
or may not be
taken, depending
0 on the ALU’s Zero
M output
Add u
x
PC 4
Add 1
Shift
left 2
PCSrc
RegWrite
MemWrite MemToReg
Read Instruction I [25 - 21]
Read Read
address [31-0]
register 1 data 1
ALU Read Read 1
I [20 - 16]
Read Zero address data M
Instruction
register 2 Read 0 u
memory 0 Result Write
data 2 M x
M Write address
register u Data 0
u x Write
x Registers memory
I [15 - 11] Write 1 ALUOp data
1 data
MemRead
ALUSrc
RegDst
I [15 - 0] Sign
extend
22
Control signal table
sw and beq are the only instructions that do not write any registers.
lw and sw are the only instructions that use the constant field. They also
depend on the ALU to compute the effective memory address.
ALUOp for R-type instructions depends on the instructions’ func field.
The PCSrc control signal (not listed) should be set if the instruction is beq
and the ALU’s Zero output is true.
23
Generating control signals
The control unit needs 13 bits of inputs.
— Six bits make up the instruction’s opcode.
— Six bits come from the instruction’s func field.
— It also needs the Zero output of the ALU.
The control unit generates 10 bits of output, corresponding to the signals
mentioned on the previous page.
You can build the actual circuit by using big K-maps, big Boolean algebra,
or big circuit design programs.
The textbook presents a slightly different control unit.
RegDst
RegWrite
I [31 - 26] ALUSrc
Read Instruction
address [31-0] ALUOp
I [5 - 0]
Control MemWrite
Instruction
MemRead
memory
MemToReg
PCSrc
Zero
24
Summary
A datapath contains all the functional units and connections necessary to
implement an instruction set architecture.
— For our single-cycle implementation, we use two separate memories,
an ALU, some extra adders, and lots of multiplexers.
— MIPS is a 32-bit machine, so most of the buses are 32-bits wide.
The control unit tells the datapath what to do, based on the instruction
that’s currently being executed.
— Our processor has ten control signals that regulate the datapath.
— The control signals can be generated by a combinational circuit with
the instruction’s 32-bit binary encoding as input.
Next, we’ll see the performance limitations of this single-cycle machine
and try to improve upon it.
25