Research window: Past 24 hours (2026-09-20 04:30 ~ 2026-09-21 04:30, Beijing time). Sources: Three GitHub organization checks (RuyiAI-Stack 16 repos, ruyisdk 46 repos, openRuyi-Project 35 repos — commits, releases, and merge requests; upstream fork commits filtered item-by-item by RISC-V keywords, irrelevant upstream commits excluded), RuyiSDK developer community (latest forum topics and RuyiAI section), openRuyi distro news page, board support matrix, arXiv search, Google News RSS multi-query in Chinese and English (via proxy, no hits this window, see appendix).

Index

  • Today’s Highlight: XuanTie kernel patch extends T-Head PMA errata to PUD/P4D huge pages (09-20)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V adaptation)
    • 1.1 PyTorch riscv branch force-pushed: 96 commits reordered, 72 mainline syncs with zero hits (09-20)
    • 1.2 New merge request: riscv64 local image build script, requires native riscv64 hardware (09-20)
    • 1.3 triton-riscv, tilelang-riscv, and llvm-project: no pushes in window (09-14 / 07-16 / 09-17)
    • 1.4 Tech intelligence repo pushed 09-20 issue, site contributor data auto-updated (09-20)
  • II. RuyiSDK Toolchain and Distro (kernel, plugins, docs, support matrix, openRuyi)
    • 2.1 XuanTie kernel tree merges upstream PMA errata backport, covering 1GB and 512GB huge pages (09-20)
    • 2.2 VS Code extension releases 0.1.7-beta.1, execution blocked in untrusted workspaces (09-20)
    • 2.3 Docs site merges Ruyi Imager graphical flashing guide (09-20)
    • 2.4 Support matrix adds CoM260 Kit (SpacemiT K3) Buildroot test report (09-20)
    • 2.5 ruyi and packages-index silent in window, no commits or releases (09-16 / 09-18 status)
    • 2.6 openRuyi 18 commits in one day: container stack allows riscv_hwprobe, cloud-native and graphics packages batch-merged (09-20)
  • III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)
    • 3.1 All three dedicated target repos silent in window (09-20 status)
    • 3.2 Intelligence-side context: RVA23 certificate selection and multi-hart thresholds for architecture testing (09-18 ~ 09-19)
  • IV. Community and Events (biweekly progress, forum, docs)
    • 4.1 Community publishes 09-20 open-source tech news digest (09-20)
    • 4.2 Lichee Pi 4A practice course Episode 03 released: GPIO and actuators (09-20)
    • 4.3 Biweekly Progress Issue 077 not published, no new announcements on openRuyi news page (since 09-15)
  • V. Trend Observations
    • 5.1 Kernel and container sides both patch RISC-V-specific behavior on the same day: from “it runs” to “it runs correctly”
    • 5.2 Toolchain product line shifts to small-step releases: extension goes beta channel, docs fill in graphical tools
    • 5.3 PyTorch fork’s riscv branch reordered against upstream baseline, CI image localization fills the gap
    • 5.4 Gaps and watch items this window

Today’s Highlight: XuanTie kernel patch extends T-Head PMA errata to PUD/P4D huge pages

Date: 2026-09-20　Source: linux-xuantie-kernel commit 167b3d7c

At 16:33 Beijing time on 09-20, the RuyiSDK XuanTie kernel tree (linux-6.6.36 branch) merged an upstream backport patch titled riscv: mm: Apply T-Head PMA memory-type errata to PUD and P4D entries. The patch notes state that DAMO XuanTie’s PMA memory-type errata injects PMA type bits via ALT_THEAD_PMA() when building page table entries, but previously only covered pfn_pte(), pfn_pmd(), pfn_pgd(), and pte_modify(), not pfn_pud() and pfn_p4d(); as a result, PUD-level (1GB) and, under sv57, P4D-level (512GB) huge page mappings do not carry the memory type encoding required by XuanTie, falling back to implicit/default PMA on such cores, where memory attributes may be inconsistent with mappings of other sizes. These leaf entries can be reached by the linear mapping (create_pud_mapping() established with PUD_SIZE) and by huge-page vmap.

