Skip to content

Conversation

grypez
Copy link
Contributor

@grypez grypez commented Jun 25, 2025

WIP

This PR prototypes a user code authority to effect a kernel syscall which accepts a remotable object argument. This solution mostly bypasses liveslots, extracting vrefs by hacking apart the return values of the only-exported-for-testing marshaller; this probably messes up liveslots's book keeping efforts.

@grypez grypez force-pushed the grypez/revoke-syscall branch from e985dd6 to 52f9b80 Compare June 26, 2025 15:17
Copy link
Contributor

@sirtimid sirtimid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both makeOcapUrl and makeRovoker are synchronous, which was the argument against using a device. I wonder could we pursue that?

@grypez
Copy link
Contributor Author

grypez commented Jul 3, 2025

Both makeOcapUrl and makeRovoker are synchronous, which was the argument against using a device. I wonder could we pursue that?

With kernel service objects #563 these user-space syscalls are E-addressable from the vats that rely on them. Will update this soon to reflect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants