Extensions
Forms
1 (1 Legacy)
Data
Intel XED v2026.08.23

CLI clears IF, the interrupt flag, so that the logical processor stops accepting maskable external interrupts until IF is set again by STI, POPF or IRET. Exceptions, NMIs and the software interrupts of INT still come through: IF holds off only interrupts from devices and the interrupt controller. A kernel uses CLI around code that an interrupt handler on the same processor must not run in the middle of, such as an update of that processor’s own data. IF belongs to one logical processor, so CLI does nothing to keep other processors out of shared data; that takes a lock.

Saving IF rather than clearing it

Code that may itself run with interrupts already off saves RFLAGS with PUSHF before the CLI and puts it back with POPF afterwards, so that IF returns to what it was instead of being set by an STI the caller did not expect.

Who may run it

CLI is I/O-sensitive, like IN and OUT: it clears IF when CPL is at most IOPL. Otherwise, at CPL 3 with CR4.PVI set (protected-mode virtual interrupts, which Intel’s manual says include 64-bit mode), it clears VIF, bit 19, instead and leaves IF alone, so that an operating system can track a virtual interrupt flag for code that expects to run CLI. In any other case it raises #GP(0); the two vendors’ manuals agree on this. The probe runs at CPL 3 with IOPL 0, and Zen 5 raised #GP there in each of its three recorded cases, with RFLAGS unchanged.

POPF differs: at the same privilege it does not fault but leaves IF as it was, so code cannot rely on a POPF to have turned interrupts off.

Kin

User interrupts, a separate mechanism, have their own flag, UIF, with CLUI and STUI as their CLI and STI. The instruction table of AMD’s Zen 5 guide lists CLI as microcoded.

Forms

Every encoding of CLI that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
CLI CLIFABase instruction set

Latency and throughput

What the scheduling models of LLVM 23.1.2 give for each form, not measurements: latency / reciprocal throughput in cycles, the ports under them. A row is a model, or models that agree; a dash, a form that its processors lack. Memory forms: latency from the address, ports without the load and store units. Which processors each model covers.
ModelCLI
Sandy Bridge5 / 2p15
Haswell, Broadwell, Skylake, Skylake-SP, Ice Lake100 / 0.25p0156
Alder Lake, Sapphire Rapids100 / 1p016
Lunar Lake100 / 1p0124
Bonnell100 / 0.5p01
Silvermont100 / 1FPC0
Piledriver100 / 0.5EX0 EX1
Zen, Zen 2100 / 0.25
Zen 3, Zen 4100 / 25ALU0 ALU1 ALU2 ALU3
Jaguar100 / 0.5ALU0 ALU1

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

if CPL <= iopl:
    if_ = 0                      # maskable interrupts held off
elif CPL == 3 and cr4 >> 1 & 1:  # CR4.PVI: protected-mode virtual
    vif = 0                      # interrupts, VIF in IF's place
else:
    fault(GP, 0)                 # as in the probe's cases: CPL 3, IOPL 0

Run on AMD Zen 5 (EPYC 9645): 3 cases. Every one raised an exception, at CPL 3, where the probe runs.

Operands

What each form reads and writes, as Intel XED records it: the operands of its syntax, in order, and the implicit ones that the syntax does not name. How to read.
OperandKindAction
CLI
RFLAGSimplicitread, write

Flags

T tested, M modified; blank: not affected. How to read.
IFIOPLVIF
All forms
MTM

Attributes

What else XED records about the forms. How to read.

All forms
may abort a TSX transaction

CPUID and processors

Each form belongs to an XED ISA set. A form can be used when the processor reports every CPUID bit of one of its ISA set's alternatives.

CPUID requirements and processors of the XED ISA sets above. Alternatives are separated by “or”; processors follow XED’s chip model, whose AMD processors end with Zen 2, and the CPU data of this site for Zen 3 to Zen 6.
ISA setCPUIDProcessors
I86

No CPUID bit: part of the base instruction set.

Every x86-64 processor in XED’s model and Zen 3 to Zen 6

More General-purpose instructions

All 109 General-purpose instructions

Sources

  1. Intel XED v2026.08.23 (commit 0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model.
  2. The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s -march feature sets and AMD’s Processor Programming References, which the page of each processor cites.
  3. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  4. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-148 (CLI)
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  6. AMD64 Architecture Programmer's Manual, Volume 2: System Programming (24593, rev. 3.46, October 2026)
  7. AMD64 Architecture Programmer's Manual, Volume 3: General-Purpose and System Instructions (24594, rev. 3.39, October 2026)
  8. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP

The tables are derived from Intel XED, Copyright Intel Corporation, licensed under the Apache License 2.0; x86-64.net converted and reformatted them. The timings come from LLVM's scheduling models, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.