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

Forms

Every encoding of SYSEXIT that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
SYSEXIT SYSEXIT0F 35SEP

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.
ModelSYSEXIT
Sandy Bridge100 / 0.33p015
Haswell, Broadwell, Skylake, Skylake-SP, Ice Lake, Alder Lake, Sapphire Rapids100 / 0.25p0156
Lunar Lake100 / 0.17p012345
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 cr4 >> 32 & 1:
    fault(UD)                    # CR4.FRED
if CPL > 0 or sysenter_cs & 0xFFFC == 0:
    fault(GP, 0)
c = sysenter_cs & 0xFFFF
if OSIZE == 64:                  # REX.W: to 64-bit code
    if not canonical(rcx):
        fault(GP, 0)
    if not canonical(rdx):
        fault(GP, 0)
    rsp = rcx
    rip = rdx
    cs = c + 32 | 3
    ss = c + 40 | 3
else:                            # to 32-bit code: compatibility mode
    rsp = ecx
    rip = edx
    cs = c + 16 | 3
    ss = c + 24 | 3
# AMD's manual: #UD in long mode, 64-bit and compatibility. The
# Zen 5 guest that ran the probe raised #GP at CPL 3, probably
# KVM's answer: KVM emulates SYSEXIT on a #UD, and checks CPL first

Run on AMD Zen 5 (EPYC 9645): 2 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
SYSEXIT
RIPimplicitwrite
RSPimplicitwrite
RCXimplicitread
RDXimplicitread

Flags

None: XED records no flag that the forms test or change.

Attributes

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

All forms
privileged: CPL 0 only; not in real-address mode; 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
SEP

SEP
CPUID.01H:EDX[11] SEP

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

More SYSENTER/SYSEXIT 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 2B, page 4-706 (SYSEXIT)

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.