implement_Bus_alt1 #16

Merged

Yehowshua merged 23 commits from implement_Bus_alt1 into main

2025-04-16 22:00:14 +00:00

Yehowshua commented

2025-04-16 22:00:06 +00:00

Owner

Bus currently type-checks and compiles but hasn't been tested for functionality...

The following warnings indicate there may be fairness concerns:

Warning: "bs/Top.bs", line 60, column 0: (G0010)
  Rule "bus_server0_arbit_requests" was treated as more urgent than
  "bus_server1_arbit_requests". Conflicts:
    "bus_server0_arbit_requests" cannot fire before "bus_server1_arbit_requests":
      calls to
        bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read
        bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset
        bus_clientRequestQueues_1_beforeDeq.write vs. bus_clientRequestQueues_1_beforeDeq.read
        bus_clientRequestQueues_1_dequeueing.wset vs. bus_clientRequestQueues_1_dequeueing.wset
    "bus_server1_arbit_requests" cannot fire before "bus_server0_arbit_requests":
      calls to
        bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read
        bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset
        bus_clientRequestQueues_1_beforeDeq.write vs. bus_clientRequestQueues_1_beforeDeq.read
        bus_clientRequestQueues_1_dequeueing.wset vs. bus_clientRequestQueues_1_dequeueing.wset
Warning: "bs/Top.bs", line 60, column 0: (G0010)
  Rule "bus_server1_arbit_requests" was treated as more urgent than
  "bus_client0_arbit_submission". Conflicts:
    "bus_server1_arbit_requests" cannot fire before "bus_client0_arbit_submission":
      calls to
        bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read
        bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset
    "bus_client0_arbit_submission" cannot fire before "bus_server1_arbit_requests":
      calls to
        bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read
        bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset
Warning: "bs/Top.bs", line 60, column 0: (G0010)
  Rule "bus_client0_arbit_submission" was treated as more urgent than
  "bus_client1_arbit_submission". Conflicts:
    "bus_client0_arbit_submission" cannot fire before "bus_client1_arbit_submission":
      calls to
        bus_submitResponseQueues_0_rv.port1__write vs. bus_submitResponseQueues_0_rv.port1__read
        bus_submitResponseQueues_1_rv.port1__write vs. bus_submitResponseQueues_1_rv.port1__read
    "bus_client1_arbit_submission" cannot fire before "bus_client0_arbit_submission":
      calls to
        bus_submitResponseQueues_0_rv.port1__write vs. bus_submitResponseQueues_0_rv.port1__read
        bus_submitResponseQueues_1_rv.port1__write vs. bus_submitResponseQueues_1_rv.port1__read

These concerns warrant further investigation...

Bus currently type-checks and compiles but hasn't been tested for functionality... The following warnings indicate there may be fairness concerns: ```bash Warning: "bs/Top.bs", line 60, column 0: (G0010) Rule "bus_server0_arbit_requests" was treated as more urgent than "bus_server1_arbit_requests". Conflicts: "bus_server0_arbit_requests" cannot fire before "bus_server1_arbit_requests": calls to bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset bus_clientRequestQueues_1_beforeDeq.write vs. bus_clientRequestQueues_1_beforeDeq.read bus_clientRequestQueues_1_dequeueing.wset vs. bus_clientRequestQueues_1_dequeueing.wset "bus_server1_arbit_requests" cannot fire before "bus_server0_arbit_requests": calls to bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset bus_clientRequestQueues_1_beforeDeq.write vs. bus_clientRequestQueues_1_beforeDeq.read bus_clientRequestQueues_1_dequeueing.wset vs. bus_clientRequestQueues_1_dequeueing.wset Warning: "bs/Top.bs", line 60, column 0: (G0010) Rule "bus_server1_arbit_requests" was treated as more urgent than "bus_client0_arbit_submission". Conflicts: "bus_server1_arbit_requests" cannot fire before "bus_client0_arbit_submission": calls to bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset "bus_client0_arbit_submission" cannot fire before "bus_server1_arbit_requests": calls to bus_clientRequestQueues_0_beforeDeq.write vs. bus_clientRequestQueues_0_beforeDeq.read bus_clientRequestQueues_0_dequeueing.wset vs. bus_clientRequestQueues_0_dequeueing.wset Warning: "bs/Top.bs", line 60, column 0: (G0010) Rule "bus_client0_arbit_submission" was treated as more urgent than "bus_client1_arbit_submission". Conflicts: "bus_client0_arbit_submission" cannot fire before "bus_client1_arbit_submission": calls to bus_submitResponseQueues_0_rv.port1__write vs. bus_submitResponseQueues_0_rv.port1__read bus_submitResponseQueues_1_rv.port1__write vs. bus_submitResponseQueues_1_rv.port1__read "bus_client1_arbit_submission" cannot fire before "bus_client0_arbit_submission": calls to bus_submitResponseQueues_0_rv.port1__write vs. bus_submitResponseQueues_0_rv.port1__read bus_submitResponseQueues_1_rv.port1__write vs. bus_submitResponseQueues_1_rv.port1__read ``` These concerns warrant further investigation...

Yehowshua added 23 commits 2025-04-16 22:00:06 +00:00

Type system progress on bus design da761f6e4e

skeletons of Bus module slowly forming fe2fa21fcc

Bus types typecheck!!! 989c4e9616

things still typecheck b4c7537a85

shoudl probably rethink approach... 076d3aed43

stubbed out mkBus for now - awaits full implementation ca02c88be3

preliminary work on client methods and some type repair 979adf3660

client methods presumably finished c9356eecfd

add bus diagram and further work on Bus 71fbb7d2e5

don't commit bkp files 548a2f26bd

quieter builds, more type uniformity, full compiles 5efef8b19c

- made builds less verbose on Mac by removing `-cpp`
 - made type constructors for most instances of `(UInt (TLog n))`
 - addressed cases where types built upon `(UInt (TLog n))` may have
   a max value of `n`, which necessitates changing the type to
   ` (UInt (TLog (TAdd 1 n)))`
 - compiler wouldn't fully evaluate types unless mkBus was
   instantiated

incomplete but need to come to stopping point cffbadd1cc

WIP : client request should handle unmapped case 45191a2abd

stopping point 628319709e

request server from client rule in client issue 813f543b42

having trouble with type constraints around clientIdx 98f2f5cdfd

notable progress WRT client requests invoking arbiter request 373d170c3f

some prep work to towards having a server accept a request cd3d728083

we may not need dispatch by client 180eeeefbe

potential scaffolding for new approach f3acae0c1c

worked on client arbiter but need to consider if starving is possible when multiple client arbiters grant access to the same server a58c836981

first attempt at server rule, also implemented consumeRequest of the server part of the Bus interface c28425f10c

in theory bus is now complete ece1f86574