The fix mirrors pfn_pmd()’s approach in pfn_pud() and pfn_p4d(), running ALT_THEAD_PMA() on the protection value. The commit carries Cc stable and Fixes tags (pointing to a35707c3d850, which introduced the errata handling); upstream discussion is in the kernel mailing list thread; the backport was signed off by an Alibaba Cloud-side maintainer and, following this tree’s style, applies ALT_THEAD_PMA() to the u64 protection value. For workloads using XuanTie cores and relying on GB-level huge pages (database buffers, VM memory, large model weight mappings), this eliminates the risk of inconsistent memory attributes across mapping sizes within the same process.

I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V Porting)

Window Overview: Of the 16 repositories in the RuyiAI-Stack organization, 3 saw activity during the window: pytorch (two branch pushes and a new merge request), ruyiai-daily (1 commit), and ruyiai-stack.github.io (1 automated commit); triton-riscv, tilelang-riscv, llvm-project, pytorch-ci, FBGEMM, cpuinfo, VecIntrinBench, IntrinTrans, harness, dsh-osc, torq-tile, skills, and SyncBots-DeepAgents saw no pushes during the window.

1.1 PyTorch riscv Branch Re-push: 96 Commits Reordered, 72 Mainline Syncs with Zero Hits (09-20)

Date: 2026-09-20　Source: riscv branch commits, branch list

