Timing and resource budgets: periods, priorities, deadlines, memory, with roll-up checks and a `budgets` report

Aperta
  • Qualcosa non va?
#368 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, rust, yaml
Ambito
backend, testing, tooling

Direzione di ricerca

Start by reading the existing wcet and quantities handling, the W893 budget checks, and the validate command. The proposal spans model fields, roll-up validation, schedulability and latency checks, a budgets report, and requirement links; the acceptance criteria define the expected capacity and utilization results. The issue leaves scheduling and measurement sources open, so the design needs resolution before implementation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Part of #363 (item 7).

Current state

wcet: (free text) and quantities: ({kind: ftti|latency|wcet|reaction, value, unit}) exist; budgets on them are checked (W893). Periods, priorities, deadlines and memory budgets are not modelled, so a statement such as "the fastest control task uses at most 70 % of the CPU and RAM and flash at most 80 %" (REQ-GTI-SYS-072 in the grid-tie model, and the MCU decision ADR-GTI-MCU-001) is prose that nothing can check.

Proposal

  1. Fields on tasks and parts. period, deadline, priority, wcet (structured, with units), stack, and static memory ram, flash, nvm on software parts/tasks; capacities on the hardware element they are allocated to (cpuMips or clock, ramKb, flashKb).
  2. Roll-up checks in validate (opt-in once capacities exist): sum of ram/flash/stack of everything allocated to an element against its capacity with a configurable margin (default from a requirement or a project setting); CPU utilisation from wcet/period per core with a schedulability bound (rate-monotonic or the utilisation bound, configurable); wcet greater than deadline; end-to-end latency along a chain of tasks against a latency quantity.
  3. Report. syscribe budgets [--config C] [--json]: per hardware element and core, used versus capacity, margin, and the largest contributors.
  4. Link to requirements: a margin requirement can be checked by a budget (verificationMethod: analysis with a budget reference).

Acceptance (tests first)

  • Adding a part that exceeds RAM capacity makes validate fail with the contributors named; at 79 % versus an 80 % margin it passes.
  • Utilisation above the bound is reported with the task list.
  • Grid-tie model: REQ-GTI-SYS-072 becomes a checked budget on the STM32G474.

Open questions

  • Multicore and interrupt-level scheduling models (start with fixed-priority preemptive on one core).
  • Where measured values come from (static analysis output ingested like test results).

Part of #272 (executable MBSE / software design).

Generated by Claude Code

Lingua principale
Rust
Stelle
8
Fork
1
Merge medio
3h 35m
PR unite (30g)
69

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di sjames/syscribe

Tutte le issue di sjames/syscribe

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.