Latest revision as of 05:57, 18 November 2023

Haswell (HSW) is Intel's microarchitecture based on the 22 nm process for mobile, desktops, and servers. Haswell, which was introduced in 2013, became the successor to Ivy Bridge. Haswell is named after Haswell, Colorado (Originally Molalla after Molalla, Oregon, it was later renamed due to the difficult pronunciation). In 2014 Intel introduced Haswell's successor, Broadwell.

For desktop and mobile, Haswell is branded as 4th Generation Intel Core processors. For server class processors, Intel branded it as Xeon E3 v3, Xeon E5 v3, and Xeon E7 v3.

Codenames[edit]

Process Technology[edit]

Main article: Ivy Bridge § Process Technology

Haswell-based chips are manufactured on Intel's 22 nm process.

Architecture[edit]

While sharing a lot of similarities with its predecessor Ivy Bridge, Haswell introduces many new enhancements and features. Haswell is the first desktop-line of x86s by Intel tailored for a system on chip architecture. This is a significant move that will continue to be developed over the next couple of microarchitectures. Overall Haswell shares the same basic flow as Sandy Bridge and Ivy but expands on them considerably in the execution engine with wider execution units and additional scheduler ports.

Key changes from Ivy Bridge[edit]

• 3.5x performance/watt over Nehalem
• Platform Controller Hub (PCH)
  • Shrink from 65 nm to 32 nm
• Support for DDR4 (server/enthusiast segments)
• Fully Integrated Voltage Regulator (FIVR)
• New C6 & C7 sleep states
• Cache
  • L1D$ has double the bandwidth
    • Load: 64B/cycle (up from 32B/cycle)
    • Store: 32B/cycle (up from 16B/cycle)
  • L2$ bandwidth to L1 is doubled
    • 64B/cycle (up from 32B/cycle)
  • STLB been made to support 2MB pages
    • Table has been doubled to 1,024 entries 8-Way (up from 512, 4-way)