At 08:57 Beijing time on 09-20, a large-scale push occurred on this fork’s riscv branch (the repository’s default branch): the branch head moved from ca728fab to 6d667e1e. Comparison with the pre-push state shows the two have diverged (96 commits ahead, 22 behind), consistent with an automated sync in the form of a rebase re-push, reordering existing RISC-V-specific patches onto a newer upstream baseline—including fixes for byte conversion on RISC-V, narrowing of the linear cross-entropy ULP tolerance for RISC-V, updates to the inductor operator info test blocklist, and the ci-riscv64 workflow file. The push also refreshed the branch state of 7 open merge requests (#23, #35, #36, #38, #43, #46, #48), of which #46 and #48 are RVV-related proposals (ATen vector extension support, RVV CPU capability reporting).

The mainline main branch had another 72 upstream sync commits in the same window (last push at 03:00 Beijing time on 09-21), covering routine PyTorch upstream topics: ongoing work on precompile modularization and guard classification, stability cleanups for distributed and checkpoint tests, CUDA 13.4 Windows builds and ARM64 CUDA image definitions, etc.; filtering item by item against keywords such as RISC-V, RVV, vector, XuanTie, rv64, and rv32 yielded 0 hits. Conclusion: today’s local porting activity is concentrated in branch reordering and CI, rather than new operators or new backends.

1.2 New Merge Request: riscv64 Local Image Build Script, Requires Native riscv64 Hardware (09-20)

Date: 2026-09-20　Source: PR #51 Add riscv64 local image

At 22:54 Beijing time on 09-20, this fork created the add-riscv64-local-image branch, and at 23:05 submitted merge request #51 (target branch riscv, 1 file, 25 lines added): adding .ci/docker/build-riscv64-local.sh, which builds the pytorch-ci:riscv64 image locally with BUILD_ENVIRONMENT=pytorch-linux-noble-riscv64-py3.12-gcc14. The script first performs three prerequisite checks—the machine architecture must be riscv64 (otherwise it errors out and exits, with a comment stating the image must be built on native riscv64 hardware), and docker and docker buildx must be available—then calls the repository’s existing build.sh to complete the build. The commit message is Add riscv64 image locally, the description states alignment with upstream, and the verification section is marked WIP. This is a CI-side “image localization” gap-filling action, corresponding to the previous gap of relying on upstream or remote image pipelines.

1.3 triton-riscv, tilelang-riscv, and llvm-project Saw No Pushes During the Window (09-14 / 07-16 / 09-17)

Date: 2026-09-20　Source: triton-riscv, tilelang-riscv

The compiler and operator porting line on the RISC-V side saw no new activity this period: triton-riscv’s last commit was on 09-14 (dependency buddy-mlir nightly update), tilelang-riscv’s was on 07-16, and the llvm-project fork’s was on 09-17. All three repositories had no commits or releases during the window.

1.4 Tech Intelligence Repository Pushed the 09-20 Issue, Site Contributor Data Auto-Updated (09-20)

Date: 2026-09-20　Source: ruyiai-daily 2026-09-20 issue

The tech intelligence repository had one commit during the window (06:42 Beijing time on 09-20), containing the 09-20 issue, whose self-described rolling window is 09-17 04:37 to 09-20 06:29. The issue covers five sections: PyTorch, LLVM/MLIR, Triton and TileLang, RISC-V, and the AI industry; the five RISC-V items are the minimum hart count threshold for architecture tests and RVA23 certificate test selection, the Sail model’s F/V capability query interface, the Ssstateen coverage supplementary submission, and the XiangShan Sbuffer tag-match register reset, with times concentrated between 09-17 and 09-19, mostly content already relayed previously, and not expanded further in this issue per the no-duplication principle (see 3.2 for background). The repository’s standard is unchanged: only verified evidence that has returned to official blogs, announcements, RFCs, Releases, or official APIs is used. Separately, the site repository had one automated commit during the window (02:29 Beijing time on 09-21), routinely updating the contributor data file.

II. RuyiSDK Toolchain and Distributions (Kernel, Plugins, Docs, Support Matrix, openRuyi)

Window Overview: Of the 46 repositories in the ruyisdk organization, 4 had pushes within the window: linux-xuantie-kernel, docs, support-matrix, and ruyisdk-vscode-extension; the latest activity for ruyi, packages-index, ruyisdk-overlay, ruyisdk-website, board-docs, and others was on 09-18 or earlier. Within the openRuyi-Project organization, only openRuyi had commits during the window (18).

2.1 XuanTie Kernel Tree Merges Upstream PMA Errata Backport, Covering 1GB and 512GB Huge Pages (09-20)

Date: 2026-09-20　Source: linux-xuantie-kernel commit history

See “Today’s Highlights.” Additional points: this branch had only this one commit within the window, the previous being a 09-16 update on RISC-V hwprobe self-test keys; the commit also carries a stable tag, indicating it will enter the stable backport channel. The XuanTie kernel tree is RuyiSDK’s long-term maintenance kernel for the DAMO XuanTie platform (including some domestic development boards), and such errata backports are delivered alongside distribution images.

2.2 VS Code Extension Releases 0.1.7-beta.1, Command Execution Blocked in Untrusted Workspaces (09-20)

Date: 2026-09-20　Source: 0.1.7-beta.1 release

At 14:21 Beijing time on 09-20, the RuyiSDK VS Code extension published 0.1.7-beta.1 (pre-release) in the repository, with a 1.33 MB .vsix artifact. This is the first beta of the next version after 0.1.6 on 09-03. The release notes list eight features and eight fixes: on the feature side, more prominent package tree search hints, detailed information displayed during package installation, slug information added to package details (and removed from tags), semantic version comparison sorting, virtual workspace detection, language pack regeneration during sync-l10n, and transparent icons in the sidebar; on the fix side, two security and robustness changes—blocking command execution in untrusted workspaces, venv deletion target validation and environment alias deactivation—plus fixes for inconsistent toolchain and sysroot selection, package tree not refreshing after repository management, no refresh after resource cleanup, and the localization issue in #227. The repository had 8 commits within the window, all concentrated between 13:34 and 14:20 on 09-20, constituting one-time release preparation; the current stable version remains 0.1.6.

2.3 Docs Site Merges Ruyi Imager Graphical Flashing Instructions (09-20)

Date: 2026-09-20　Source: docs PR #149

At 10:43 Beijing time on 09-20, the docs site merged PR #149 (author Glavo): adding a new Ruyi Imager documentation section (including category configuration and index page, 5 file changes in total), and presenting Ruyi Imager alongside the existing command-line flashing workflow in the system installation guide. Ruyi Imager is a graphical system image flashing tool for RISC-V development boards; the new documentation covers supported software packages, flashing steps, safety notes, and project resources. For users primarily on entry-level boards, this turns “installing the system” from a command-line workflow into a GUI-based operation path.

2.4 Support Matrix Adds CoM260 Kit (SpacemiT K3) Buildroot Test Report (09-20)

Date: 2026-09-20　Source: support-matrix commit 21c8e46c

At 16:41 Beijing time on 09-20, the development board support matrix added a Buildroot test report for the CoM260 Kit (8 files, 422 lines, including Chinese and English documentation and four photos). Board information: CoM260 Kit on the SpacemiT K3 platform, with 8 X100 plus 8 A100 cores, 16GB LPDDR5, and 128GB UFS; the tested system is SpacemiT Buildroot K3 v1.0.7 (image built on 2026-08-19), test status marked as good, and the documentation provides the TITANTOOLS flashing workflow, pinout diagram, and desktop running screenshots. This is another board-level addition to the matrix after the two Debian reports for Premier P550 and VisionFive2 Lite on 09-18, further densifying system coverage for the K3 platform.

2.5 ruyi and packages-index Silent Within the Window, No Commits or Releases (09-16 / 09-18 Status)

Date: 2026-09-20　Source: ruyi Releases, packages-index

Since the release of 0.54.0-alpha.20260918 on 09-18, the ruyi main branch and version branches have had no new commits or Releases within the window, with the most recent merge request update stopping on 09-17; the currently installable stable version remains 0.52.0, and the latest pre-release on the 0.53 line remains 0.53.0-beta.20260917. The package index’s last commit stopped on 09-16 (multi-mirror configuration and opencv download source restrictions), with no updates within the window; the latest activity for the Gentoo overlay, official website repository, board-level documentation, and others was on 09-18 or earlier.

2.6 openRuyi’s 18 Commits in a Single Day: Container Stack Allows riscv_hwprobe, Cloud-Native and Graphics Packages Batch-Added (09-20)

Date: 2026-09-20　Source: openRuyi commit list

The openRuyi package directory had 18 commits within the window, the most single-day commits among the three organizations.

First, a RISC-V behavior fix for the container stack: a seccomp patch (41 lines) was added to containers-common, adding the riscv_hwprobe syscall to the container default seccomp whitelist, immediately adjacent to riscv_flush_icache (synchronized in both the Go default configuration and seccomp.json). The rationale given in the patch description points directly to performance: riscv_hwprobe only reads CPU feature information, and OpenSSL and zlib-ng rely on it to probe ISA extensions; once the call returns ENOSYS, it silently falls back to scalar implementations, making encryption and compression performance inside containers lower than the hardware’s actual capability. The patch is signed by a maintainer from the Institute of Software, Chinese Academy of Sciences, and the corresponding upstream issue is already in progress.

Second, download URL fixes for four container-related repositories: the upstream repositories for composefs, buildah, podman, and containers-common have migrated, and the URLs in the spec files were updated accordingly.

Third, additions and upgrades: added cloudpods 4.0.3 and cloudpods-operator 4.0.3 (multi-cloud and virtualization platform and its Kubernetes operations components), MinIO key encryption service kes 0.24.0 (with three patches: migrate to the current KMS API, allow archiving build version metadata, and fix Fortanix HTTP status formatting), Go terminal progress bar library cheggaaa/pb in both v1 and v3 packages (3.1.7), Vulkan benchmark vkmark 2025.01, 3D asset import library assimp 6.0.5, and graphics math library glm 1.0.3; upgraded go 1.27.0 to 1.27.1 (checksums and the 1.26.5 bootstrap toolchain updated in sync), jemalloc 5.3.1 to 5.4.0, iptables 1.8.11 to 1.8.13, flashrom 1.7.0 to 1.8.0, and libjaylink to 0.5.0.

III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)

