Add 'wasmtime: custom syscall' and 'wasmtime: UDP echo-server' demos #33
Conversation
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
2 times, most recently
from
ea26806 to
c735292
Compare
wasmtime-custom-syscall/README.md
Outdated
| @@ -0,0 +1,8 @@ | |||
| # Wasmtime Custom Syscall Demo | |||
| This demo implements a WASM runtimem based on Wasmtime, provididng custom | |||
There was a problem hiding this comment.
runtimem -> runtime
and
provididng -> providing
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
2 times, most recently
from
44ecb27 to
1574880
Compare
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
3 times, most recently
from
7fa6c6a to
9401836
Compare
|
@steveej What is the status on this? I'd like to review when it is working. |
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
2 times, most recently
from
fcc9e1e to
f534429
Compare
The status of this PR is that I'm continuously adding more features to this, because the scope of this demo hasn't been limited. Currently the demo will run a UDP echo-server on a hardcoded port. I'm working on extracting code to a common library and designing an experimental WASM module system. |
This adds a demo which shows an implementation of a simple WASM syscall module named _stdio_, containing a single syscall named _println_. It demonstrates how the backend provides the syscall to the WASM guest, and in turn how the guest calls into the syscalls.
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
2 times, most recently
from
013d3ee to
b9a0e68
Compare
steveej
changed the title
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
from
b9a0e68 to
7424c9e
Compare
This demo shows the extension of the previously introduced _stdio_ syscall module, and adds a _net_ syscall module, which implements rudimentary UDP functionality. The WASM guest application uses these syscalls to build an UDP echo server.
steveej
force-pushed
the
pr/wasmtime-custom-syscall
branch
from
7424c9e to
ee92f24
Compare
|
I've put two related demos in this PR now, without great effort to extract common code. As the production code will likely in the wasmtime upstream repository, I think it's not worth the effort to refactor this further in here. @npmccallum This is ready to be reviewed with the above in mind, please :-) |
Fixes #24.
Fixes #35.