bingshuo/hololake-system-architecture
Watch
1
0
Fork
You've already forked hololake-system-architecture
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

fix(ghal): support JD Cloud 4096-entry queues

Browse source 
Seal physical probe failures as FAIL_0 receipts, clear consumed proof only through an authorized receipt, and isolate each legacy virtqueue in a 128 KiB region sized for JD Cloud.
This commit is contained in:
冰朔 2026-08-03 21:07:06 +08:00
commit e52843f4de
4 changed files with 131 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

8
product-source/hololake-platform/guanghu-os/README.md
View file

@ -112,6 +112,14 @@ Native build scripts derive their NASM addresses from
`WORLD-MANIFEST.hldp`; the traditional bootstrap code no longer owns fixed
Shanghai sector numbers.
The first JD one-time physical probe reached the native kernel and returned to
Linux with a sealed `FAIL_0` diagnostic: the cloud virtio-net RX queue exposes
4096 entries, while the inherited GHAL allocation accepted at most 1024. The
JD adapter therefore assigns a non-overlapping 128 KiB region to each legacy
queue and accepts the observed 4096-entry maximum. A failed probe remains a
failure; its LBA 134 proof must be sealed and cleared with
`clear-jd-native-probe-proof.sh` before an exact-hardware retry.
## Hosted Stage 1 installation
`scripts/install-hosted-stage1.sh` is the repeatable Ubuntu construction