3.1 All Three Dedicated Target Repositories Silent Within the Window (09-20 Status)

Date: 2026-09-20　Source: VecIntrinBench, IntrinTrans, FBGEMM

The three repositories targeting vector intrinsic benchmarks, intrinsic translation, and low-precision operator libraries had no commits within the window: VecIntrinBench’s last commit was 02-13, IntrinTrans 06-25, and the FBGEMM fork 07-13. The same group’s observation targets cpuinfo (05-20) and torq-tile (04-09) were likewise silent. The most recent reproducible result in this direction remains the RVV kernel optimization covered on 09-17, with no new benchmark data this period.

3.2 Intelligence-Side Background: RVA23 Certificate Selection and Multi-hart Thresholds in Architecture Testing (09-18 ~ 09-19)

Date: 2026-09-20　Source: riscv-arch-test PR #2408, riscv-arch-test PR #2421

The 09-20 technical intelligence issue relayed four upstream architecture verification developments, all merged before the window, recorded here as background: the architecture test repository added a CERTIFICATE option (merged 09-18, which can map the RVA23 certificate scope to executable test selections, automatically excluding extension tests and M-mode tests not belonging to that certificate), and a minimum hart count threshold (merged 09-19, where test metadata declares the required minimum hart count, and the test is not selected when the DUT configuration is insufficient); the Sail model’s C++ interface extension (merged 09-17, adding floating-point registers, D extension and vector register capability queries, and vlen, for simulation and debugging tools to read directly); and XiangShan’s fix for Sbuffer tag match register reset (merged 09-17, avoiding uninitialized select signals before the first store forwarding). All four are at the test and model interface layer and do not constitute hardware implementation changes.

