1 / 60

Processor structure and function

Processor structure and function . Members: Zhe Geng Jorge Montenegro Carlos Garrido wAlli Butt Adrian Suarez Diego Arias . Contents . Processor Organization Register Organization User-visible registers Control and Status register Example Microprocessor Register Organizations

lysa
Download Presentation

Processor structure and function

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Processor structure and function Members: ZheGeng Jorge Montenegro Carlos Garrido wAlli Butt Adrian Suarez Diego Arias

  2. Contents • Processor Organization • Register Organization • User-visible registers • Control and Status register • Example Microprocessor Register Organizations • Instruction Cycle • The Indirect Cycle • Data Flow  •  Instruction Pipeline • Strategy • Branch Prediction

  3. Processor organization ZheGeng

  4. CPU must do the following things : • Fetch instruction • --- Read instruction from memory • Interpret instruction • --- The instruction is decoded • Fetch data • --- Read data from memory or an I/O module • Process data • --- Perform arithmetic or logical operation • Write data • --- Write data to memory or an I/O module

  5. CPU With system bus

  6. CPU Internal Structure

  7. Register Organization Carlos garrido & jorgemontenegro

  8. Registers • CPU must have some working space (temporary storage) • Called registers • Number and function vary between processor designs • One of the major design decisions • Top level of memory arrangement

  9. User Visible Registers • General Purpose • Data • Address • Condition Codes

  10. How Many GP Registers? • Between 8 - 32 • Fewer = more memory references • More does not reduce memory references and takes up processor real estate • See also RISC • One cycle execution time • Pipelining • Large number of registers

  11. How big? • Large enough to hold full address • Large enough to hold full word • Often possible to combine two data registers • C programming • double int a; • long int a;

  12. Condition Code Registers • ADVANTAGES: • Because condition codes are set by normal arithmetic and data movement instructions • Conditional instructions, such as BRANCH are simplified relative to composite instructions, such as TEST AND BRANCH. • Condition codes facilitate multi-way branches. For example, a TEST instruction can be followed by two branches, one on less than or equal to zero and one on greater than zero.

  13. Condition Code Registers • DISADVANTAGES: • Condition codes add complexity, both to the hardware and software. Condition code bits are often modified in different ways by different instructions. • Condition codes are irregular, they are typically not part of the main data path, so they require extra hardware connections. • Often condition code machines must add special non-condition-code instructions for special situations anyway. • In a pipelined implementation, condition codes require special synchronization to avoid conflicts.

  14. Control and status registers • Program Counter (PC): Contains the address of an instruction to be fetched. • Instruction Decoding Register (IR): Contains the instruction most recently fetched. • Memory Address Register (MAR): Contains the address of a location in memory • Memory Buffer Register (MBR): Contains a word of data to be written to memory or the most recently read.

  15. Program status word (PSW) • Sign:Contains the sign bit of the result of the last arithmetic operation. • Zero: Set when the register is “0” • Carry: Set if an operation resulted in a carry addition or subtraction of a higher order bit • Equal: Set if a logical compare result is equality. • Overflow: Used to indicated arithmetic overflow. • Interrupt enable/disable: Used to enable or disable interrupts.

  16. Supervisor Mode • Supervisor: Indicates whether the processor is executing in supervisor mode or user mode • Privilege instruction • Address space • Memory management • Protection domain or Protection Ring • Ring • Kernel

  17. Microprocessor register organization

  18. Instruction Cycle wAlli Butt

  19. Section 12.3Instruction Cycle An instruction cycle (sometimes called fetch-and-execute cycle, fetch-decode-execute cycle, or FDX) is the basic operation cycle of a computer. It is the process by which a computer retrieves a program instruction from its memory, determines what actions the instruction requires, and carries out those actions. This cycle is repeated continuously by the central processing unit (CPU), from bootup to when the computer is shut down.

  20. The circuits used in the CPU during the cycle are: • Program Counter (PC)– • Memory Address Register (MAR)- • Memory Data Register (MDR)- • Instruction register (IR)– • Control Unit (CU)- • Arithmetic logic unit (ALU)- • There are typically four stages of an instruction cycle that the CPU carries out: • Fetch the instruction from memory. • 2) "Decode" the instruction. • 3) "Read the effective address" from memory if the instruction has an indirect address. • 4) "Execute" the instruction.

  21. The instruction cycle is the time in which a single instruction is fetched from memory, decoded, and executed. THE FOUR SUB-CYCLES: Fetch Reads the next instruction from memory into the processor. Indirect Cycle May require memory access to fetch operands, therefore more memory accesses. Interrupt Save current instruction and service the interrupt. Execute Interpret the opcode and perform the indicated operation.

  22. There are six fundamental phases of the instruction cycle: • 1.) fetch instruction (aka pre-fetch) • 2.) decode instruction • 3.) evaluate address (address generation) • 4.) fetch operands (read memory data) • 5.) execute (ALU access) • 6.) store result (writeback memory data)

  23. DECODE EVALUATE AND FETCH Decoding the instruction? The decoder interprets what? What is being fetched from memory? What decision is made next? Based on the decision what are the options? What if decision is a direct memory operation? What if decision is an indirect memory operation?

  24. A note on addressing modes

  25. Instruction Cycle with and without Indirect Cycle…

  26. Sample question: • Given that the instruction cycle is the time in which a single instruction is fetched from memory, decoded, and executed: • A microprocessor provides an instruction capable of moving a string of bytes from one area of memory to another. The fetching and initial decoding of the instruction takes 10 clock cycles.Thereafter, it takes 15 clock cycles to transfer each byte.Themicroprocessor is clocked at a rate of 10 GHz. Determine the length of the instruction cycle for the case of a string of 64 bytes. • ANSWER: • The length of a clock cycle is 0.1 ns. The length of the instruction cycle for this • case is [10 + (15 × 64)] × 0.1 = 960 ns.

  27. Another example: total number of cycles required • To execute the SAL instruction: • add A, B, C • 1.) Fetchinstruction (add) from memory address PC. • 2.) IncrementPC to address of next instruction. • 3.) Decodethe instruction and operands. • 4.) Loadthe operands B and C from memory. • 5.) Executethe add operation. • 6.) Storethe result into memory location A. • Execution Time • Suppose each memory access (fetch, load, store) requires 10 clock cycles and that the PC update, instruction decode, and execution each require 1 clock cycle. The total number of cycles to execute the add instruction is: • 10+1+1+10+10+1+10 = 43 cycles/instruction. • A CPU running at 100 Mhz (100,000,000 cycles/sec) can execute add instructions at a rate of 100,000,000/43 = 2,325,581 instructions/sec, or ~2.3 Mips (million instructions/sec).

  28. IR MBR Data Flow: Fetch Cycle

  29. Memory MBR Data Flow: Indirect Cycle

  30. PC Control Unit Data Flow: Interrupt Cycle

  31. Data Flow: Execute Cycle • The execute cycle: • Takes many forms • the form depends on which of the various machine instructions is in the IR. • This cycle may involve • transferring data among registers • read or write from memory • I/O • invocation of the ALU

  32. Instruction Pipeline Adrian Suarez & Diego Arias

  33. Instruction Pipelining • By separating an instruction cycle into stages, multiple instructions at different stages can be worked on at the same time. • For example, Stage 2 of the current instruction can be overlapped with Stage 1 of the next instruction.

  34. A Two-Stage Pipeline • An instruction cycle can be divided into two stages: • Fetch: get an op-code from main memory and put it in a register • Execute: decode an op-code and execute the instruction • The execute stage of the current instruction would overlap with the fetch stage of the next instruction. • Assuming that fetch and execute use the same number of clock cycles, this would double the speed (in reality, execute takes longer).

  35. A Two-Stage Pipeline

  36. A Six-Stage Pipeline • Fetch instruction (FI): get op-code from memory and put it in a register • Decode instruction (DI): decode op-code and determine addressing mode • Calculate operand (CO): get effective address of source operands • Fetch operands (FO): get operands from memory and put them in registers • Execute instruction (EI): execute instruction and write result to a register • Write operand (WO): store the result in memory • This pipeline is more typical of modern computers, especially RISC computers (e.g. MIPS, SPARC, and DLX). • Each stage occupies about the same number of clock cycles.

  37. A Six-Stage Pipeline

  38. Why not a 100-Stage Pipeline? • If 1 instruction per cycle can be achieved with a 5-stage pipeline, adding more stages would only increase the number registers without increasing speed (it might actually make the computer less efficient). • Overlapping of instructions requires additional logic to account for dependencies between instructions (i.e. a memory read after a memory write to the same location).

  39. Pipeline Hazards • Resource hazards: when two instructions in the pipeline need to use the same resource • Data hazards: when two instructions must be executed in sequence (i.e. a memory write followed by a memory read) • Branch hazards: when a conditional branch occurs and the pipeline fetches the wrong instructions

  40. Resource Hazards • A resource hazard occurs when two stages in the pipeline need to use the same resource at the same time. For example, two stages need to read from main memory (assuming that the data hasn’t been cached) when an operand fetch is overlapped with an instruction fetch. • In this case, the two stages must be executed in series rather than in parallel, and a delay must be introduced in the pipeline.

  41. Resource Hazards

  42. Resource Hazards

  43. Data Hazards • A data hazard occurs whenever data is fetched from a location before it contains the correct value. • The “correct” value is whatever value it would contain if the instructions were executed in sequence. • Whenever the fetch stage must access data that hasn’t yet been written, the pipeline must be delayed at the fetch stage.

  44. Data Hazards • ADD EAX, EBX • SUB ECX, EAX • ; I3 • ; I4

  45. Branch Hazards

  46. Pipeline Implementation • A pipeline is implemented as a series of sequential circuits, with each stage taking its input from the output of the previous stage

  47. DEALING WITH BRANCHES • The most difficult part in designing an instruction pipeline is assuring a steady flow of instructions to the initial stages of the pipeline. Several approaches have been taken for dealing with conditional branches. • Multiple streams • Prefetch branch target • Loop buffer • Branch prediction • Delayed branch.

  48. Dealing with branches

  49. Multiple streams • A pipeline has disadvantages for a branch instruction because it must choose one of two instructions to fetch the next instruction and may take the wrong choice. One way of dealing with this is to allow the pipeline to fetch both instructions, making use of both streams. • With multiple pipelines there are delays for accessing register and memory. • Additional branch instructions may enter the pipeline before the original branch decision is resolved.

  50. Prefetch branch target • The target of the branch is prefetched when a conditional branch is recognized in addition to the instruction following the branch. • The target is saved until execution, if a branch is taken that means that it has already been prefetched.

More Related