# PyTorch: [AARCH64] Use oneDNN jit:int8 matmul for torch._int_mm (#200389)

> **Key Architectural Takeaway:** On AArch64, torch._int_mm always uses the native fallback loop.

**Published:** 2026-10-13T11:39:29+00:00 
**Source:** PyTorch GitHub Releases 
**Category:** bigtech-foss 
**Canonical URL:** https://fosswire.org/news/pytorch-aarch64-use-onednn-jitint8-matmul-for-torchintmm-200.html 

## Executive Summary
On AArch64, torch._int_mm always uses the native fallback loop. TorchAO's Int8DynamicActivationInt8WeightConfig calls _int_mm on CPU, so int8 linear layers don't benefit from oneDNN. Since v3.13, oneDNN's AArch64 jit:int8 matmul (SVE + I8MM) supports s32 output ( uxlfoundation/oneDNN#5267 ). This PR routes _int_mm to it. Changes (AArch64 only; x86 unchanged) Dispatch _int_mm to oneDNN when the CPU has SVE and I8MM.

## Architectural & Systems Analysis
From an infrastructure engineering, cloud-native scale, and hyperscale governance standpoint:

- **Hyperscale Provenance:** Open-sourcing internal frameworks subjects proprietary systems to rigorous public analysis.
- **De-facto Standard Cohesion:** Publishing enterprise tooling establishes interoperable specifications across distributed execution.
- **Vendor Decoupling:** Platform engineers can inspect underlying telemetry and memory layouts without black-box vendor lock-in.

## Impact on the Open Ecosystem
Bridges enterprise engineering scale with independent, reproducible open-source software stacks.