openskills.info
Course catalog
Course Preview

x86-64 Architecture

x86-64 is the 64-bit extension of the x86 instruction-set architecture used by most desktop and server PCs. It defines the instructions, registers, operating modes, memory rules, and protection mechanisms that software and operating systems rely on when they run on an x86-64 processor.

itComputer architecture and hardware

Don't Panic — x86-64 Architecture

x86-64 is the rulebook that lets a compiled program and a processor agree on what an instruction means. It is not the blueprint for a particular chip, which is fortunate because a chip blueprint would be a very poor thing to fit into an executable. AMD calls its extension AMD64; Intel calls its compatible version Intel 64. The binary mostly cares that the promised rules line up.

The first useful separation is between the ISA, the instruction-set architecture, and the microarchitecture hiding underneath it. The ISA says that registers exist, instructions have effects, and exceptions occur. The microarchitecture decides how many pipelines, caches, and prediction mechanisms turn that promise into a real processor. Same binary, different machinery, and possibly a very different afternoon spent measuring it.

The second separation is the ABI, the agreement between compiled functions. The ISA provides registers, but the ABI decides which ones carry arguments, which ones survive a call, and how the stack stays aligned. System V and Microsoft x64 make different choices while sharing x86-64 underneath. So “it is x86-64 assembly” is not yet a complete address; it still needs a platform.

Memory also declines to be merely a number. An instruction forms an effective address, then paging translates it through page tables and checks permissions. The address must be canonical for the implementation's configured width. A value can fit in 64 bits and still be rejected before it reaches ordinary memory. The processor is being fussy because the alternative is allowing nonsense to become an exciting kind of bug.

Features arrive as another layer of paperwork. CPUID reports optional facilities, and an operating system may need to enable state before software can use them. A virtual machine can expose only a selected baseline so it can move between compatible hosts. Long mode therefore does not mean every later instruction is safe to execute. It means the door is open; it does not mean every room is furnished.

Read the Introduction for the complete path from instruction bytes to paging and privilege. Use Slides for the layer map and failure clues. Keep the Cheatsheet nearby when registers, addressing, ABI rules, or CPUID checks become suspicious. The Reference tab leads to the manuals that settle arguments with documentation, which is often less dramatic than arguing with a processor and much more effective.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources