0.5.0 —— 第三台机器不再是例外 - #3
Merged
Merged
Conversation
xPack 按目标族发布 QEMU 且没有 x86 构建,于是 x86_64 那一行此前从 apt 装模拟器 再手工调用:它是唯一一行结果取决于 Ubuntu 恰好发了什么的。mcpplibs/qemu-x86 从源码 为五个宿主构建 qemu-system-x86_64,xim:qemu-x86 携带它。 - build.mcpp 的三分支同形,机器类型按 arch 选(virt / q35) - CI 三行都走 mcpp run,分支消失 - 模板与 README 的 'x86_64 只能 build' 全部改为可运行 - README 的「未做」表:时钟一行从「未开始」改为「已回答未实现」,由 examples/clock-study 的实测支撑;xim:qemu-x86 一行删除 实测:三例(switch / clock-study)× 三机器全部构建并运行。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
xPack 按目标族发布 QEMU 且没有 x86 构建,于是 x86_64 那一行此前从 apt 装模拟器再手工调用 —— 它是三行里唯一一行结果取决于 Ubuntu 恰好发了什么的。
mcpplibs/qemu-x86从源码为五个宿主构建qemu-system-x86_64,xim:qemu-x86已合入索引(openxlings/xim-pkgindex#665)。改动
build.mcpp的三分支同形。机器类型按 arch 选:两台 RISC 机器上virt,x86_64 上q35—— 它没有 para-virtual 板,镜像经 multiboot 而不是-kernel的裸镜像路径进入,这也是它的链接脚本带 a.out kludge 而另外两个不带的原因mcpp run,if [ -n "\${{ matrix.qemu }}" ]那个分支消失,apt一列删除examples/clock-study:时钟归属的调研,三台机器各跑一次,FINDING.md记录结论xim:qemu-x86一行删除;时钟一行从「未开始」改为「已回答未实现」⭐ 时钟调研的产出
三台机器都能用一条无地址指令读到单调递增的计数器,只有一台能说出它走多快(aarch64 的
cntfrq_el0= 62500 kHz;riscv 架构不报告,x86_64 的 CPUID leaf 0x15 拒绝)。⇒ 把「时钟」当一件事是错的:
counter()属于本层,frequency()与set_deadline()不属于。先写接口会得到三件一套,其中两件在三台里的两台上无法兑现。本地实测
两个例子 × 三台机器全部构建并运行:
switch ok在 riscv64 / aarch64 / x86_64 上都打印,clock-study三台都跑完。x86_64 的引导用的是qemu-x86的载荷。