The SPIN model `wake_workers_no_std` must follow the new loop order

未关闭 适合新手
#804 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
75/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
rust

调研方向

阅读 specification/awkernel_async_lib/src/task/wake_workers_no_std/wake_workers.pml 中的 primary_main,并将其循环顺序与 kernel/src/lib.rs:109-114 进行比较。更新模型,使其依次运行 wake_tasks、wake_workers,然后运行 sleep;当模型与实现一致,且受影响的已提交结果文件已重新生成时,任务即完成。issue 指出,run.sh 可能会将受内存限制而未完成的搜索错误地报告为成功,因此重新生成结果时,请检查是否出现搜索未完成警告。

由索引模型根据 Issue 内容生成。

描述

File: specification/awkernel_async_lib/src/task/wake_workers_no_std/wake_workers.pml
(primary_main), related to kernel/src/lib.rs:109-114.

The model still has the old order:

wake_tasks(time_to_wait)
sleep(0, time_to_wait)
wake_workers(0)

The loop has three steps, so wake_tasks; wake_workers; sleep is a different
cyclic order, and the 32 committed result files no longer describe the
implementation. Please update the model in this PR or in a follow-up:

wake_tasks(time_to_wait)
wake_workers(0)
sleep(0, time_to_wait)

I ran this reordered model locally. All 16 configurations of
CONCURRENT_WORK_CONSERVATION and EVENTUALLY_EXECUTE
(TIMER_EDGE/TIMER_LEVEL x IRQ_POS 0-3) completed a full state-space
(TIMER_EDGE/TIMER_LEVEL x IRQ_POS 0-3) completed a full state-space
search with errors: 0. I did not run the 16 CPU_WAKING_TO_ACTIVE_CPU0/1
configurations.

Notes for regenerating the results:

  • The state space grows by a few percent, and -DMEMLIM=55000 in the Makefile
    is no longer enough. EVENTUALLY_EXECUTE needs 50.7-52.8 GB for
    IRQ_POS 1-3 and more for IRQ_POS=0. EVENTUALLY_EXECUTE /
    TIMER_LEVEL / IRQ_POS=0 needed 55.5 GB, and it only completed with a
    smaller hash table (./pan -a -n -w26) and -DMEMLIM=56500.
  • run.sh only checks for a trail file, so a run that stops at the memory
    limit (Warning: Search not completed) is recorded as true. It should also
    check for that warning.
  • The README lists kernel/src/main.rs as a target, but the loop is in
    kernel/src/lib.rs.

Other parts of the model need no change:

  • spawn_task does run_queue++ and then wake_up(..., 0, ...). The
    implementation keeps this order; the notification only moved from
    ArcWake::wake into the schedulers.
  • wake_tasks has no wake_up, which matches wake_cpu(0) being a no-op on
    CPU 0.
  • The model uses run_queue both as the queue and as the counter, so it
    already assumes an exact counter. This PR makes the implementation match it.
  • The std model (wake_workers) has a two-step loop
    (select_wait; wake_workers), so the reorder does not change it after the
    first iteration.
主要语言
Rust
星标
282
派生
12
平均合并
2 天 9 小时
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tier4/awkernel 的其他 Issue

查看 tier4/awkernel 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。