• Reorder Buffer (ROB) was increased to 192 entries (up from 168)
• Scheduler has been widened, (see #Front-end)
  • Increased to 60 entries (up from 54)
  • Integer register file up 8 entries to 168
  • FP register file up 24 entries to 168
  • 2 additional execution ports (see #Execution_Units)
• New memory model for Transactional Synchronization Extensions

CPU changes[edit]

Haswell can do many general purpose instructions with 4 ops/cycle throughput. SandyBridge/Ivybridge could do so only for NOPs, CLC, some vector MOVs and some zeroing instructions (SUB, XOR and vector analogs).

• MOVSX and MOVZX have 4 op/cycle throughput for 8->32, 8->64 and 16->64 bit forms.
• Many ALU operations have 4 op/cycle throughput for GP registers: XOR, OR, NEG, NOT, ADD, SUB, CMP, AND, etc.
• Variable shifts and rotates (SHL r32, CL etc) latency increased from 1 cycle to 2 cycles, variable SHLD/SHRD from 2 cycles to 4 cycles.
• REP MOVS copy is twice as fast: now ~52 bytes/cycle.
• REP STOS fill is twice as fast: now ~30 bytes/cycle.

GPU changes[edit]

• Direct3D 11.1
• OpenGL 4.3
• OpenCL 1.2
• Four versions of GPU options codenamed GT1, GT2, GT3 and GT3 (with GT3e having a dedicated eDRAM L4$)

New instructions[edit]

Haswell introduced a number of new instructions:

• AVX2 - Advanced Vector Extensions 2; an extension that extends most integer instructions to 256 bits vectors.
• BMI1 - Bit Manipulation Instructions Sets 1
• BMI2 - Bit Manipulation Instructions Sets 2
• MOVBE - Move Big-Endian instruction
• FMA3 - Floating Point Multiply Accumulate, 3 operands
• TSX - Transactional Synchronization Extensions
• INVPCID - Invalidate Process-Context Identifier
• LZCNT - Leading zero count

Block Diagram[edit]

Individual Core[edit]

Memory Hierarchy[edit]

The memory hierarchy in Haswell had a number of changes from its predecessor. The cache bandwidth for both load and store have been doubled (64B/cycle for load and 32B/cycle for store; up from 32/16 respectively). Significant enhancements have been done to support the new gather instructions and transactional memory. With Haswell new port 7 which adds an address generation for stores, up to two loads and one store are possible each cycle.

• Cache
  • L1I Cache:
    • 32 KB 8-way set associative
      • 64 B line size
      • Write-back policy
      • shared by the two threads, per core
  • L1D Cache:
    • 32 KB 8-way set associative
      • 64 B line size
      • shared by the two threads, per core
      • 4 cycles for fastest load-to-use
      • 64 Bytes/cycle load bandwidth
      • 32 Bytes/cycle store bandwidth
      • Write-back policy
  • L2 Cache:
    • unified, 256 KB 8-way set associative
    • 11 cycles for fastest load-to-use
    • 64B/cycle bandwidth to L1$
    • Write-back policy
  • L3 Cache:
    • 1.5 - 3 MB
    • Write-back policy
    • Per core
  • L4 Cache:
    • 128 MB
    • Per package
    • Only on the Iris Pro GPUs

Haswell TLB consists of dedicated level one TLB for instruction cache and another one for data cache. Additionally there is a unified second level TLB.

• TLBs:
  • ITLB
    • 4KB page translations:
      • 128 entries; 4-way set associative
      • dynamic partition; divided between the two threads
    • 2MB/4MB page translations:
      • 8 entries; fully associative
      • Duplicated for each thread
  • DTLB
    • 4KB page translations:
      • 64 entries; 4-way set associative
      • fixed partition; divided between the two threads
    • 2MB/4MB page translations:
      • 32 entries; 4-way set associative
    • 1G page translations:
      • 4 entries; 4-way set associative
  • STLB
    • 4KB+2M page translations:
      • 1024 entries; 8-way set associative
      • shared

Core[edit]

Pipeline[edit]

Haswell, like its predecessor Ivy Bridge, also has a dual-threaded and out-of-order pipeline.

Front-end[edit]

The front-end is the complicated part of the microarchitecture as it deals with variable length x86 instructions ranging from 1 to 15 bytes. The main goal here is to fetch and decode correctly the next set of instructions. The caches have not changed in Haswell from Ivy Bridge, with the L1i$ still 32KB , 8-way set associative shared dynamically by the two threads. Instruction cache instruction fetching remains 16B/cycle. TLB is also still 128-entries, 4-way for 4KB pages and 8-entries, fully associative for 2MB page mode. The fetched instructions are then moved on to an instruction queue which has 40 entries, 20 for each thread. Haswell continued to improve the branch misses although the exact details have not been made public.

Haswell has the same µOps cache as Ivy Bridge - 1,536 entries organized in 32 sets of 8 cache lines with 6 µOps each. Hits can yield up to 4-µOps/cycle. The cache supports microcoded instructions (being pointers to ROM entries). Cache is shared by the two threads.

Following the instruction queue, instructions are coded via the complex 4-way decoder. The decoder has 3 simple decoders and 1 complex decoder. In total, they are capable of emitting 3 single fused µOps and an additional 1-4 fused µOps. The unit handles both micro and macro fusions. Macro-fusion as a result of compatible adjacent µOps may be merged into a single µOp. Push and pops as well as call and return are also handled at this stage. 4 instructions, but with the aid of the macro-fusion, up to 5 instructions can be decoded each cycle.

Execution engine[edit]

Continuing with the decoder is the register renaming stage. This is crucial for out-of-order execution. In this stage the architectural x86 registers get mapped into one of the many physical registers. The integer physical register file (PRF) has been enlarged by 8 addition registers for a total 168. Likewise the FP PRF was extended by 24 registers bringing it too to 168 registers. The larger increase in the FP PRF is likely to accommodate the new AVX2 extension. The ROB in Haswell has been increased to 192 entries (from 168 in Ivy) where each entry corresponds to a single µOp. The ROB is fixed split between the two threads. Additional scheduler resources get allocated as well - this includes stores, loads, and branch buffer entries. Note that due to how dependencies are handled, there may be more or less µOps than what was fed in. For the most part, the renamer is unified and deals with both integers and vectors. Resources, however, are partitioned between the two threads. Finally, as a last step, the µOps are matched with a port depending on their intended execution purpose. Up to 4 fused µOps may be renamed and handled per thread per cycle. Both the load and store in-flight units were increased to 72 and 42 entries respectively.

Haswell continues to use a unified scheduler for all µOps which holds 60 entries. µOps at this stage sit idle until they are cleared to be executed via their assigned dispatch port. µOps may be held due to resource unavailability.

Following a successful execution, µOps retire at a rate of up to 4 fused µOps/cycle. Retirement is once again in-order and frees up any reserved resource (ROB entries, PRFs entries, and various other buffers).

Execution Units[edit]

Some of the biggest architectural changes were done in the area of the execution units. Haswell widened the scheduler by two ports - one new integer dispatch port and a new memory port bringing the total to 8 µOps/cycle. The various ports have also been rebalanced. The new port 6 adds another Integer ALU designs to improve integer workloads freeing up Port 0 and 1 for vector works. It also adds a second branch unit to lower the congestion for Port 0. The second port that was added, Port 7 adds a new AGU. This is largely due to the improvements for AVX2 that roughly doubled its throughput. Port 0 had its ALU/Mul/shifter extended to 256-bits; same is true for the vector ALU on port 1 and the ALU/shuffle on port 5. Additionally a 256-bit FMA unit were added to both port 0 and port 1. The change makes it possible for FMAs and FMULs to issue on both ports. In theory, Haswell can peak at over double the performance of Sandy Bridge, with 16 double / 32 single precision FLOP/cycle + Integer ALU option + Vector operation.

The scheduler dispatches up to 8 ready µOps/cycle in FIFO order through the dispatch ports. µOps involving computational operations are sent to ports 0, 1, 5, and 6 to the appropriate unit. Likewise ports 2, 3, 4 and 7 are used for load/store and address calculations.

Clock domains[edit]

This section is empty; you can help add the missing info by editing this page.

Overclocking[edit]

See also: Intel's XMP

Overclocking needs to be done on an unlocked part such as the Core i7-5820K, Core i7-5930K, or Core i7-5960X Extreme Edition. Additionally those chips need to be paired with the Intel X99 Chipset.

The 5930K and the 5820K are hexa-core parts whereas the 5960X is an octa-core part. Between 28 and 40 PCIe lanes are possible with a core ratio of up to x80 the BCLK.

Haswell provides a Coarsed BCLK ratios of either 100 MHz, 125 MHz, or 167 MHz (this was consequently changed in Skylake). The clock is generated internally by the chipset, but motherboard ODMs could generate it independently. A single BCLK from the PCH is fed in < 1 MHz steps, however in practice the input is very much limited by PCI Express and DMI PLL interface. This works out to 100 MHz ± 5-7% PEG/DMI @ 5:5, 125 MHz ±5-7% PEG/DMI @ 5:4, and 166.66 MHz ±5-7% @ 5:3.

All the clock domains in Haswell are derived from the BCLK (also called DMICLK). In the diagram on the right (xC) refers to the Core Frequency and is represented as a multiple of BCLK (Core Frequency = BCLK × Core Freq Multiplier up to x80). Likewise (xM) refers to the memory ratio (up to 2667 MT/s in granularity operations of 200 and 266 MHz) and Two additional multipliers to adjust the PEG(PCIe & Graphics)/DMI links which should remain at a nominal frequency of 100 MHz.

Voltage control is done by Haswell's new FIVER (Full Integrated Voltage Regulator) based architecture. This means that voltage arrives via the V_CCin input from the motherboard into the processor and onto the voltage regulator (V_CCin = SVID 1.8 V Nom up to 2.3 V+). Internally, the various voltage planes are all derived from there. This includes the V_CORE, V_RING, and V_SA. With the memory voltage (V_DDQ = 1.2 V Nom) provided from the motherboard with to its own rail.

Die[edit]

Client Die[edit]

Client die come in 2, 4, or 8 cores setup with dual/quad being mainstream models and the octa-core being the high-end desktop.

Dual-core GT2[edit]

• 22 nm process
• 960,000,000 transistors
• 131 mm² die size
• 2 CPU cores

Dual-core GT3[edit]

• 22 nm process
• 1,300,000,000 transistors
• 181 mm² die size
• 2 CPU cores

Quad-core GT2[edit]

• 22 nm process
• 1,400,000,000 transistors
• 177 mm² die size
• 4 CPU cores
• 1 GPU core
  • 2x10xEU (80 ALUs)

Quad-core GT3[edit]

• 22 nm process
• 1,700,000,000 transistors
• 260 mm² die size
• 4 CPU cores

Octa-core[edit]

• Core i7-5960X
• Octa-core processor
• 22 nm process
• 2,600,000,000 transistors
• 355.52 mm² die size
• 17.6 mm x 20.2 mm

Server Die[edit]

Octadeca-core[edit]

• 18 cores processor
• 22 nm process
• 5,690,000,000 transistors
• 622 mm² die size

Added instructions[edit]

AVX2 - Integer data types were extended to 256-bit SIMD.

BMI1 / BMI2 - Bit Manipulation Instructions Sets

FMA3 - Fused Multiply-Add instructions, 3 operands

MOVBE - Move Big-Endian instruction

TSX - Transactional Synchronization Extensions

Cores[edit]

This section is empty; you can help add the missing info by editing this page.

All Haswell Chips[edit]