IV. Community and Events (Biweekly Progress, Forum, Documentation)

4.1 Community Publishes 09-20 Open-Source Technology Hot News Digest (09-20)

Date: 2026-09-20　Source: Community post 2843

At 11:30 Beijing time on 09-20, the RuyiAI section of the RuyiSDK developer community added a daily hot news digest post, with content from the same source as the 09-20 technical intelligence issue; the summary points to precision advances in compilers and hardware backends (LLVM/MLIR framework reduction width and target semantics discussions, Triton’s multi-CTA scan support and AMD code generation module split), as well as events related to AI security boundaries. This section has maintained a pace of one post per day since 09-17.

4.2 LicheePi 4A Practical Course Episode 03 Released: GPIO and Actuators (09-20)

Date: 2026-09-20　Source: Community post 2844

At 23:19 Beijing time on 09-20, the community released the third lecture of the “LicheePi 4A RISC-V Linux Practical Course,” themed on GPIO and actuators. The course uses LicheePi 4A plus RuyiSDK and the C language as its baseline; this chapter uses gpiod to control a 5V fan via a relay, requiring students to write the three functions line_request, fan_set, and fan_decide themselves and get simulated temperature hysteresis control working; the post provides a wiring table and command sequence, and notes engineering details: the signal pin is at 1.8V level, the fan goes through a relay rather than being driven directly by GPIO, and a line can only have one occupant at a time (a leftover gpioset process will hold the line). The series catalog shows that Lecture 04 covers command dialogue and temperature control, and the lecture notes and experiments include real-device photos and on-board recordings.

4.3 Biweekly Progress Issue 077 Not Released, No New Announcements on openRuyi News Page (Since 09-15)

Date: 2026-09-20　Source: RuyiAI section, openRuyi news page

The latest RuyiSDK biweekly progress report remains Issue 076 (09-15, covering the releases of ruyi 0.52 and VS Code extension 0.1.6), and Issue 077 was not released within the window. The latest article on the openRuyi news page remains the 2026.08 version announcement (08-27), with no preview yet for the 2026.09 monthly version, and no updates to historical articles such as the secure boot practice guide.

