You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The syscall.createPromise() call currently returns two separate identifiers, a promiseID and a resolverID. Both are mapped through per-vat tables when the kernel delivers them into a vat, which we use to keep track of which vats are allowed access to which promises and resolvers. The kernel-side identifier is the same for each.
We think we can simplify things by only tracking a single value. This will be named promiseID on the kernel side, and importPromiseID on the vat side (since all promises are kernel promises, so any promise-related slots that the vat knows about will be imports from the kernel).
The kernel promise table tracks a "decider vatid" for each promise. We'll use this to authorize syscall.fulfillToXYZ, which will now accept an importPromiseID instead of a resolverID.
This will parallel a change in #162, where promises can be imported/exported between machines just like presences, and are not kept in separate tables.
The text was updated successfully, but these errors were encountered:
The
syscall.createPromise()
call currently returns two separate identifiers, apromiseID
and aresolverID
. Both are mapped through per-vat tables when the kernel delivers them into a vat, which we use to keep track of which vats are allowed access to which promises and resolvers. The kernel-side identifier is the same for each.We think we can simplify things by only tracking a single value. This will be named
promiseID
on the kernel side, andimportPromiseID
on the vat side (since all promises are kernel promises, so any promise-related slots that the vat knows about will be imports from the kernel).The kernel promise table tracks a "decider vatid" for each promise. We'll use this to authorize
syscall.fulfillToXYZ
, which will now accept animportPromiseID
instead of aresolverID
.This will parallel a change in #162, where promises can be imported/exported between machines just like presences, and are not kept in separate tables.
The text was updated successfully, but these errors were encountered: