Files
xenia-rs/migration/project-root/ppc-manual/memory/icbi.md
MechaCat02 e6d43a23ac chore: add migration/ bundle for cross-machine setup
Bundles state that lives OUTSIDE the xenia-rs repo so a fresh clone on
another machine can be brought up to identical configuration via
migration/setup.sh:

  - claude-memory/             ~/.claude/projects/-home-fabi-RE-Project-Sylpheed/memory/
                               (103 files, 1.1 MB - MEMORY.md + every
                                project_xenia_rs_*.md from audits
                                addis_signext through audit-058)
  - project-root/dot-claude/   <project-root>/.claude/settings.json
                               (Stop hook + permissions)
  - project-root/ppc-manual/   <project-root>/ppc-manual/
                               (PowerPC reference docs, 397 files, 3.7 MB)
  - project-root/run-canary.sh <project-root>/run-canary.sh
  - README.md                  Human-readable setup checklist
  - setup.sh                   Idempotent installer (also reclones
                               xenia-canary at pinned HEAD 6de80dffe)
  - MANIFEST.md                Per-file mapping + per-file-not-bundled
                               restoration recipe

Excluded from bundle (not shippable via git):
  - Sylpheed ISO (7.8 GB; copyright; manual copy required)
  - sylpheed.db (395 MB; regenerable from XEX via analysis tooling)
  - target/ build artifacts (rebuild on target)
  - audit-runs probe firehoses (.log/.stdout/.stderr ~11 GB; rerun if needed)
  - audit-runs memory dumps (.bin ~4.5 GB; rerun audit-026/027/029 if needed)
  - xenia-canary checkout (setup.sh reclones from
    git.mc02.dev/fabi/Xenia-Canary.git at HEAD 6de80dffe)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-10 21:38:38 +02:00

5.0 KiB
Raw Permalink Blame History

icbi — Instruction Cache Block Invalidate

Category: Memory · Form: X · Opcode: 0x7c0007ac

Assembler Mnemonics

Mnemonic XML entry Flags Description
icbi icbi Instruction Cache Block Invalidate

Syntax

icbi [RA], [RB]

Encoding

icbi — form X

  • Opcode word: 0x7c0007ac
  • Primary opcode (bits 05): 31
  • Extended opcode: 982
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode
610 RT/FRT/VRT destination
1115 RA/FRA/VRA source A
1620 RB/FRB/VRB source B
2130 XO extended opcode (10 bits)
31 Rc record-form flag

Operands

Field Role Description
RA0 icbi: read Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0.
RB icbi: read Source GPR.

Register Effects

icbi

  • Reads (always): RA0, RB
  • Reads (conditional): none
  • Writes (always): none
  • Writes (conditional): none

Status-Register Effects

No condition-register or status-register effects.

Operation (pseudocode)

; Pseudocode derives directly from the xenia-rs interpreter
; arm (see Implementation References). Operation semantics:
;   - Read source operands from the fields listed under Operands.
;   - Apply the arithmetic / logical / memory action described
;     in the Description field above.
;   - Write results to the destination register(s); update any
;     status bits enumerated under Status-Register Effects.
; Consult the IBM AIX reference link under IBM Reference for
; canonical PPC-style pseudocode where xenia's expression is
; terse.

C Translation Example

/* C translation: the xenia-rs interpreter arm below in           */
/* Implementation References is the authoritative semantic        */
/* snapshot. Translate it line-by-line:                            */
/*   - ctx.gpr[N]  -> r[N]       (or f[]/v[] for FPRs/VRs)        */
/*   - mem.read_u*/write_u* -> mem_read_u*_be / mem_write_u*_be   */
/*   - ctx.update_cr_signed(fld, v) -> update_cr_signed(fld, v)   */
/*   - ctx.xer_ca / xer_ov / xer_so -> xer.CA / xer.OV / xer.SO   */
/* The Register Effects and Status-Register Effects tables above  */
/* enumerate every side effect a faithful translation must emit.  */

Implementation References

icbi

Special Cases & Edge Conditions

  • Self-modifying code primitive. Removes the line containing EA from the instruction cache so a subsequent fetch reads from memory. Required after writing new instructions because the I-cache is not coherent with the D-cache or with main memory.
  • Standard recipe. The full sequence is: stw (write new code) → dcbst (push dirty data through D-cache to memory) → sync (wait for memory) → icbi (drop stale I-cache line) → isync (drain prefetch / refetch). Skipping any of these can leave the CPU executing stale instructions.
  • Cache line size. Xenon's I-cache line is 128 bytes; the low seven bits of EA are ignored.
  • RA0 semantics. When RA = 0, base is the literal zero. icbi 0, RB invalidates the line containing address RB.
  • Unprivileged. icbi is problem-state, unlike its data-side cousin dcbi.
  • No exception on bad address. Treated as a hint at the hardware level — invalidating an absent line is harmless.
  • Per-thread effect. On the multithreaded Xenon core, icbi propagates across hardware threads sharing the same L1 I-cache; cross-core invalidation requires bus broadcast handled implicitly by the cache coherence protocol.
  • Xenia models as no-op. No I-cache is simulated; rebuilds of generated code (when applicable) are triggered by the JIT cache-watcher, not by icbi itself.
  • dcbst — D-cache write-back (paired step before icbi).
  • dcbf, dcbi — D-cache push / invalidate.
  • isync — instruction-stream barrier (paired step after icbi).
  • sync — full memory barrier between dcbst and icbi.

IBM Reference