The generator had not been able to run correctly since the manual moved into
`tools/ppc-manual/`: it computed the repository root as `HERE.parent.parent`,
which now names `tools/`, so the XML, Canary's emitters and xenia-rs all stopped
resolving — silently, because both scrapers skipped what they could not find.
Every page's references had been pointing at paths that exist nowhere.
What each source contributed, measured on the 350 pages before this change:
Operation (pseudocode) 251 pages: fixed boilerplate "derives from the xenia-rs
interpreter"; 99 carry real hand-written seeds
C translation 337 pages: the same kind of boilerplate
xenia-rs snapshot 336 pages: the interpreter arm, pasted in — the only
per-instruction semantics on unseeded pages
links xenia-rs opcode/decoder/interpreter + Canary emitter
Now:
* semantics come from **Xenia Canary**, the reference emulator, read through
`git show` at a pinned upstream commit (`origin/canary_experimental`,
f21ebd49e9). Not our checkout: it carries instrumentation and lacked
upstream's `mcrf` fix, so it would have published probes and a wrong `mcrf`.
Each page embeds the emitter (`InstrEmit_<mnem>`), and for the 128 pure
one-line delegations also the helper that holds the semantics.
* decode references point at `crates/sylpheed-ppc` — the decoder that
produces `sylpheed.db` — as in-repo relative links.
* the boilerplate now says what is true, and the C translation guide maps
Canary's actual HIR calls, checked against `ppc_hir_builder.h` (including
that `UpdateCR(n, v)` truncates to 32 bits).
* `rust_scraper.py` -> `decoder_scraper.py` (interpreter half dropped);
missing sources are now errors, not empty results.
Verified:
consistency checks 455 XML entries, 350 families, 598 index keys
hand-written tails 386/386 byte-identical after regeneration
xenia-rs in generated 0
pages with a snapshot 349/350 (was 336) — `dcbi` has no Canary emitter at all
in-repo decoder links 910/910 resolve to a line holding the identifier
emitter boundaries brace counter == column-0 `}` rule on 521/521;
preprocessor model unit-tested (#if 0/#else/#elif)
idempotency re-run: 0 pages updated, 0 working-tree changes
Hand-written notes (outside the generated regions) are not rewritten here:
* 110 links into `../../xenia-rs/...` were dead; they now point at the file in
the archived repository (git.mc02.dev/fabi/xenia-rs @ 8401d4d). Line anchors
were dropped because the notes predate that commit — 0 of 441 old line
ranges match it — and a precise-looking wrong anchor is worse than none. The
link text, which carries the author's line numbers, is unchanged.
* 140 prose claims about xenia-rs's behaviour remain. 23 are verified to hold
for Canary too (the 32-bit CR0 truncation, OE left unimplemented); the other
114 need checking one by one, and some invert — e.g. `divdx` notes a correct
64-bit CR0 update in xenia-rs where Canary's `UpdateCR` truncates. Left for
a deliberate pass rather than a blind substitution.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
5.4 KiB
5.4 KiB
mtmsr — Move to Machine State Register
Category: Control / CR / SPR · Form: X · Opcode:
0x7c000124· sync
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
mtmsr |
mtmsr |
— | Move to Machine State Register |
Syntax
mtmsr [RS]
Encoding
mtmsr — form X
- Opcode word:
0x7c000124 - Primary opcode (bits 0–5):
31 - Extended opcode:
146 - Synchronising: yes
| Bits | Field | Meaning |
|---|---|---|
| 0–5 | OPCD |
primary opcode |
| 6–10 | RT/FRT/VRT |
destination |
| 11–15 | RA/FRA/VRA |
source A |
| 16–20 | RB/FRB/VRB |
source B |
| 21–30 | XO |
extended opcode (10 bits) |
| 31 | Rc |
record-form flag |
Operands
| Field | Role | Description |
|---|---|---|
RS |
mtmsr: read | Source GPR (alias for RD in some stores). |
MSR |
mtmsr: write | Machine State Register. |
Register Effects
mtmsr
- Reads (always):
RS - Reads (conditional): none
- Writes (always):
MSR - Writes (conditional): none
Status-Register Effects
No condition-register or status-register effects.
Operation (pseudocode)
; No hand-written pseudocode for this instruction yet.
; The authoritative semantics are the Canary emitter snapshot under
; Implementation References; about half of Canary's emitters open
; with the PPC-style definition as a comment (`RD <- (RA) + (RB)`).
; Every side effect is also enumerated in the Register Effects and
; Status-Register Effects tables above.
C Translation Example
/* No hand-written C yet. Translate the Canary emitter snapshot */
/* under Implementation References; its HIR maps directly: */
/* f.LoadGPR(n) / f.StoreGPR(n, v) -> r[n] / r[n] = v */
/* f.LoadFPR / StoreFPR, f.LoadVR / StoreVR -> f[n], v[n] */
/* f.Load(ea, T), f.Store(ea, v) -> raw read / write; emitters */
/* wrap them in f.ByteSwap for the big-endian guest value */
/* f.UpdateCR(n, v) -> CR field n from v's LOW 32 BITS vs 0 */
/* f.LoadCA / f.StoreCA -> xer.CA; f.StoreSAT -> vscr.SAT */
/* i.XO.RA, i.D.DS, ... -> the bit-fields listed under Operands */
/* The Register Effects and Status-Register Effects tables above */
/* enumerate every side effect a faithful translation must emit. */
Implementation References
mtmsr
- Canary XML:
tools/ppc-instructions.xml— search formnem="mtmsr" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_control.cc:824 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:183 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:895
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_mtmsr(PPCHIRBuilder& f, const InstrData& i) {
f.StoreContext(offsetof(PPCContext, msr), f.LoadGPR(i.X.RT));
return 0;
}
Special Cases & Edge Conditions
- Privileged.
mtmsris supervisor-only on real hardware. Executing it from problem state raises a Privileged Instruction interrupt. Game code never emits it; only the kernel and exception-return paths use it. - 32-bit form.
mtmsrwrites the low 32 bits of MSR (legacy PPC32 form). On the Xenon (a PPC64 implementation), usemtmsrdfor the full 64-bit MSR. Some Xenon kernel sequences still usemtmsrto leave the high half untouched while flipping low-half flags like EE/PR. - Synchronisation. Marked
sync—mtmsris execution-synchronising. The Xenon must drain all preceding instructions before the new MSR takes effect, and PowerISA recommends a followingisyncto guarantee subsequent instructions execute under the new MSR. Loperand. Modern PowerISA defines anLbit selecting "EE/RI only" (L=1) versus "all" (L=0); xenia-rs ignoresLand writes the entire MSR. Real Xbox 360 kernel code uses bothL=0andL=1.- xenia model. Treats MSR as a flat
u64field. Bothmtmsrandmtmsrdexecute the same body —ctx.msr = ctx.gpr[rs]. No privilege or atomicity is enforced; no side effects on TLB / interrupt mask / endianness are simulated. - No CR / XER side effects.
- Caveat for translators. Because the host kernel runs natively in xenia, the guest MSR has no architectural meaning beyond storage. Code that reads it back via
mfmsrwill see exactly what was last written.
Related Instructions
mfmsr— read MSR.mtmsrd— 64-bit form (writes the entire MSR).sc— kernel entry; the kernel handler typically usesmtmsr/rfidto return.isync— companion fence after MSR writes.
mtmsr has no simplified mnemonics.
IBM Reference
- AIX 7.3 —
mtmsr(Move to Machine State Register) - PowerISA v2.07B, Book III §4.3.1 — MSR field definitions and
L-bit semantics.