Files
xenia-rs/migration/project-root/ppc-manual/memory/dcbst.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

4.8 KiB
Raw Permalink Blame History

dcbst — Data Cache Block Store

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
dcbst dcbst Data Cache Block Store

Syntax

dcbst [RA0], [RB]

Encoding

dcbst — form X

  • Opcode word: 0x7c00006c
  • Primary opcode (bits 05): 31
  • Extended opcode: 54
  • 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 dcbst: read Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0.
RB dcbst: read Source GPR.

Register Effects

dcbst

  • 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

dcbst

Special Cases & Edge Conditions

  • Write-through, no invalidate. If the addressed line is dirty, it is written back to memory; the line itself remains in the cache (clean afterwards). Lighter than dcbf — the cache stays warm.
  • Cache line size. Xenon's line is 128 bytes; the low seven bits of EA are ignored. There is no dcbst128; the operation is sized to the architectural line.
  • RA0 semantics. RA = 0 selects literal zero as base. dcbst 0, RB pushes the line containing address RB to memory.
  • Self-modifying code stage 1. The canonical "patch then run" sequence is stw (modify) → dcbst (push dirty data to memory) → syncicbi (invalidate I-cache for the same address) → isync. dcbst is preferred over dcbf here because it leaves the data in D-cache for any subsequent normal reads.
  • DMA hand-off. Used before initiating a GPU or DMA read of a buffer the CPU has just written, to ensure memory holds the latest data.
  • Unprivileged. Available from problem state.
  • Xenia models as no-op. No cache state is simulated; PC advances and memory is already authoritative.
  • dcbf — flush + invalidate (heavier alternative).
  • dcbi — invalidate without write-back (privileged).
  • dcbz, dcbz128 — allocate-and-zero.
  • dcbt, dcbtst — prefetch hints.
  • icbi — instruction-cache invalidate, sequenced after dcbst in self-modifying-code recipes.
  • sync, isync — ordering primitives that bracket cache control.

IBM Reference