V. Trend Observations

5.1 Kernel and Container Sides Patch RISC-V-Specific Behavior on the Same Day: From “Can Run” to “Runs Correctly”

The two most technically substantive commits in this window add no new features; instead, they correct RISC-V-specific semantics: the XuanTie kernel tree backports the PMA errata fix to PUD/P4D-level huge pages, preventing GB-scale mapped memory attributes from being inconsistent with other sizes; openRuyi adds riscv_hwprobe to the container seccomp allowlist, preventing OpenSSL and zlib-ng from silently falling back to scalar due to ENOSYS. The shared criterion for both is no longer “whether it can run,” but “whether it runs according to the hardware’s actual capabilities and architectural constraints.” Patches at this level rarely generate news, yet they directly determine measured performance and stability, and merit continued tracking in the daily brief.

5.2 Toolchain Product Line Shifts to Small-Step Releases: Plugin Enters Beta Channel, Docs Fill In Graphical Tooling

The VS Code extension enters pre-release for its next version with 0.1.7-beta.1, the documentation site adds graphical flashing instructions for Ruyi Imager the same day, and the support matrix adds a Buildroot report for the SpacemiT K3 board—these three items cover the three usage paths of editor extension, image flashing, and system adaptation, all aimed at “lowering the barrier to entry.” The ruyi core remains silent, and the 0.53 stable release still has not been tagged, giving the product cadence a “peripherals first, core digesting” shape.

5.3 PyTorch Fork’s riscv Branch Rebased onto Upstream Baseline, CI Image Localization Fills In

The riscv branch this time moves local patches onto a newer upstream baseline via a 96-commit rebase, which will bring a considerable synchronization workload in the short term along with an attendant regression surface; the newly opened PR #51 the same day calls for building CI images on native riscv64 hardware, indicating that the RISC-V-side pipeline is still filling in infrastructure rather than advancing features. The two open RVV-related merge requests (#46, #48) were refreshed by the rebase, with no new review progress, and remain the most anticipated changes in this stack.

5.4 Gaps and Focus Points in This Window

Gaps that must be faithfully recorded: news-side multi-language queries for RuyiAI, RuyiSDK, the Ruyi community, and openRuyi continue to return zero hits; no new arXiv entries within the window; ruyi and packages-index silent; all three dedicated target repositories for vectors and operators silent. Focus points: first, the tagging timing of the 0.53 stable release and biweekly progress issue 077; second, the openRuyi 2026.09 monthly release announcement (the previous version being 2026.08); third, whether new RISC-V adaptation commits will follow the PyTorch fork rebase, and the verification progress of PR #51.

Source Verification Table

Source Verification Result
RuyiAI-Stack organization (16 repos) pytorch pushed twice (riscv branch rebase of 96 commits, main sync of 72 commits) and newly opened PR #51; ruyiai-daily 1 time, site repo 1 time; the remaining 13 repos silent
ruyisdk organization (46 repos) 4 repos active: linux-xuantie-kernel (1 time), docs (1 time), support-matrix (1 time), ruyisdk-vscode-extension (8 times and released 0.1.7-beta.1); the rest silent
openRuyi-Project organization (35 repos) openRuyi 18 commits, no new Release; other repos silent
Google News RSS (multiple Chinese and English queries) Zero hits for RuyiAI / RuyiSDK / Ruyi community / openRuyi; control queries in the same batch returned normally, ruling out a scraping failure
RuyiSDK community forum 2 new topics (09-20 news, Lichee Pi 4A session 03); biweekly progress issue 077 not published
openRuyi news page No new version announcement (latest remains 2026.08)
Development board support matrix 1 commit: CoM260 Kit Buildroot test report (09-20)
arXiv (RISC-V vectors and AI compilers) No new entries within the window (most recent being the 09-17 survey, already recorded in a previous report)

Complete Source List