Final Study Guide
Download
Report
Transcript Final Study Guide
EE 333
Fall 2006
Computer Organization
Final Exam Study
Final Exam
Tuesday, December 12
1:30P – 3:30P
Closed Book
Lillevik 333f06-s3
University of Portland
School of Engineering
1
EE 333
Fall 2006
Skills
• Explain the five major components of a
computer and what they do
• Convert between decimal, binary, hex
• Describe the MIPS programmer’s view
• Explain the key MIPS features
• Given memory contents, find a specific byte
or word
Lillevik 333f06-s3
University of Portland
School of Engineering
2
EE 333
Fall 2006
Skills
• Write a MIPS assembly program segment
for a mathematical expression
• Write a MIPS assembly program segment
for a loop
• Explain the difference between an assembly
language instruction and a machine
language instruction
Lillevik 333f06-s3
University of Portland
School of Engineering
3
EE 333
Fall 2006
Skills
• Convert between an effective address and a
target address
• Explain the two passes of an assembler
• Describe the R, I, and J-format instructions
and their fields
• Convert an assembly language statement to
its machine language representation
Lillevik 333f06-s3
University of Portland
School of Engineering
4
EE 333
Fall 2006
Skills
• Determine the mode and select input values
for an LS181 for a specific function
• Design a 16-bit ALU using the LS181 part
• Design a logical shifter both left and right
• Design a 16-to-32 bit sign extender circuit
• Find the register and/or immediate values
for the MIPS datapath and an instruction
Lillevik 333f06-s3
University of Portland
School of Engineering
5
EE 333
Fall 2006
Skills
• Define: program counter, register file,
instruction memory, data memory
• Identify the number of clocks for the multicycle datapath and an instruction
• Calculate the Fmax for the MIPS datapath
Lillevik 333f06-s3
University of Portland
School of Engineering
6
EE 333
Fall 2006
Skills
• Describe the organization (key components)
of the MIPS datapath: shared memory, ALU,
registers, memory
• Explain the five MIPS instruction steps and
what they do (IF, ID, EX, MEM, WB)
• Identify instruction steps on a timing
diagram
Lillevik 333f06-s3
University of Portland
School of Engineering
7
EE 333
Fall 2006
Skills
• Determine the minimum clock period for
synchronous system: T > Tprop + Tcomb + Tset
• Find Fmax for a computer system
• Explain an optimistic action
• Describe the function of the MIPS control
signals
Lillevik 333f06-s3
University of Portland
School of Engineering
8
EE 333
Fall 2006
Skills
• Determine the MIPS control signals for:
– Instruction fetch
– Instruction decode, register read, and optimistic
branch address
– R-type execution and register write back
Lillevik 333f06-s3
University of Portland
School of Engineering
9
EE 333
Fall 2006
Skills
• Determine the MIPs control signals for:
– Memory reference
• Effective address
• Memory access (write for store, read for load)
• Register write back (for load)
– Beq execution
– Jump execution
Lillevik 333f06-s3
University of Portland
School of Engineering
10
EE 333
Fall 2006
Skills
• Design a PC with the LS161
• List the MIPS state transitions for a set of
instructions
• Describe the organization (key components)
of the MDP16 datapath
• Convert between MDP16 assembly and
machine instructions
Lillevik 333f06-s3
University of Portland
School of Engineering
11
EE 333
Fall 2006
Skills
• Design a register file and determine the
timing diagram
• Explain the goals of a memory hierarchy
and the cost-capacity-speed relationships
• Describe the Principle of Locality
• Define the characteristics of ROM and
RAM components
Lillevik 333f06-s3
University of Portland
School of Engineering
12
EE 333
Fall 2006
Skills
• Design a ROM and RAM memory system
and determine the timing diagram
• For a memory system, find the length and
width of memory components
• Explain how main memory relates to a
direct-mapped cache
Lillevik 333f06-s3
University of Portland
School of Engineering
13
EE 333
Fall 2006
Skills
• Find the cache contents for a sequence of CPU
writes
• Determine cache hit/miss for a sequence of
CPU reads
• Calculate memory system average latency given
hit rate and main/cache memory latencies
Lave h Lcache 1 h Lmem
Lillevik 333f06-s3
University of Portland
School of Engineering
14
EE 333
Fall 2006
Skills
• Apply the expression for average latency to
different memory designs
• Explain the performance advantage of
write-back cache
• Determine if cache write-back is required
for a sequence of CPU writes
• Explain how set associative cache operates
Lillevik 333f06-s3
University of Portland
School of Engineering
15
EE 333
Fall 2006
Skills
• Compare the MIPS and MDP16 datapaths
• Describe the architecture and
implementation options for a computer
control unit
• Explain the advantages of
microprogramming and the general steps
• Describe the function of the MDP16 control
signals
Lillevik 333f06-s3
University of Portland
School of Engineering
16
EE 333
Fall 2006
Skills
• List the MDP16 control signals to assert for
a given operation
• Find the number of microinstructions for an
instruction (same as number of clocks)
• Determine and interpret the instruction state
diagram
• Microprogram the MDP16 IF, ID steps
Lillevik 333f06-s3
University of Portland
School of Engineering
17
EE 333
Fall 2006
Skills
• Microprogram the MDP16 R-type, I-type, and
J-type instructions, interpret the logic trace
• Explain how to use the MicroAsm program
• Design a memory system with ROM and
RAM, interpret the logic trace
• Describe how to pipeline the MIPS computer
• Find the speedup of a pipelined device
Lillevik 333f06-s3
University of Portland
School of Engineering
18
EE 333
Fall 2006
Skills
• Show how to modify a controller to support
a pipeline
• Write a subroutine using the jal and jr
instructions
• Explain how an interrupt works and why
they are used
• Describe an interrupt service routine (ISR)
Lillevik 333f06-s3
University of Portland
School of Engineering
19
EE 333
Fall 2006
Skills
• Find the bandwidth, B/s, of a bus
• Solve a problem relating the bus rate, size
of data, time to transfer information
– Data bus
– Disk drive
– I/O device
• Explain the key features of a disk: cylinder,
head, sector, platter, track, arm, spindle
Lillevik 333f06-s3
University of Portland
School of Engineering
20
EE 333
Fall 2006
Skills
• Find disk average rotational latency, s
• Explain the role of bus agents: master, slave
• Define bus cycle: arbitration, address, data,
response
• Design a serial, parallel bus arbiter
• List the goals of a RAID system and explain
how it works
Lillevik 333f06-s3
University of Portland
School of Engineering
21
EE 333
Fall 2006
Skills
• Design an I/O agent and interpret the logic
trace
– Decoding
– Reads, writes
– Tri-state bus
• Explain how an RS232 device works and is
programmed
Lillevik 333f06-s3
University of Portland
School of Engineering
22
EE 333
Fall 2006
Skills
• Explain the disadvantages of programmed
I/O (busy waits)
• Explain how direct memory access works
– Controller
– Interrupt service routine
• Describe virtual address and physical
address
• Determine the values of a page table
Lillevik 333f06-s3
University of Portland
School of Engineering
23
EE 333
Fall 2006
Skills
• Explain how the OS handles a page fault
• Find the average access time of a memory
and disk drive system
• Describe how a Translation Lookaside
Buffer (TLB) improves virtual memory
Lillevik 333f06-s3
University of Portland
School of Engineering
24
EE 333
Lillevik 333f06-s3
Fall 2006
University of Portland
School of Engineering
25
EE 333
Fall 2006
Test Preparation
• Study in small groups
– Focus on lecture and in-class problems
– With serious students, some of same level
– Go over problems, set them up, do not number
crunch
– Leave beer in refrigerator until done
• Make up a crib sheet: even though not allowed
• Don’t stay up all night, get good sleep
Lillevik 333f06-s3
University of Portland
School of Engineering
26
EE 333
Fall 2006
Test Preparation
•
•
•
•
Set up a backup for your alarm clock
Eat breakfast, lunch, dinner
Arrange alternate transportation to campus
Bring everything you need for the exam
– Pencils
– Erasers
Lillevik 333f06-s3
University of Portland
School of Engineering
27
EE 333
Fall 2006
Taking the test
• Put your name and student number on exam
• Read over the exam before writing
• Read each problem carefully, understand
what was asked
• Show your work
– Provide enough detail
– Don’t do problem “in your head”
Lillevik 333f06-s3
University of Portland
School of Engineering
28
EE 333
Fall 2006
Taking the test
• Think partial credit
– Put something down for each question
– If you are unclear, write down what you might
do to solve the problem
• Stay in motion, budget your time
– Work on a problem until you get stuck
– Give it a couple more minutes, then move on
– Return to the problem later
Lillevik 333f06-s3
University of Portland
School of Engineering
29
EE 333
Fall 2006
Taking the test
• Keep your work legible
• If you don’t understand a problem, ask the
instructor
• Don’t panic
– If you find yourself sweating, hyperventilating,
take a break
– Take a few deep breaths, stretch
– Then return to the exam
Lillevik 333f06-s3
University of Portland
School of Engineering
30
EE 333
Fall 2006
Taking the test
• Check your exam at the end
– Did you answer every question & part?
– Do your answers seem reasonable?
– Do your answers check out?
• Hand in your paper when time is called
Lillevik 333f06-s3
University of Portland
School of Engineering
31